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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1 h bis mehrere Wochen1-3 h15-30 min30-120 min
Participantsdifferent
1-83-102-62-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeProcess Map, Handoff List, Improvement BacklogRoot cause notes, CountermeasuresObservation Notes, Improvement Ideas
Tagsno overlap
Continuous improvementLeanExperiments
ProcessOperationsImprovement
Root causeIncidentLeanProblem solving
LeanObservationProcessOperations
Add more methods