View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopArchitecture Decision RecordForce Field AnalysisStrategic, Tactical and Operational Planning
| Criterion |  Business Strategy Strategy Execution Loop |  Architecture Architecture Decision Record |  Decision Making Force Field Analysis |  Business Strategy Strategic, Tactical and Operational Planning |
|---|---|---|---|---|
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 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. | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 15-45 min | 45-90 min | 90-180 min |
Participantsdifferent | 5-12 | 1-3 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | ADR File, Decision Log, Rationale | Force Field Map, Change Levers, Risk Notes | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureRationaleDocumentationGovernance | ChangeDecisionStrategy | CadenceGovernanceExecution |