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 Delphi Method | ![]() Architecture Request for Comments | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | High | Medium | High |
Timedifferent | 1-4 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 6-30 Experten | 3-20 Reviewer | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Async | Workshop + async |
Outputdifferent | Expert Forecast, Consensus Range, Assumption Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ForecastingExpertsDecisionStrategy | ArchitectureDecisionAsyncGovernance | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






