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 |  Team Design Team Topologies Interaction Modes |  Decision Making DACI |  Decision Making RAPID |
|---|---|---|---|---|
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 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 cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | Half day | 30-60 min | 45-90 min |
Participantsdifferent | 1-3 | Team-Leads plus Architecture | 2-10 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interaction Heat Map, Agreements per Pair | DACI Matrix, Decision Owner, Decision Log | RAPID Role Map, Recommendation, Decision Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TeamAlignmentCollaborationOrganization | DecisionRolesGovernanceAlignment | DecisionRolesGovernance |