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 Starfish Retrospective |  Product Discovery Smoke Test |  Growth A/B Testing |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 45-90 min | 1-5 Tage | 1-4 Wochen | 45-90 min |
Participantsdifferent | 4-12 | Nutzertraffic | 1-6 | 4-12 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation | RetrospectiveTeamImprovement |