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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration for ABC Analysis
Operations
ABC Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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.When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowHighLowMedium
Timedifferent
15-30 min45-90 min30-60 min1-4 h
Participantsdifferent
2-63-101-53-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresRanked Backlog, Cost-of-Delay AssumptionsABC Classification, Focus Rules, Control ListProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
LeanEconomicsSequencePrioritization
PrioritizationOperationsPortfolio
Root causeProblem solvingQualityIncident
Add more methods