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 |  Agile Start Stop Continue |  Operations Root Cause Analysis |  Agile Mad Sad Glad |
|---|---|---|---|---|
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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 30-60 min | 1-4 h | 30-60 min |
Participantsdifferent | 3-10 | 3-12 | 3-8 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Start Stop Continue Board, Improvement Actions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Emotion Board, Themes, Action Items |
Tagsno overlap | RolesResponsibilityTeamFacilitation | RetrospectiveImprovementTeamReflection | Root causeProblem solvingQualityIncident | RetrospectiveTeamReflection |