View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Operations A3 Problem Solving |  Architecture Architecture Decision Record |  Operations After-Action Review |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min | 15-45 min | 20-45 min |
Participantsdifferent | 5-12 | 2-5 | 1-3 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | A3 Report, Action Plan, Root Cause Analysis | ADR File, Decision Log, Rationale | Lessons learned, Action items, Event summary |
Tagsno overlap | ExecutionCadenceLearningGovernance | LeanProblem solvingCoachingOperations | ArchitectureRationaleDocumentationGovernance | LearningOperationsImprovement |