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 |  Decision Making Wideband Delphi |  Architecture Architecture Decision Record |
|---|---|---|---|
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. | A single opinion rarely holds up for planning when the future is genuinely uncertain. It separates options, evaluation criteria, and open risks. The result is captured as an Estimate Range, Assumption Log, and Expert Consensus Notes. | 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 | Medium | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h or multiple rounds | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 4-12 Experten | 1-3 |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Estimate Range, Assumption Log, Expert Consensus Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | EstimationExpertsForecasting | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
