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 |  Decision Making OODA Loop |  Architecture arc42 |  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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Medium | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 15-60 min je Zyklus | 1-2 Tage | 45-90 min |
Participantsdifferent | 5-12 | 1-8 | 1-4 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Situation Assessment, Decision Loop, Action Updates | Architecture Document, Context View, Runtime View, Deployment View | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ExecutionCadenceLearningGovernance | DecisionChangeLearningStrategy | ArchitectureDocumentationCommunication | ChangeDecisionStrategy |