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
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
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
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.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 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
MediumMediumLowMedium
Timedifferent
1-3 h1-3 h15-30 min1-4 h
Participantsdifferent
4-103-102-63-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Current-state map, Future-state map, Bottleneck listProcess Map, Handoff List, Improvement BacklogRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
LeanFlowWasteDelivery
ProcessOperationsImprovement
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods