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 | ![]() Decision Making Delphi Method | ![]() Architecture Request for Comments | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 30-60 min | 1-4 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min |
Participantsdifferent | 2-10 | 6-30 Experten | 3-20 Reviewer | 1-3 |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | DACI Matrix, Decision Owner, Decision Log | Expert Forecast, Consensus Range, Assumption Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale |
Tagsno overlap | DecisionRolesGovernanceAlignment | ForecastingExpertsDecisionStrategy | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance |



