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 Fishbone Diagram |  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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-60 min | 30 min Setup, dann laufend | 30-60 min | 15-45 min |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 2-8 | 1-3 |
Formatdifferent | Async | Async | Workshop | Async |
Outputdifferent | Runbook, Checklist, Escalation Path | RAID Log, Status Report Source | Fishbone Diagram, Cause Categories, Investigation Backlog | ADR File, Decision Log, Rationale |
Tagsno overlap | OperationsReliabilityDocumentation | RiskTrackingStakeholdersGovernance | Root causeQualityOperations | ArchitectureRationaleDocumentationGovernance |