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 Context Map |  Domain Modeling Domain Context Map |  Business Strategy Balanced Scorecard |
|---|---|---|---|---|
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 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. | 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. | 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 | Medium | High |
Timedifferent | 2-4 h workshop plus review | 1-3 h | 1-3 h | Halber Tag bis mehrere Wochen |
Participantsdifferent | 4-10 | 2-8 | 3-10 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | AlignmentExecutionGoalsCausality | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | StrategyMetricsExecution |