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 |  Agile Starfish Retrospective |  Agile Mad Sad Glad |  Facilitation Responsibility Poker |
|---|---|---|---|---|
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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 | 4-12 | 3-10 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Starfish Board, Practice Changes, Experiments | Emotion Board, Themes, Action Items | Responsibility Map, Role Agreements, Open Questions |
Tags1 shared | AutonomyRolesTeam | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamReflection | RolesResponsibilityTeamFacilitation |