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 Domain Storytelling |  Operations Change Analysis |  Domain Modeling Context Map |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 1-2 h | 45-120 min | 1-3 h | 1-3 h |
Participantsdifferent | 2-8 | 2-6 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ChangeRoot causeTroubleshootingComparison | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries |