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 | ![]() Operations After-Action Review | ![]() Agile Start Stop Continue |
|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 20-45 min | 30-60 min |
Participantsdifferent | 4-12 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Lessons learned, Action items, Event summary | Start Stop Continue Board, Improvement Actions |
Tags1 shared | RetrospectiveTeamImprovement | LearningOperationsImprovement | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






