View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Starfish Retrospective |  Operations Accountability Ladder |  Agile Start Stop Continue |  Facilitation Responsibility Poker |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 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 | 20-45 min | 30-60 min | 45-90 min |
Participantsdifferent | 4-12 | 1-8 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Ownership Reflection, Action Commitment, Coaching Notes | Start Stop Continue Board, Improvement Actions | Responsibility Map, Role Agreements, Open Questions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | ResponsibilityLeadershipTeam | RetrospectiveImprovementTeamReflection | RolesResponsibilityTeamFacilitation |