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 Pretotyping |  Product Discovery Smoke Test |  Operations Root Cause Analysis |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 1-5 Tage | 1-4 h | 1-5 Tage |
Participantsdifferent | 1-4 | Nutzertraffic | 3-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Interest Metrics, Conversion Signal, Learning Note | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | ValidationExperimentsDemandGrowth | Root causeProblem solvingQualityIncident | ValidationExperimentsDemandDiscovery |