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 |  Operations Change Analysis |  Domain Modeling Bounded Context Canvas |  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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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-120 min | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 2-6 | 3-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Context Canvas, Glossary, Integration Notes | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ChangeRoot causeTroubleshootingComparison | Domain-Driven DesignBoundariesModeling | ChangeDecisionStrategy |