The bottleneck
rate limiter · theory of constraints
The single constraint that sets the pace of a whole system. Improving anything other than the bottleneck makes the system busier without making it faster, which is why most improvement efforts change nothing.
In practice
Five people can deliver twelve projects a month and every proposal needs your signature. The business delivers what you can review, and hiring a sixth person changes nothing.
The common mistake
Improving the part of the process you understand best. Unless it is the constraint, the gain is absorbed by the queue and total output is identical.
The bottleneck is the single step that limits the output of an entire system. Every system has one, and only one at a time.
Why only one matters
Output is set by the slowest step. Work arriving faster than that step can process it queues in front; capacity after it sits idle waiting. Improving any step that is not the bottleneck changes nothing about what comes out the other end.
This is why effort so often produces no result. A team works hard, every individual is busy, several functions get measurably faster, and total output is unchanged — because none of the improvements touched the constraint.
Finding it
The bottleneck is where work piles up. In a factory it is inventory in front of a machine. In a business it is a queue: proposals waiting for approval, code waiting for review, clients waiting for onboarding, decisions waiting for one person.
In most small businesses the bottleneck is the owner's attention. Everything routes through one calendar, and the business produces at the rate that calendar allows. See owner dependency.
The sequence
Work on it in order, because the cheap steps come first:
- Identify where the queue is.
- Exploit it — get more from the constraint without spending. Stop it doing work that something else could do, remove interruptions, keep it supplied so it never waits.
- Subordinate everything else to it. Other steps should run at the constraint's pace rather than their own maximum, which feels wrong and stops the system manufacturing work in progress.
- Elevate it by adding capacity — hire, buy, automate.
- Repeat, because relieving one constraint always moves it somewhere else.
The final step is what makes this a practice. There is always a bottleneck; the work is knowing where it currently sits, because it moves. See The Goal and four bottlenecks.
The reason the constraint always moves is diminishing returns. Relieving a constraint means feeding one input while the others stay fixed, and each addition then buys less than the one before it until something else becomes scarce. A bend in the curve is not a signal to stop. It is a signal that the bottleneck has moved, and continuing to feed the input that used to work is the shape of most plateaus.
Concept web
Open the full webQuestions
What is a bottleneck in business?
The single step that limits the output of the whole system. Work queues in front of it and capacity after it sits idle, so total output matches the bottleneck's rate regardless of other improvements.
How do you find the bottleneck?
Look for where work accumulates — proposals awaiting approval, clients awaiting onboarding, decisions awaiting one person. In small businesses it is usually the owner's available attention.
What happens after you fix a bottleneck?
The constraint moves to a different step. There is always a bottleneck somewhere, so the work is identifying its current location rather than eliminating it permanently.