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 | ![]() Innovation Design Sprint | ![]() 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. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | 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 | High |
Timedifferent | 1-3 h | 4-5 Tage | 2-4 h Analyse, laufend |
Participantsdifferent | 3-8 | 5-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Prototype, Test Findings, Decision Rationale | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowMeasurementConstraints | Design sprintPrototypeValidationInnovation | OperationsConstraintsFlowImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






