View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy GAP Analysis | ![]() Domain Modeling Domain Context Map | ![]() Facilitation Stakeholder Salience Model | ![]() Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 60-90 min | 1-3 h |
Participantsdifferent | 2-8 | 3-10 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Domain Context Map, Boundary Notes, Ownership Map | Salience Diagram, Strategy per Class | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | StrategyAnalysisPlanning | Domain-Driven DesignContextBoundaries | StakeholdersFacilitationAlignmentGovernance | Domain-Driven DesignBoundariesStrategy |



