View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Accountability Ladder | ![]() Agile Starfish Retrospective | ![]() Facilitation Delegation Poker | ![]() Facilitation Responsibility Poker |
|---|---|---|---|---|
Purposedifferent | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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 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 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 | 20-45 min | 45-90 min | 45-90 min | 45-90 min |
Participantsdifferent | 1-8 | 4-12 | 3-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Ownership Reflection, Action Commitment, Coaching Notes | Starfish Board, Practice Changes, Experiments | Delegation Board, Decision Boundaries, Role Agreements | Responsibility Map, Role Agreements, Open Questions |
Tags1 shared | ResponsibilityLeadershipTeam | RetrospectiveImprovementExperimentsTeam | AutonomyRolesTeam | RolesResponsibilityTeamFacilitation |



