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 OODA Loop | ![]() Decision Making Delphi Method | ![]() 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. | 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. | 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 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 | Medium | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-60 min je Zyklus | 1-4 Wochen | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 1-8 | 6-30 Experten | 1-3 |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Situation Assessment, Decision Loop, Action Updates | Expert Forecast, Consensus Range, Assumption Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | DecisionChangeLearningStrategy | ForecastingExpertsDecisionStrategy | ArchitectureRationaleDocumentationGovernance |



