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 |  Product Strategy DIBB |  Architecture Request for Comments |  Decision Making OODA Loop |
|---|---|---|---|---|
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. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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 | Low | Medium | Medium |
Timedifferent | 45-90 min | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 15-60 min je Zyklus |
Participantsdifferent | 3-12 | 2-8 | 3-20 Reviewer | 1-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Situation Assessment, Decision Loop, Action Updates |
Tags1 shared | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis | ArchitectureDecisionAsyncGovernance | DecisionChangeLearningStrategy |