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 |  Decision Making Constraint Analysis |  Operations 5 Whys |  DevOps Incident Command |
|---|---|---|---|---|
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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 20-60 min | 30-90 min | 15-30 min | As needed |
Participantsdifferent | 1-4 | 2-8 | 2-6 | 4-15 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Root cause notes, Countermeasures | Incident Log, Action Tracker, Stakeholder Updates |
Tagsno overlap | OperationsReliabilityDocumentation | ConstraintsDecisionPlanningOptions | Root causeIncidentLeanProblem solving | IncidentOperationsReliability |