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 Brainstorming |  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. | 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. | 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 | Low | Medium |
Timedifferent | 1-2 h | 2-6 h | 30-60 min | Halber Tag bis mehrere Tage |
Participantsdifferent | 2-8 | 2-8 | 4-12 | 10-50 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Event Model, UI Flow, Commands, Read Models | Idea pool, Theme clusters, Shortlist | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | EventsBlueprintDomain-Driven DesignBehavior | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingWorkshopCollaborationIdeation |