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 MORT Analysis |  Operations Fault Tree Analysis |  Facilitation Stakeholder Mapping |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitydifferent | High | High | Low | Medium |
Timedifferent | Mehrere Tage bis Wochen | 2-6 h | 60–90 min | 2-4 h |
Participantsdifferent | 2-6 | 3-8 | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Stakeholder Map, Engagement Plan, Risk Notes | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | RiskRoot causeSafety | StakeholdersAlignmentFacilitationChange | Root causePatternsIncidentSystemic |