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 Theory of Constraints |  Operations Bottleneck Analysis |  Operations Kepner-Tregoe |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | High | Medium | High | Low |
Timedifferent | 2-4 h Analyse, laufend | 1-3 h | 2-8 h | 15-30 min |
Participantsdifferent | 3-12 | 3-8 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Problem Analysis, Decision Analysis, Risk Plan | Root cause notes, Countermeasures |
Tagsno overlap | OperationsConstraintsFlowImprovement | FlowMeasurementConstraints | Problem solvingRoot causeDecisionOperations | Root causeIncidentLeanProblem solving |