View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations 5 Whys |  Delivery Value Stream Mapping |  Operations Root Cause Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
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 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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-30 min | 1-3 h | 1-4 h | 2-4 h |
Participantsdifferent | 2-6 | 4-10 | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Current-state map, Future-state map, Bottleneck list | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Root causeIncidentLeanProblem solving | LeanFlowWasteDelivery | Root causeProblem solvingQualityIncident | Root causeSafetyIncident |