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 After-Action Review |  Architecture Architecture Decision Record |  Operations Process Mapping |
|---|---|---|---|---|
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. | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 20-45 min | 15-45 min | 1-3 h |
Participantsdifferent | 5-12 | 3-12 | 1-3 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Lessons learned, Action items, Event summary | ADR File, Decision Log, Rationale | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | ExecutionCadenceLearningGovernance | LearningOperationsImprovement | ArchitectureRationaleDocumentationGovernance | ProcessOperationsImprovement |