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 |  Architecture Architecture Decision Record |  Decision Making OODA Loop |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | 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. | 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 | High | Low | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 15-45 min | 15-60 min je Zyklus | 45-90 min |
Participantsdifferent | 5-12 | 1-3 | 1-8 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | ADR File, Decision Log, Rationale | Situation Assessment, Decision Loop, Action Updates | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureRationaleDocumentationGovernance | DecisionChangeLearningStrategy | ChangeDecisionStrategy |