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 Architecture Decision Record |  Systems Thinking Leverage Points |  Architecture Request for Comments |  Decision Making OODA Loop |
|---|---|---|---|---|
Purposedifferent | 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 15-45 min | Half day | 1-3 Wochen vom Draft bis zur Entscheidung | 15-60 min je Zyklus |
Participantsdifferent | 1-3 | 3-12 | 3-20 Reviewer | 1-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Leverage Map, Action Strategy | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Systems thinkingChangeStrategy | ArchitectureDecisionAsyncGovernance | DecisionChangeLearningStrategy |