View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making DACI |  Architecture Architecture Decision Record |  Team Design Team Topologies Interaction Modes |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30-60 min | 15-45 min | Half day | 90-180 min |
Participantsdifferent | 2-10 | 1-3 | Team-Leads plus Architecture | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | DACI Matrix, Decision Owner, Decision Log | ADR File, Decision Log, Rationale | Interaction Heat Map, Agreements per Pair | Decision Rights Matrix, Agreement |
Tagsno overlap | DecisionRolesGovernanceAlignment | ArchitectureRationaleDocumentationGovernance | TeamAlignmentCollaborationOrganization | DecisionGovernanceAlignmentResponsibility |