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 Fault Tree Analysis |  Operations Process Mapping |  Operations Family Tree Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | High | Medium | Medium | High |
Timedifferent | 2-6 h | 1-3 h | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-8 | 3-10 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Process Map, Handoff List, Improvement Backlog | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | RiskRoot causeSafety | ProcessOperationsImprovement | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident |