View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Communication Plan |  Decision Making Delphi Method |  Architecture Request for Comments |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 45-90 min | 1-4 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage |
Participantsdifferent | 2-6 | 6-30 Experten | 3-20 Reviewer | 1-4 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Expert Forecast, Consensus Range, Assumption Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | ForecastingExpertsDecisionStrategy | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication |