methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
A paper-based illustration representing Brainstorming with its core stages and visible working result.
Innovation
Brainstorming
Paper illustration for Reverse Brainstorming
Innovation
Reverse Brainstorming
Purposedifferent
For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development.For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer.
Complexitydifferent
LowMediumLowLow
Timedifferent
15-30 min3–4 h for initial assessment; preparation and deeper analysis additional30-60 min30-60 min
Participantsdifferent
2-61 or a small team; particularly suitable for 3–4 people4-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Root cause notes, CountermeasuresLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksIdea pool, Theme clusters, ShortlistReverse Ideas, Risk Themes, Solution Ideas
Tagsno overlap
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskAssessmentLean
BrainstormingIdeationCreativityWorkshopDivergence
BrainstormingIdeationCreativityRisk
Add more methods