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 Lotus Blossom |
|---|---|---|---|---|
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 central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | Halber Tag bis mehrere Tage | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 10-50 | 3-12 | 3-10 |
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 | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | BrainstormingWorkshopCollaborationIdeation | Systems thinkingMappingBoundariesChange | BrainstormingIdeationCreativityDivergenceWorkshop |



