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 Domain Context Map |  Business Strategy Balanced Scorecard |  Facilitation Stakeholder Mapping |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | Halber Tag bis mehrere Wochen | 60–90 min | 1-3 h |
Participantsdifferent | 3-10 | 4-12 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Balanced Scorecard, Strategic Measures, Initiative Map | Stakeholder Map, Engagement Plan, Risk Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignContextBoundaries | StrategyMetricsExecution | StakeholdersAlignmentFacilitationChange | Domain-Driven DesignBoundariesStrategy |