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 Family Tree Analysis |  Delivery Value Stream Mapping |  Operations MORT Analysis |  Operations Fault Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 2-4 h | 1-3 h | Mehrere Tage bis Wochen | 2-6 h |
Participantsdifferent | 2-6 | 4-10 | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Current-state map, Future-state map, Bottleneck list | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | Root causePatternsIncidentSystemic | LeanFlowWasteDelivery | Root causeSafetySystemicIncident | RiskRoot causeSafety |