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 | ![]() Business Strategy Strategy Map | ![]() Business Strategy Balanced Scorecard |
|---|---|---|---|
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. | 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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 h | 2-4 h workshop plus review | Halber Tag bis mehrere Wochen |
Participantsdifferent | 2-8 | 4-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Strategy Map, Objective Set, Cause-Effect Hypotheses | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AlignmentExecutionGoalsCausality | StrategyMetricsExecution |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






