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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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 Analysis.
Operations
Root Cause Analysis
Purposedifferent
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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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 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
MediumLowLowMedium
Timedifferent
1-3 h30-120 min15-30 min1-4 h
Participantsdifferent
2-82-62-63-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Cause Tree, Evidence Notes, CountermeasuresObservation Notes, Improvement IdeasRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeTreeIncidentQuality
LeanObservationProcessOperations
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods