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 |  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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 30-60 min | 20-45 min |
Participantsdifferent | 1-3 | 2-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Fishbone Diagram, Cause Categories, Investigation Backlog | Lessons learned, Action items, Event summary |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeQualityOperations | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
