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 Fake Door Test |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-240 min | Stunden bis wenige Tage | 1-5 Tage | 30-60 min |
Participantsdifferent | 1-6 | 1-4 | Nutzertraffic | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision | Completed Experiment Canvas, Success Metric |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ValidationDemandMVP | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryHypothesis |