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 |  Operations Change Analysis |  Decision Making OODA Loop |
|---|---|---|---|
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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-120 min | 15-60 min je Zyklus |
Participantsdifferent | 3-20 Reviewer | 2-6 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ChangeRoot causeTroubleshootingComparison | DecisionChangeLearningStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
