Bottleneck.
aka constraint, choke point, limiting step
The one slow step that quietly holds everything else up.
What it actually means
A bottleneck is the step in a process with the least capacity, the point where work piles up and waits. Because everything has to pass through it, the bottleneck sets the speed of the whole system. Improving any other step barely helps until the bottleneck itself is fixed.
The name comes from the neck of a bottle: however big the bottle, liquid only pours as fast as the narrow neck allows. In a business, the neck might be a machine, a single approver, a slow supplier or one specialist everyone depends on. The clue is usually a queue. Wherever work is waiting in a pile, look just past it. A telltale sign is that people before it are rushed while people after it are often idle, waiting for work to arrive.
The nuance people miss is that speeding up a non-bottleneck step often makes things worse. If the packing station can handle 100 orders an hour but the label printer manages only 60, a faster packing team just builds a bigger pile next to the printer. This idea is central to the theory of constraints, popularized by the business novel The Goal by Eliyahu Goldratt. Also, bottlenecks move. Fix one, and the next slowest step becomes the new limit.
Where you'll hear it
Design and development are on schedule, but legal review is the bottleneck. Every contract waits about a week for one person, so the launch date depends on that queue.
Translation: everyone else is fine. One overloaded step is setting the pace, so that is where help or a new process is needed.
Also in tech, where a slow database query or limited bandwidth can bottleneck an app, in hiring, where a single interviewer slows every offer, and in supply chains, where one port, factory or component can delay products all over the world. In each case the fix starts with the same question: where does the waiting happen?
The pop-culture version
Thousands of people arrive at a festival. The car park is huge, the shuttle buses are frequent, and inside there are five stages and dozens of food stalls. But there is only one working turnstile at the gate. Shuttles drop off a new busload every few minutes.
It does not matter how many buses run or how many stages are waiting. Everyone gets in at the speed of that turnstile. Adding more buses just makes the crowd outside the gate bigger and grumpier. Meanwhile the stage crews inside stand around, ready for a crowd that has not arrived yet.
The fix is not more buses. It is more gates, faster ticket scanning or staggered arrival times. That is how bottlenecks work in any process: find the narrowest point, widen it, and only then think about the rest.
The practical rule: when work feels slow, look for where things wait in a pile. Fix that step first, then check where the new pile forms, because that is your next bottleneck.
Say it like you mean it
“Approvals are the bottleneck, so let us give a second manager sign-off rights for orders under a set amount.”
It names the exact slow step and proposes a fix that increases its capacity.“Everything is a bottleneck in this project.”
By definition, a process usually has one main bottleneck at a time; calling everything one hides the real cause.You may also hear "we are the bottleneck," said by a team that knows others are waiting on it. Saying it openly is a good sign. It usually opens a conversation about priorities, extra help or simplifying the work. Good teams treat it as a shared problem to solve, not as someone to blame.
A review of Goldratt's The Goal, unpacking bottlenecks, throughput and the theory of constraints, and what they teach about smarter procurement decisions.
Decoded next
Decoded by the Kurums editorial team. Kurums Decoded translates the language of business for people who are new to it. Definitions are kept short on purpose; the serious version above goes deep. Nothing here is financial, legal or career advice.
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.
