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 Hypothesis-Driven Troubleshooting |  Product Discovery Test Card |  Product Discovery Learning Card |
|---|---|---|---|---|
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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Stunden bis wenige Tage | 30-240 min | 20-35 min | 25-40 min |
Participantsdifferent | 1-4 | 1-6 | 1-5 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Test Card with a pre-set threshold | Learning Card with evidence and next action |
Tagsno overlap | ValidationDemandMVP | TroubleshootingProblem solvingDiagnosis | ExperimentsValidationDiscoveryHypothesis | ExperimentsValidationDiscoveryLearning |