View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Expectation Mapping | ![]() Domain Modeling Context Map | ![]() Business Strategy Balanced Scorecard |
|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | 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 | Low | Medium | High |
Timedifferent | 45-90 min | 1-3 h | Halber Tag bis mehrere Wochen |
Participantsdifferent | 3-12 | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Context Map, Integration Patterns, Boundary Notes | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | AlignmentStakeholdersTeam | Domain-Driven DesignBoundariesStrategy | StrategyMetricsExecution |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






