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 |  Knowledge Modeling Event Modeling |  Product Discovery Opportunity Solution Tree |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h | 2-6 h | 1-2 h Setup, laufend | 1-5 Tage |
Participantsdifferent | 1-8 | 2-8 | 2-6 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Event Model, UI Flow, Commands, Read Models | Opportunity Solution Tree, Experiment Backlog, Learning Log | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryOutcomesExperimentsOpportunity | ValidationExperimentsDemandDiscovery |