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 Learning Review |  Architecture Architecture Decision Record |  Operations Runbook |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 15-45 min | 20-60 min | 20-45 min |
Participantsdifferent | 3-10 | 1-3 | 1-4 | 3-12 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path | Lessons learned, Action items, Event summary |
Tagsno overlap | LearningRetrospectiveIncidentOperations | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation | LearningOperationsImprovement |