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 Root Cause Tree Analysis |  Operations 8D Problem Solving |
|---|---|---|---|---|
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 a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 1-2 h | 1-3 h | 1-6 Wochen |
Participantsdifferent | 2-8 | 2-8 | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain Story, Glossary Notes, Process Narrative | Cause Tree, Evidence Notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | KnowledgeDomain-Driven DesignProcess | Root causeTreeIncidentQuality | QualityProblem solvingRoot cause |