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 Bottleneck Analysis.
Operations
Bottleneck Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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 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.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
MediumLowMediumMedium
Timedifferent
1-3 h15-30 min1-3 h1-4 h
Participantsdifferent
3-82-64-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresRoot cause notes, CountermeasuresCurrent-state map, Future-state map, Bottleneck listProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
FlowMeasurementConstraints
Root causeIncidentLeanProblem solving
LeanFlowWasteDelivery
Root causeProblem solvingQualityIncident
Add more methods