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 | ![]() Domain Modeling EventStorming | ![]() Decision Making Delphi Method | ![]() Domain Modeling 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. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 1-2 h | 2-8 h | 1-4 Wochen | 1-3 h |
Participantsdifferent | 2-8 | 5-12 | 6-30 Experten | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Expert Forecast, Consensus Range, Assumption Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignEventsDiscoveryWorkshop | ForecastingExpertsDecisionStrategy | Domain-Driven DesignBoundariesStrategy |



