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 LoopAfter-Action Reviewarc42Strategic, Tactical and Operational Planning
| Criterion | ![]() Business Strategy Strategy Execution Loop | ![]() Operations After-Action Review | ![]() Architecture arc42 | ![]() 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. | 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 | 20-45 min | 1-2 Tage | 90-180 min |
Participantsdifferent | 5-12 | 3-12 | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Lessons learned, Action items, Event summary | Architecture Document, Context View, Runtime View, Deployment View | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | ExecutionCadenceLearningGovernance | LearningOperationsImprovement | ArchitectureDocumentationCommunication | CadenceGovernanceExecution |



