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 |  Decision Making Assumption Surfacing |  Knowledge Modeling Knowledge Mapping |  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. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 45-90 min | 1-3 h | 45-60 min |
Participantsdifferent | 1-4 | 2-8 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption List, Critical Assumptions, Learning Plan | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationDemandMVP | AssumptionsRiskDecisionDiscovery | KnowledgeMappingRisk | AssumptionsRiskExperimentsValidation |