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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
15-30 min45-90 min30-120 min1-4 h
Participantsdifferent
2-62-52-63-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresA3 Report, Action Plan, Root Cause AnalysisObservation Notes, Improvement IdeasProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
LeanProblem solvingCoachingOperations
LeanObservationProcessOperations
Root causeProblem solvingQualityIncident
Add more methods