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 Runbook |  Architecture arc42 |  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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | 30-90 min | 20-60 min | 1-2 Tage | 20-45 min |
Participantsdifferent | 3-12 | 1-4 | 1-4 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Runbook, Checklist, Escalation Path | Architecture Document, Context View, Runtime View, Deployment View | Lessons learned, Action items, Event summary |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | OperationsReliabilityDocumentation | ArchitectureDocumentationCommunication | LearningOperationsImprovement |