View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:After-Action ReviewArchitecture Decision RecordStrategic, Tactical and Operational Planning
| Criterion | ![]() Operations After-Action Review | ![]() Architecture Architecture Decision Record | ![]() Business Strategy Strategic, Tactical and Operational Planning |
|---|---|---|---|
Purposedifferent | 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. | 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 | Low | Low | Medium |
Timedifferent | 20-45 min | 15-45 min | 90-180 min |
Participantsdifferent | 3-12 | 1-3 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | ADR File, Decision Log, Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | LearningOperationsImprovement | ArchitectureRationaleDocumentationGovernance | CadenceGovernanceExecution |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






