
A bottleneck is the stage in a process that limits the throughput of the whole system. It is not necessarily the slowest stage in absolute terms. It is the point whose processing capacity is exhausted first under the current demand and arrangement.
Consider a café that can take orders, collect cups and process payments quickly, while its espresso machine can produce only four drinks per minute. Adding another cashier will not increase the number of finished drinks; it will merely build the queue for preparation faster. Total output may rise only by increasing machine capacity, changing the mix of drinks or reorganising the workflow. The bottleneck may then shift to milk preparation or collection.
A bottleneck differs from latency. Latency asks how long one order takes from beginning to end; a bottleneck concerns how many orders the system can pass through per unit of time. Nor is it identical to general inefficiency: improving waste in a non-bottleneck stage may not raise total output. The concept matters because making one part faster does not necessarily improve the whole. To decide where to intervene, look for the point where work persistently accumulates and identify which capacity actually constrains the next step.
Discover more from Geoffrey Chen
Subscribe to get the latest posts sent to your email.