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 Sailboat Retrospective |  Agile Start Stop Continue |  Operations Accountability Ladder |  Facilitation Responsibility Poker |
|---|---|---|---|---|
Purposedifferent | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. | 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 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 | 30-60 min | 20-45 min | 45-90 min |
Participantsdifferent | 4-12 | 3-12 | 1-8 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions | Ownership Reflection, Action Commitment, Coaching Notes | Responsibility Map, Role Agreements, Open Questions |
Tags1 shared | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection | ResponsibilityLeadershipTeam | RolesResponsibilityTeamFacilitation |