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 Force Field Analysis |  UX Research Customer Journey Mapping |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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 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. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 45-90 min | 2-4 h | 1-3 h |
Participantsdifferent | 2-8 | 3-12 | 4-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes | Journey Map, Pain-point List, Opportunity Backlog | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy | JourneyServiceService design | Domain-Driven DesignBoundariesModeling |