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 |  Product Discovery Assumption Mapping |  Product Discovery Fake Door Test |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 45-60 min | 1-5 Tage | 45-90 min |
Participantsdifferent | 1-4 | 2-8 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption map, Test backlog, Risk ranking | Click Data, Interest Signal, Learning Decision | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | ValidationDemandMVP | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandDiscovery | AssumptionsRiskDecisionDiscovery |