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 Context Map |  Knowledge Modeling Domain Storytelling |  Operations 8D Problem Solving |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 1-2 h | 1-6 Wochen | 1-3 h |
Participantsdifferent | 2-8 | 2-8 | 4-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain Story, Glossary Notes, Process Narrative | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | KnowledgeDomain-Driven DesignProcess | QualityProblem solvingRoot cause | Domain-Driven DesignBoundariesModeling |