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 |  Systems Thinking Leverage Points |  Domain Modeling Domain Context Map |  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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 | High | Medium | Low |
Timedifferent | 1-3 h | Half day | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Leverage Map, Action Strategy | Domain Context Map, Boundary Notes, Ownership Map | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Systems thinkingChangeStrategy | Domain-Driven DesignContextBoundaries | ChangeDecisionStrategy |