View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategic, Tactical and Operational PlanningForce Field Analysisarc42Strategy Execution Loop
| Criterion |  Business Strategy Strategic, Tactical and Operational Planning |  Decision Making Force Field Analysis |  Architecture arc42 |  Business Strategy Strategy Execution Loop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 90-180 min | 45-90 min | 1-2 Tage | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 4-12 | 3-12 | 1-4 | 5-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Force Field Map, Change Levers, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | CadenceGovernanceExecution | ChangeDecisionStrategy | ArchitectureDocumentationCommunication | ExecutionCadenceLearningGovernance |