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 Responsibility Poker |  Operations Family Tree Analysis |  Operations Barrier Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 2-4 h | 2-4 h | 15-30 min |
Participantsdifferent | 3-10 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Family Tree Diagram, Pattern Notes, Systemic Measures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Root cause notes, Countermeasures |
Tagsno overlap | RolesResponsibilityTeamFacilitation | Root causePatternsIncidentSystemic | Root causeSafetyIncident | Root causeIncidentLeanProblem solving |