View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Operations After-Action Review |  Business Strategy Strategy Execution Loop |  Operations Process Mapping |
|---|---|---|---|---|
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. | 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. | 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 | Low | Low | High | Medium |
Timedifferent | 15-45 min | 20-45 min | Initial 3-6 h, then monthly or quarterly reviews | 1-3 h |
Participantsdifferent | 1-3 | 3-12 | 5-12 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Lessons learned, Action items, Event summary | Execution Loop, Review Cadence, Strategic Learning Log | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LearningOperationsImprovement | ExecutionCadenceLearningGovernance | ProcessOperationsImprovement |