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 After-Action Review |  Operations Runbook |  DevOps Incident Command |
|---|---|---|---|---|
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. | 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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 20-45 min | 20-60 min | As needed |
Participantsdifferent | 1-3 | 3-12 | 1-4 | 4-15 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Lessons learned, Action items, Event summary | Runbook, Checklist, Escalation Path | Incident Log, Action Tracker, Stakeholder Updates |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LearningOperationsImprovement | OperationsReliabilityDocumentation | IncidentOperationsReliability |