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 Bucket System.
Agile
Bucket System
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
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 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.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.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
LowMediumMediumMedium
Timedifferent
15-30 min30-90 min30-90 min1-4 h
Participantsdifferent
2-63-123-123-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresBucketed Backlog, Relative Estimates, Split CandidatesAffinity Size Map, Grouped Estimates, Unclear ItemsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
EstimationBacklogRelative sizing
EstimationBacklogRelative sizing
Root causeProblem solvingQualityIncident
Add more methods