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 Fault Isolation |  Product Discovery Pretotyping |  Innovation Lean Startup |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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 | Medium | Medium |
Timedifferent | 30-180 min | Stunden bis wenige Tage | Wochen bis Monate je Lernzyklus | 1-5 Tage |
Participantsdifferent | 1-6 | 1-4 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | TroubleshootingDiagnosisEngineering | ValidationDemandMVP | LeanStartupValidationMVP | ValidationExperimentsDemandDiscovery |