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
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration for Bucket System.
Agile
Bucket System
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 need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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.When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
15-30 min30-90 min1-3 h30-90 min
Participantsdifferent
2-63-122-83-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Root cause notes, CountermeasuresAffinity Size Map, Grouped Estimates, Unclear ItemsCause Tree, Evidence Notes, CountermeasuresBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
Root causeIncidentLeanProblem solving
EstimationBacklogRelative sizing
Root causeTreeIncidentQuality
EstimationBacklogRelative sizing
Add more methods