Bottleneck
Why it matters
Effort spent anywhere else is largely wasted. Speeding up a step that is not the bottleneck only piles more work in front of the one that is. Output stays where it was. Speeding up the real bottleneck moves everything. This idea comes from the Theory of Constraints, set out by Eliyahu Goldratt in his 1984 book The Goal.
Founders often work on the step they find most interesting or most visible, not the one holding growth back.
What it is
Any process is a chain of steps, and the slowest one decides how much gets through. Picture a motorway where three lanes narrow to one. It does not matter how fast traffic moves before or after the narrow point, because the narrow point sets the flow.
Four terms circle this idea, so here is how they fit. The Theory of Constraints is the method. A constraint is whatever limits the system. The bottleneck is the step where that limit shows up as a queue. The Bottleneck Resource is the scarce person, tool or capacity behind that step. This page is the one to start from.
In a business the chain might be the path from first visitor to retained customer. Say there are plenty of leads and a good close rate, but every deal waits for the one senior person who can run technical calls. That step is the bottleneck, and the whole pipeline moves at its pace.
Common mistakes
- Fixing the step that feels most broken instead of the one that measures slowest.
- Declaring victory after one fix, when the constraint has simply moved.
How to find and fix it
- Map the process end to end and measure how long work waits at each step, not how busy each step looks.
- Find the step where work piles up waiting. That is usually the constraint.
- Protect that step from interruptions and from work someone else could do.
- Keep it fed, so it never sits idle waiting for an earlier step.
- Raise its capacity, for example by training a second person or adding a tool.
- Measure again. Fixing one bottleneck usually reveals the next.
