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 |  UX Research User Interviews |  Domain Modeling EventStorming |  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. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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 | Low | Medium | Low |
Timedifferent | 1-2 h | 30–60 min per interview | 2-8 h | 1-2 h |
Participantsdifferent | 1-8 | 1 participant per interview | 5-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Interview Notes, Themes, Insight Summary | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | QualitativeResearchCustomerDiscovery | Domain-Driven DesignEventsDiscoveryWorkshop | KnowledgeDomain-Driven DesignProcess |