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 | ![]() Decision Making OODA Loop | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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 | High | Medium | Medium | Low |
Timedifferent | 1-4 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 15-60 min je Zyklus | 15-45 min |
Participantsdifferent | 6-30 Experten | 3-20 Reviewer | 1-8 | 1-3 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | Expert Forecast, Consensus Range, Assumption Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Situation Assessment, Decision Loop, Action Updates | ADR File, Decision Log, Rationale |
Tagsno overlap | ForecastingExpertsDecisionStrategy | ArchitectureDecisionAsyncGovernance | DecisionChangeLearningStrategy | ArchitectureRationaleDocumentationGovernance |



