View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Lean Startup |  Engineering Fault Isolation |  Product Discovery Smoke Test |  Product Discovery Pretotyping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | Wochen bis Monate je Lernzyklus | 30-180 min | 1-5 Tage | Stunden bis wenige Tage |
Participantsdifferent | 2-8 | 1-6 | Nutzertraffic | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Interest Metrics, Conversion Signal, Learning Note | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tagsno overlap | LeanStartupValidationMVP | TroubleshootingDiagnosisEngineering | ValidationExperimentsDemandGrowth | ValidationDemandMVP |