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 | ![]() Decision Making Decision Matrix | ![]() Systems Thinking Systems Mapping | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Decision Matrix, Scoring Rationale, Selected Option | System Map, Dependencies, Leverage Points | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | DecisionCriteriaScoringTradeoffs | Systems thinkingMappingBoundariesChange | ChangeDecisionStrategy |



