View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  Operations Family Tree Analysis |  Operations Fault Tree Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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 | Medium | Medium | High | Low |
Timedifferent | 1-3 h | 2-4 h | 2-6 h | 15-30 min |
Participantsdifferent | 4-10 | 2-6 | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Family Tree Diagram, Pattern Notes, Systemic Measures | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Root cause notes, Countermeasures |
Tagsno overlap | LeanFlowWasteDelivery | Root causePatternsIncidentSystemic | RiskRoot causeSafety | Root causeIncidentLeanProblem solving |