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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
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
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.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.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
MediumMediumLowLow
Timedifferent
1-3 h90-180 min initial, dann laufend15-30 min30-120 min
Participantsdifferent
3-103-82-62-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogKPI Tree, Owner ListRoot cause notes, CountermeasuresObservation Notes, Improvement Ideas
Tagsno overlap
ProcessOperationsImprovement
MetricsStrategyAlignmentMeasurement
Root causeIncidentLeanProblem solving
LeanObservationProcessOperations
Add more methods