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 PDCA Cycle.
Operations
PDCA Cycle
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
Purposedifferent
For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
1 h bis mehrere Wochen15-30 min30-120 min1-4 h
Participantsdifferent
1-82-62-63-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeRoot cause notes, CountermeasuresObservation Notes, Improvement IdeasProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Continuous improvementLeanExperiments
Root causeIncidentLeanProblem solving
LeanObservationProcessOperations
Root causeProblem solvingQualityIncident
Add more methods