View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Scrum |  Decision Making OODA Loop |  Business Strategy Strategy Execution Loop |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 15-60 min je Zyklus | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 1-8 | 5-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Situation Assessment, Decision Loop, Action Updates | Execution Loop, Review Cadence, Strategic Learning Log | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | AgileIterationCadence | DecisionChangeLearningStrategy | ExecutionCadenceLearningGovernance | ChangeDecisionStrategy |