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 Request for Comments |  Delivery Communication Plan |  Decision Making RAPID |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 2-6 | 3-12 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Plan, Channel Matrix, Message Cadence | RAPID Role Map, Recommendation, Decision Log | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CommunicationStakeholdersDeliveryPlanning | DecisionRolesGovernance | DecisionRolesGovernanceAlignment |