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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
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.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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.
Complexitydifferent
LowLowMediumHigh
Timedifferent
15-30 min30-120 min1-3 h2-8 h
Participantsdifferent
2-62-63-102-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement BacklogProblem Analysis, Decision Analysis, Risk Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
LeanObservationProcessOperations
ProcessOperationsImprovement
Problem solvingRoot causeDecisionOperations
Add more methods