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 |  Facilitation Alignment Mapping |  Agile ROAM Board |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-2 h | 20-40 min initial, dann laufend | 60-90 min |
Participantsdifferent | 2-8 | 4-12 | 3-15 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Alignment Map, Open Issues, Decision Questions | ROAM Board, Owner List | Salience Diagram, Strategy per Class |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AlignmentStakeholdersStrategyFacilitation | RiskAgileTrackingAlignment | StakeholdersFacilitationAlignmentGovernance |