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 |  Facilitation Responsibility Poker |  Operations MORT Analysis |  Operations Accountability Ladder |
|---|---|---|---|---|
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 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 2-4 h | 45-90 min | Mehrere Tage bis Wochen | 20-45 min |
Participantsdifferent | 2-6 | 3-10 | 2-6 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Responsibility Map, Role Agreements, Open Questions | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Ownership Reflection, Action Commitment, Coaching Notes |
Tagsno overlap | Root causePatternsIncidentSystemic | RolesResponsibilityTeamFacilitation | Root causeSafetySystemicIncident | ResponsibilityLeadershipTeam |