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 |  Innovation Brainstorming |  Domain Modeling EventStorming |
|---|---|---|---|
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 team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 1-2 h | 30-60 min | 2-8 h |
Participantsdifferent | 2-8 | 4-12 | 5-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Idea pool, Theme clusters, Shortlist | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | BrainstormingIdeationCreativityWorkshopDivergence | Domain-Driven DesignEventsDiscoveryWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
