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 |  Product Discovery Smoke Test |  Agile Starfish Retrospective |  Growth A/B Testing |
|---|---|---|---|---|
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 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 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 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. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 30-60 min | 1-5 Tage | 45-90 min | 1-4 Wochen |
Participantsdifferent | 3-12 | Nutzertraffic | 4-12 | 1-6 |
Formatdifferent | Workshop | Async | Workshop | Async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Interest Metrics, Conversion Signal, Learning Note | Starfish Board, Practice Changes, Experiments | Experiment results, Decision log, Learning summary |
Tagsno overlap | RetrospectiveImprovementTeamReflection | ValidationExperimentsDemandGrowth | RetrospectiveImprovementExperimentsTeam | ExperimentsGrowthAnalyticsValidation |