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 |  Architecture Architecture Decision Record |  Operations Fishbone Diagram |  Operations After-Action Review |
|---|---|---|---|---|
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. | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 15-45 min | 30-60 min | 20-45 min |
Participantsdifferent | 5-12 | 1-3 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | ADR File, Decision Log, Rationale | Fishbone Diagram, Cause Categories, Investigation Backlog | Lessons learned, Action items, Event summary |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureRationaleDocumentationGovernance | Root causeQualityOperations | LearningOperationsImprovement |