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 Theory of Constraints |  Domain Modeling Context Map |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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 system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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 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 | Low | High | Medium | Medium |
Timedifferent | 1-2 h | 2-4 h Analyse, laufend | 1-3 h | 1-3 h |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Constraint Map, Improvement Plan, Flow Metrics | Context Map, Integration Patterns, Boundary Notes | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | OperationsConstraintsFlowImprovement | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignBoundariesModeling |