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 |  Product Discovery Pretotyping |  Operations Root Cause Analysis |  Growth A/B Testing |
|---|---|---|---|---|
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. | 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 a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | Low | Low | Medium | High |
Timedifferent | 1-5 Tage | Stunden bis wenige Tage | 1-4 h | 1-4 Wochen |
Participantsdifferent | Nutzertraffic | 1-4 | 3-8 | 1-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationExperimentsDemandGrowth | ValidationDemandMVP | Root causeProblem solvingQualityIncident | ExperimentsGrowthAnalyticsValidation |