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 Domain Context Map |  Knowledge Modeling Domain Storytelling |  Knowledge Modeling Event Modeling |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. | 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. | 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 | Low | Medium | Medium |
Timedifferent | 1-3 h | 1-2 h | 2-6 h | 1-2 h |
Participantsdifferent | 3-10 | 2-8 | 2-8 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Domain Story, Glossary Notes, Process Narrative | Event Model, UI Flow, Commands, Read Models | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | Domain-Driven DesignContextBoundaries | KnowledgeDomain-Driven DesignProcess | EventsBlueprintDomain-Driven DesignBehavior | KnowledgeConceptsMappingSensemaking |