View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopAfter-Action ReviewArchitecture Communication CanvasArchitecture Decision Record
| Criterion | ![]() Business Strategy Strategy Execution Loop | ![]() Operations After-Action Review | ![]() Architecture Architecture Communication Canvas | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 20-45 min | 60-120 min | 15-45 min |
Participantsdifferent | 5-12 | 3-12 | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Lessons learned, Action items, Event summary | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | ExecutionCadenceLearningGovernance | LearningOperationsImprovement | ArchitectureCommunicationStakeholdersCanvas | ArchitectureRationaleDocumentationGovernance |



