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 | ![]() Facilitation Responsibility Poker | ![]() Agile Sailboat Retrospective |
|---|---|---|---|
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 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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 30-60 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Responsibility Map, Role Agreements, Open Questions | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | RetrospectiveImprovementTeamReflection | RolesResponsibilityTeamFacilitation | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






