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 |  Architecture Views and Beyond |  Operations Learning Review |  Operations Runbook |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-90 min | 1-3 Tage | 1-3 h | 20-60 min |
Participantsdifferent | 3-12 | 1-4 | 3-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Architecture Views, Cross-view Notes, Rationale | Learning Review Notes, System Factors, Improvement Actions | Runbook, Checklist, Escalation Path |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | DocumentationStakeholdersArchitecture | LearningRetrospectiveIncidentOperations | OperationsReliabilityDocumentation |