View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Domain Modeling Context Map |  Decision Making DACI |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 1-3 h | 30-60 min | 1-2 h |
Participantsdifferent | 1-3 | 2-8 | 2-10 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Context Map, Integration Patterns, Boundary Notes | DACI Matrix, Decision Owner, Decision Log | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesStrategy | DecisionRolesGovernanceAlignment | AlignmentStakeholdersStrategyFacilitation |