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 |  Operations Failure Mode and Effects Analysis |  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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 | High | Low |
Timedifferent | 20-60 min | 30 min Setup, dann laufend | 2-6 h | 15-45 min |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 3-10 | 1-3 |
Formatdifferent | Async | Async | Workshop | Async |
Outputdifferent | Runbook, Checklist, Escalation Path | RAID Log, Status Report Source | FMEA Table, Risk Priority, Mitigation Actions | ADR File, Decision Log, Rationale |
Tagsno overlap | OperationsReliabilityDocumentation | RiskTrackingStakeholdersGovernance | RiskQualityOperationsRoot cause | ArchitectureRationaleDocumentationGovernance |