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 Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree 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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowHighLowMedium
Timedifferent
15-30 min45-90 min30-60 min1-3 h
Participantsdifferent
2-63-101-62-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Root cause notes, CountermeasuresRanked Backlog, Cost-of-Delay AssumptionsPareto Chart, Top Causes, Focus ListCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
Root causeIncidentLeanProblem solving
LeanEconomicsSequencePrioritization
PrioritizationQualityFocusRoot cause
Root causeTreeIncidentQuality
Add more methods