View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Map |  Domain Modeling Domain Context Map |  Domain Modeling Context Map |
|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 2-4 h workshop plus review | 1-3 h | 1-3 h |
Participantsdifferent | 4-10 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | Domain Context Map, Boundary Notes, Ownership Map | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | AlignmentExecutionGoalsCausality | Domain-Driven DesignContextBoundaries | Domain-Driven DesignBoundariesStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
