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 |  Growth A/B Testing |  Agile Start Stop Continue |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 45-90 min | 1-4 Wochen | 30-60 min | 45–75 min |
Participantsdifferent | 4-12 | 1-6 | 3-12 | Team members involved |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Experiment results, Decision log, Learning summary | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | ExperimentsGrowthAnalyticsValidation | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |