View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordStrategic, Tactical and Operational PlanningAfter-Action ReviewStrategy Execution Loop
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() Operations After-Action Review | ![]() Business Strategy Strategy Execution Loop |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | Medium | Low | High |
Timedifferent | 15-45 min | 90-180 min | 20-45 min | Initial 3-6 h, then monthly or quarterly reviews |
Participantsdifferent | 1-3 | 4-12 | 3-12 | 5-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Lessons learned, Action items, Event summary | Execution Loop, Review Cadence, Strategic Learning Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | CadenceGovernanceExecution | LearningOperationsImprovement | ExecutionCadenceLearningGovernance |



