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 Runbook |  Delivery RAID Log |  DevOps Blameless Postmortem |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 20-60 min | 30 min Setup, dann laufend | 30-90 min | 15-45 min |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 3-12 | 1-3 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | Runbook, Checklist, Escalation Path | RAID Log, Status Report Source | Postmortem Doc, Action Items, Timeline | ADR File, Decision Log, Rationale |
Tagsno overlap | OperationsReliabilityDocumentation | RiskTrackingStakeholdersGovernance | Site Reliability EngineeringIncidentLearningReliability | ArchitectureRationaleDocumentationGovernance |