View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Delegation Poker |  Operations Family Tree Analysis |  Operations Barrier Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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 risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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 | Low | Medium | Medium | High |
Timedifferent | 45-90 min | 2-4 h | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-10 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Family Tree Diagram, Pattern Notes, Systemic Measures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | AutonomyRolesTeam | Root causePatternsIncidentSystemic | Root causeSafetyIncident | Root causeSafetySystemicIncident |