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 Barrier Analysis |  Operations 5 Whys |  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 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Low | High |
Timedifferent | 45-90 min | 2-4 h | 15-30 min | Mehrere Tage bis Wochen |
Participantsdifferent | 3-10 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Root cause notes, Countermeasures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | AutonomyRolesTeam | Root causeSafetyIncident | Root causeIncidentLeanProblem solving | Root causeSafetySystemicIncident |