View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Domain Modeling Context Map | ![]() Knowledge Modeling Domain Storytelling | ![]() Innovation Design Charrette |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-2 h | Halber Tag bis mehrere Tage |
Participantsdifferent | 2-8 | 2-8 | 10-50 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain Story, Glossary Notes, Process Narrative | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | KnowledgeDomain-Driven DesignProcess | BrainstormingWorkshopCollaborationIdeation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






