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 |  Knowledge Modeling IBIS |  Knowledge Modeling Concept Mapping |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | 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 | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 1-3 h | 1-2 h | 1-5 Tage |
Participantsdifferent | 1-4 | 2-8 | 1-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Issue Map, Positions, Argument Notes | Concept Map, Relationship Labels, Knowledge Gaps | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | RationaleKnowledgeDecision | KnowledgeConceptsMappingSensemaking | ValidationExperimentsDemandDiscovery |