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 Decision Rights Mapping |  Architecture Views and Beyond |  Decision Making DACI |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | 1-3 Tage | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-12 | 1-4 | 2-10 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Decision Rights Matrix, Agreement | Architecture Views, Cross-view Notes, Rationale | DACI Matrix, Decision Owner, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | DecisionGovernanceAlignmentResponsibility | DocumentationStakeholdersArchitecture | DecisionRolesGovernanceAlignment | ArchitectureDecisionAsyncGovernance |