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 |  Product Discovery Learning Card |  Product Discovery Riskiest Assumption 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-180 min | Stunden bis wenige Tage | 25-40 min | 1-2 Wochen pro Iteration |
Participantsdifferent | 1-6 | 1-4 | 1-5 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Learning Card with evidence and next action | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | TroubleshootingDiagnosisEngineering | ValidationDemandMVP | ExperimentsValidationDiscoveryLearning | ExperimentsValidationDiscoveryAssumptions |