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 Fishbone Diagram |  Business Strategy Strategy Execution Loop |  Operations After-Action Review |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 15-45 min | 30-60 min | Initial 3-6 h, then monthly or quarterly reviews | 20-45 min |
Participantsdifferent | 1-3 | 2-8 | 5-12 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Fishbone Diagram, Cause Categories, Investigation Backlog | Execution Loop, Review Cadence, Strategic Learning Log | Lessons learned, Action items, Event summary |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeQualityOperations | ExecutionCadenceLearningGovernance | LearningOperationsImprovement |