Bottleneck — A bottleneck is the step in a process that limits the overall throughput of the system.
In plain English
A bottleneck is the step in a process that limits the overall output of the system.
It doesn’t matter how fast everything else runs.
The bottleneck decides the pace.
If one step can only process 10 units per hour, the entire system is capped at 10 units per hour.
You can improve every other step.
It won’t increase total output.
What they actually mean
Most organizations think they have multiple bottlenecks.
They don’t.
They have one true constraint at a time.
But instead of identifying it, they:
• Improve everything slightly
• Run optimization projects everywhere
• Increase utilization across departments
Which usually increases chaos.
The bottleneck doesn’t care how busy everyone else is.
It only cares about capacity.
Improving non-bottlenecks feels productive.
Improving the bottleneck feels uncomfortable — because it exposes trade-offs.
Example
A production line has five steps.
Four can produce 100 units per hour.
One can produce 60.
The system output is 60.
If you increase the four fast steps to 120 per hour:
Nothing changes.
If you increase the bottleneck from 60 to 70:
The entire system improves.
This is why local efficiency is misleading.
🔗 Cycle Time
🔗 Flow
Where you’ll hear it
Operations meetings, Lean workshops, crisis reviews — and anytime someone says:
“We just need everyone to work harder.”
Does it actually matter?
✅ Yes.
The bottleneck determines:
• Throughput
• Lead time
• Delivery stability
• System stress
If you ignore the bottleneck, improvements scatter.
If you focus on it, improvements compound.
Common misconceptions
“We have multiple bottlenecks everywhere.”
You can have many problems — but usually only one true bottleneck at a time.
“Fixing bottlenecks means working faster.”
It usually means working differently — or reducing demand upstream.
“If everyone is busy, there is no bottleneck.”
High utilization often creates bottlenecks.
“Bottlenecks move randomly.”
They move predictably when the system changes.
The slowest machine is always the bottleneck.
Sometimes it’s a policy, approval, or decision layer.
If everyone improves, the system improves.
Only if the constraint improves.
Red flags
🚩 Every department runs separate efficiency projects.
🚩 Utilization is maximized everywhere.
🚩 Work piles up before one specific step.
🚩 Urgent jobs always “get stuck” in the same place.
🚩 Lead time keeps increasing despite productivity gains.
Worth learning?
5/5
If you understand bottlenecks, you stop wasting energy.
Deep dive
The constraint is a system property
A bottleneck is not a bad department.
It’s a system imbalance.
Constraints can be:
• Physical (machine capacity)
• Human (skill limitations)
• Policy-based (approvals, rules)
• Market-based (demand limitations)
The goal is not to eliminate all bottlenecks.
That’s impossible.
The goal is to manage the constraint intentionally.
The five focusing steps (Theory of Constraints)
1. Identify the constraint.
2. Exploit it (use it efficiently).
3. Subordinate everything else to it.
4. Elevate it (increase capacity).
5. Repeat when it shifts.
Most companies skip step 3.
They elevate everything.
Which increases cost without increasing throughput.
Why bottlenecks shift
When you improve a constraint, another step becomes the new limiter.
That’s normal.
The system evolves.
Continuous improvement isn’t about removing constraints.
It’s about managing the right one.
Report an error
Found something wrong or misleading? Let us know — we want this site to stay fact-based (even when we joke).