View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Operations A3 Problem Solving |  Operations Gemba Walk |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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 | Medium | Low | Low |
Timedifferent | 30-90 min | 45-90 min | 30-120 min | 20-45 min |
Participantsdifferent | 3-12 | 2-5 | 2-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | A3 Report, Action Plan, Root Cause Analysis | Observation Notes, Improvement Ideas | Lessons learned, Action items, Event summary |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | LeanProblem solvingCoachingOperations | LeanObservationProcessOperations | LearningOperationsImprovement |