View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations After-Action Review |  Business Strategy Strategy Execution Loop |  Architecture C4 Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Low | High | Low | Low |
Timedifferent | 20-45 min | Initial 3-6 h, then monthly or quarterly reviews | 1-4 h | 15-45 min |
Participantsdifferent | 3-12 | 5-12 | 1-5 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Lessons learned, Action items, Event summary | Execution Loop, Review Cadence, Strategic Learning Log | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | LearningOperationsImprovement | ExecutionCadenceLearningGovernance | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |