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 |  Domain Modeling Context Map |  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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-3 h | 2-8 h | 1-2 h |
Participantsdifferent | 1-8 | 2-8 | 5-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Context Map, Integration Patterns, Boundary Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignEventsDiscoveryWorkshop | KnowledgeDomain-Driven DesignProcess |