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
Paper illustration for Bucket System.
Agile
Bucket System
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
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 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.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.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
MediumMediumLowMedium
Timedifferent
30-90 min1-4 h15-30 min1-3 h
Participantsdifferent
3-123-82-62-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Bucketed Backlog, Relative Estimates, Split CandidatesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanRoot cause notes, CountermeasuresCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
EstimationBacklogRelative sizing
Root causeProblem solvingQualityIncident
Root causeIncidentLeanProblem solving
Root causeTreeIncidentQuality
Add more methods