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
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
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
Purposedifferent
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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
45-90 min30-120 min1-3 h15-30 min
Participantsdifferent
2-52-63-102-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement BacklogRoot cause notes, Countermeasures
Tagsno overlap
LeanProblem solvingCoachingOperations
LeanObservationProcessOperations
ProcessOperationsImprovement
Root causeIncidentLeanProblem solving
Add more methods