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 |  Product Discovery Assumption Mapping |  Agile Starfish Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 1-4 Wochen | 45-60 min | 45-90 min | 30-60 min |
Participantsdifferent | 1-6 | 2-8 | 4-12 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Experiment results, Decision log, Learning summary | Assumption map, Test backlog, Risk ranking | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ExperimentsGrowthAnalyticsValidation | AssumptionsRiskExperimentsValidation | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |