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 |  Growth A/B Testing |  Product Discovery Assumption Mapping |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
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 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 45-90 min | 1-4 Wochen | 45-60 min | 1-2 Wochen pro Iteration |
Participantsdifferent | 4-12 | 1-6 | 2-8 | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Experiment results, Decision log, Learning summary | Assumption map, Test backlog, Risk ranking | Prioritized Assumption List, Test Plan, Results Report |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | ExperimentsGrowthAnalyticsValidation | AssumptionsRiskExperimentsValidation | ExperimentsValidationDiscoveryAssumptions |