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 A3 Problem Solving |  Operations Runbook |  Operations After-Action Review |  DevOps Incident Command |
|---|---|---|---|---|
Purposedifferent | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 45-90 min | 20-60 min | 20-45 min | As needed |
Participantsdifferent | 2-5 | 1-4 | 3-12 | 4-15 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Runbook, Checklist, Escalation Path | Lessons learned, Action items, Event summary | Incident Log, Action Tracker, Stakeholder Updates |
Tags1 shared | LeanProblem solvingCoachingOperations | OperationsReliabilityDocumentation | LearningOperationsImprovement | IncidentOperationsReliability |