View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Knowledge Mapping |  Product Discovery Smoke Test |  Product Discovery Pretotyping |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 1-5 Tage | Stunden bis wenige Tage | 1-5 Tage |
Participantsdifferent | 3-12 | Nutzertraffic | 1-4 | Nutzertraffic |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Interest Metrics, Conversion Signal, Learning Note | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | KnowledgeMappingRisk | ValidationExperimentsDemandGrowth | ValidationDemandMVP | ValidationExperimentsDemandDiscovery |