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 Concept Mapping |  Product Discovery Pretotyping |  Product Discovery Fake Door Test |  Product Discovery MVP Test Matrix |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 h | Stunden bis wenige Tage | 1-5 Tage | 45-75 min |
Participantsdifferent | 1-8 | 1-4 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision | Test Matrix, Test Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | ValidationDemandMVP | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryOptions |