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 |  Growth A/B Testing |  Product Discovery Pretotyping |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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 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. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 1-5 Tage | 1-4 Wochen | Stunden bis wenige Tage | 45-60 min |
Participantsdifferent | Nutzertraffic | 1-6 | 1-4 | 2-8 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption map, Test backlog, Risk ranking |
Tags1 shared | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation | ValidationDemandMVP | AssumptionsRiskExperimentsValidation |