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 | ![]() Knowledge Modeling Event Modeling | ![]() Innovation Design Charrette |
|---|---|---|---|
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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 1-2 h | 2-6 h | Halber Tag bis mehrere Tage |
Participantsdifferent | 2-8 | 2-8 | 10-50 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Event Model, UI Flow, Commands, Read Models | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | EventsBlueprintDomain-Driven DesignBehavior | BrainstormingWorkshopCollaborationIdeation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






