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 Interview |  Knowledge Modeling Domain Storytelling |
|---|---|---|---|---|
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 opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 h | 2-6 h | 30-60 min je Interview | 1-2 h |
Participantsdifferent | 1-8 | 2-8 | 5-12 Interviews | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Event Model, UI Flow, Commands, Read Models | Interview Notes, Opportunity Themes, Customer Quotes | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryInterviewsOpportunityCustomer | KnowledgeDomain-Driven DesignProcess |