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 |  Growth A/B Testing |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | Stunden bis wenige Tage | 30-240 min | 1-4 Wochen | 45-60 min |
Participantsdifferent | 1-4 | 1-6 | 1-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Experiment results, Decision log, Learning summary | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationDemandMVP | TroubleshootingProblem solvingDiagnosis | ExperimentsGrowthAnalyticsValidation | AssumptionsRiskExperimentsValidation |