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 | ![]() Facilitation Dot Estimation |
|---|---|---|---|
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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-3 h | 0.5-2 Tage | 5-20 min |
Participantsdifferent | 2-8 | 4-12 | 3-20 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Scenario Set, Strategic Implications, Robust Options | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StrategyUncertaintyPlanning | EstimationEffortRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






