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 LoopForce Field AnalysisArchitecture Decision RecordStrategic, Tactical and Operational Planning
| Criterion |  Business Strategy Strategy Execution Loop |  Decision Making Force Field Analysis |  Architecture Architecture Decision Record |  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. | 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. | 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. | 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 | 45-90 min | 15-45 min | 90-180 min |
Participantsdifferent | 5-12 | 3-12 | 1-3 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Force Field Map, Change Levers, Risk Notes | ADR File, Decision Log, Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | ExecutionCadenceLearningGovernance | ChangeDecisionStrategy | ArchitectureRationaleDocumentationGovernance | CadenceGovernanceExecution |