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 Start Stop Continue |  Agile Starfish Retrospective |  Facilitation Responsibility Poker |  Operations Accountability Ladder |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 45-90 min | 45-90 min | 20-45 min |
Participantsdifferent | 3-12 | 4-12 | 3-10 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Responsibility Map, Role Agreements, Open Questions | Ownership Reflection, Action Commitment, Coaching Notes |
Tags1 shared | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | RolesResponsibilityTeamFacilitation | ResponsibilityLeadershipTeam |