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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 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.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
LowLowMediumLow
Timedifferent
15-30 min30-120 min1-4 h30-60 min
Participantsdifferent
2-62-63-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Root cause notes, CountermeasuresObservation Notes, Improvement IdeasProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Root causeIncidentLeanProblem solving
LeanObservationProcessOperations
Root causeProblem solvingQualityIncident
Root causeQualityOperations
Add more methods