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 Scenario Planning |  Domain Modeling Domain Context Map |  Business Strategy GAP Analysis |
|---|---|---|---|---|
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. | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. | 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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | 0.5-2 Tage | 1-3 h | 1-3 h |
Participantsdifferent | 2-8 | 4-12 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Scenario Set, Strategic Implications, Robust Options | Domain Context Map, Boundary Notes, Ownership Map | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StrategyUncertaintyPlanning | Domain-Driven DesignContextBoundaries | StrategyAnalysisPlanning |