View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Smoke Test |  Agile Start Stop Continue |  Agile Starfish Retrospective |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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 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 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 | 1-5 Tage | 30-60 min | 45-90 min | 1-4 Wochen |
Participantsdifferent | Nutzertraffic | 3-12 | 4-12 | 1-6 |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationExperimentsDemandGrowth | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | ExperimentsGrowthAnalyticsValidation |