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 | ![]() Facilitation Responsibility Poker | ![]() 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. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 | Low | Medium |
Timedifferent | Mehrere Tage bis Wochen | 45-90 min | 2-4 h |
Participantsdifferent | 2-6 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Responsibility Map, Role Agreements, Open Questions | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | RolesResponsibilityTeamFacilitation | Root causePatternsIncidentSystemic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






