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 Flywheel |  Product Discovery Pretotyping |  Product Discovery Fake Door Test |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | 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 | Medium | Low | Medium | High |
Timedifferent | 60-120 min | Stunden bis wenige Tage | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 3-8 | 1-4 | Nutzertraffic | 1-6 |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision | Experiment results, Decision log, Learning summary |
Tagsno overlap | GrowthRetentionConversion | ValidationDemandMVP | ValidationExperimentsDemandDiscovery | ExperimentsGrowthAnalyticsValidation |