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 Scenario Planning |  Domain Modeling Context Map |  Product Strategy Impact Mapping |
|---|---|---|---|---|
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. | 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 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 goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | 0.5-2 Tage | 1-3 h | 45-90 min |
Participantsdifferent | 3-10 | 4-12 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Scenario Set, Strategic Implications, Robust Options | Context Map, Integration Patterns, Boundary Notes | Impact Map, Outcome Hypotheses, Delivery Options |
Tagsno overlap | Domain-Driven DesignContextBoundaries | StrategyUncertaintyPlanning | Domain-Driven DesignBoundariesStrategy | OutcomesStrategyBehaviorPlanning |