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 |  Engineering Fault Isolation |  Product Discovery MVP Test Matrix |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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. | 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 several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. | 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 | Low | Medium | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 30-180 min | 45-75 min | 30-60 min |
Participantsdifferent | 1-4 | 1-6 | 2-8 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Test Matrix, Test Plan | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ValidationDemandMVP | TroubleshootingDiagnosisEngineering | ExperimentsValidationDiscoveryOptions | ExperimentsValidationDiscoveryHypothesis |