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 Context Map |  Domain Modeling EventStorming |  Innovation Starbursting |
|---|---|---|---|---|
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 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 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. | Helps clarify ideas, open questions, and testable next steps in concrete terms. It opens the thinking space, collects ideas, and leads to testable options. The result is captured as a star-shaped question map, question list, and assumption list. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-3 h | 2-8 h | 30-60 min |
Participantsdifferent | 2-8 | 2-8 | 5-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Context Map, Integration Patterns, Boundary Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Star-Shaped Question Map, Question List, Assumption List |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignEventsDiscoveryWorkshop | BrainstormingIdeationWorkshopDiscovery |