View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Scrum |  Decision Making Force Field Analysis |  Decision Making OODA Loop |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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 | High | Medium | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-4 Wochen je Sprint, laufend | 45-90 min | 15-60 min je Zyklus |
Participantsdifferent | 5-12 | 3-10 (Scrum Team) | 3-12 | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Force Field Map, Change Levers, Risk Notes | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ExecutionCadenceLearningGovernance | AgileIterationCadence | ChangeDecisionStrategy | DecisionChangeLearningStrategy |