View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsDelphi MethodArchitecture Communication CanvasArchitecture Decision Record
| Criterion |  Architecture Request for Comments |  Decision Making Delphi Method |  Architecture Architecture Communication Canvas |  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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 Wochen | 60-120 min | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 6-30 Experten | 2-8 | 1-3 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Expert Forecast, Consensus Range, Assumption Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ForecastingExpertsDecisionStrategy | ArchitectureCommunicationStakeholdersCanvas | ArchitectureRationaleDocumentationGovernance |