View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling EventStorming |  Knowledge Modeling Knowledge Mapping |  UX Research Affinity Diagramming |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-8 h | 1-3 h | 45–90 min | 1-2 h |
Participantsdifferent | 5-12 | 3-12 | 3-10 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Theme clusters, Insight statements, Opportunity areas | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | KnowledgeMappingRisk | SynthesisQualitativeRoot cause | KnowledgeConceptsMappingSensemaking |