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 Root Cause Analysis |
|---|---|---|---|
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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 45-90 min | 2-4 h | 1-4 h |
Participantsdifferent | 3-10 | 2-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Family Tree Diagram, Pattern Notes, Systemic Measures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RolesResponsibilityTeamFacilitation | Root causePatternsIncidentSystemic | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
