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 |  Innovation Design Charrette |  Systems Thinking Systems Mapping |  Innovation Brainstorming |
|---|---|---|---|---|
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. | 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. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | Halber Tag bis mehrere Tage | 1-3 h | 30-60 min |
Participantsdifferent | 2-8 | 10-50 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | System Map, Dependencies, Leverage Points | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | BrainstormingWorkshopCollaborationIdeation | Systems thinkingMappingBoundariesChange | BrainstormingIdeationCreativityWorkshopDivergence |