View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Product Discovery Pretotyping |  Product Discovery Smoke Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 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 | Medium | Low | Low | Medium |
Timedifferent | 30-240 min | Stunden bis wenige Tage | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 1-6 | 1-4 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ValidationDemandMVP | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |