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 |  Architecture Request for Comments |  Facilitation Alignment Mapping |  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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h | 60-90 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 4-12 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ArchitectureDecisionAsyncGovernance | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |