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 Force Field Analysis |  Delivery RAID Log |  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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 30 min Setup, dann laufend | 15-60 min je Zyklus |
Participantsdifferent | 3-20 Reviewer | 3-12 | 1-3 maintaining, briefing for everyone | 1-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Force Field Map, Change Levers, Risk Notes | RAID Log, Status Report Source | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ChangeDecisionStrategy | RiskTrackingStakeholdersGovernance | DecisionChangeLearningStrategy |