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 Incident Command |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 20-60 min | 30 min Setup, dann laufend | As needed | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 4-15 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | RAID Log, Status Report Source | Incident Log, Action Tracker, Stakeholder Updates | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | OperationsReliabilityDocumentation | RiskTrackingStakeholdersGovernance | IncidentOperationsReliability | ArchitectureQualityRiskTradeoffsStakeholders |