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 Bottleneck Analysis |  DevOps Game Day |  Operations 5 Whys |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-3 h | Halber Tag | 15-30 min | 2-4 h Analyse, laufend |
Participantsdifferent | 3-8 | 5-20 | 2-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Simulation Notes, Gaps List, Updated Runbooks | Root cause notes, Countermeasures | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowMeasurementConstraints | ResilienceOperationsIncident | Root causeIncidentLeanProblem solving | OperationsConstraintsFlowImprovement |