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
Paper illustration for Kaizen Event.
Operations
Kaizen Event
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.For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.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
LowLowMediumMedium
Timedifferent
1 h bis mehrere Wochen15-30 min0.5-5 Tage1-4 h
Participantsdifferent
1-82-64-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeRoot cause notes, CountermeasuresKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Continuous improvementLeanExperiments
Root causeIncidentLeanProblem solving
LeanContinuous improvementOperations
Root causeProblem solvingQualityIncident
Add more methods