View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth A/B Testing |  Agile Start Stop Continue |  Product Discovery Riskiest Assumption Test |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 1-4 Wochen | 30-60 min | 1-2 Wochen pro Iteration | 45-90 min |
Participantsdifferent | 1-6 | 3-12 | 2-6 | 4-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Experiment results, Decision log, Learning summary | Start Stop Continue Board, Improvement Actions | Prioritized Assumption List, Test Plan, Results Report | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ExperimentsGrowthAnalyticsValidation | RetrospectiveImprovementTeamReflection | ExperimentsValidationDiscoveryAssumptions | RetrospectiveImprovementExperimentsTeam |