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 Force Field Analysis |  Architecture Architecture Decision Record |  Decision Making OODA Loop |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. | 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 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 15-45 min | 15-60 min je Zyklus | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-12 | 1-3 | 1-8 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | ADR File, Decision Log, Rationale | Situation Assessment, Decision Loop, Action Updates | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureRationaleDocumentationGovernance | DecisionChangeLearningStrategy | ArchitectureDecisionAsyncGovernance |