Bottleneck
A bottleneck is the single constraint that limits the output of an entire system — the narrowest point through which everything must pass. The theory of constraints holds that improving anything except the bottleneck does nothing for overall throughput.
✦ Widely referenced — cross-referenced 7× across this reference (1 related ideas · 6 hubs) · The State of Thinking 2026 →
How it works
Find the one step, resource, or factor that caps the whole system’s output, then focus all improvement there. Optimising non-bottlenecks is wasted effort — the system can only move as fast as its slowest constraint allows.
Almost all improvement effort is wasted because it lands on the 90% that isn't the constraint.
How to use it
- Diagnosing why a process is slow — find the single limiting step, not the busy-looking ones.
- Directing improvement effort at the constraint, where it actually raises throughput.
- Recognising that a chain is only as strong as its weakest link.
Worked example
A factory line runs at the speed of its slowest machine. Speeding up every other machine just piles up inventory in front of the slow one — output doesn’t rise at all until you fix the bottleneck itself. Then a new bottleneck appears elsewhere.
Where it fails
Bottlenecks move — fix one and another appears, so it’s a continuous process, not a one-time fix. And the visible bottleneck isn’t always the real one; mistaking a symptom for the constraint wastes the effort the model is meant to focus.
- The theory presumes one dominant constraint; in loosely coupled systems several near-equal limits share control, and no single fix moves throughput much.
- Maximizing flow through the constraint can sacrifice quality, resilience, or people — throughput is not the only objective a system serves.
- It applies cleanly to flow systems with sequential steps; creative or exploratory work often has no stable 'narrowest point' to find.
How to apply it, step by step
- Map the flow of work end to end and measure where queues pile up.
- Confirm the constraint: it is the step whose pace sets total output, not the loudest complaint.
- Squeeze more from the bottleneck before adding capacity — remove idle time, defects, and non-essential load.
- Subordinate everything else to it: upstream must never starve it, downstream never block it.
- Once throughput rises, re-map the system — the constraint has probably moved.
The deeper point
It is the antidote to "work on everything" — in any system, almost all improvement effort is wasted because it lands on non-constraints. The discipline is to ignore the 90% that isn’t the bottleneck, even when it’s the part that’s easiest or most fun to improve.
Frequently asked
- What is a bottleneck?
- It’s the single constraint that limits an entire system’s output — the narrowest point everything must pass through. A system can only move as fast as its bottleneck allows, however efficient the other parts are.
- What is the theory of constraints?
- It’s the principle that every system has one limiting constraint (bottleneck), and improving anything except that constraint does nothing for overall throughput. Focus all improvement on the bottleneck.
- Why does fixing non-bottlenecks not help?
- Because the system’s output is capped by the bottleneck. Speeding up other steps just creates a pile-up in front of the constraint — total throughput stays the same until the bottleneck itself is improved.
Related
Keep reading
Lao Tzu
Water seeks the low place and still wears away stone — the case for strength found in softness.
See this alongside the other thinking tools of building a startup, product management, leadership & managing people, learning, software engineers and productivity.
The books behind better thinking
Listen to any of these free. Start a free Audible trial and get your first audiobook on the house.
Prefer to read? The canonical picks:
- Thinking, Fast and Slow — Daniel Kahneman
- The Art of Thinking Clearly — Rolf Dobelli
- The Great Mental Models, Volume 1 — Shane Parrish
- Poor Charlie’s Almanack — Charlie Munger
- Super Thinking — Gabriel Weinberg & Lauren McCann
- Seeking Wisdom — Peter Bevelin
As an Amazon Associate, ReadGlobe earns from qualifying purchases and Audible trials — at no extra cost to you.
Cite this page
ReadGlobe. (2026). Bottleneck. https://readglobe.com/model/bottleneck/
"Bottleneck." ReadGlobe, 29 May 2026, readglobe.com/model/bottleneck/.
Primary source: Wikipedia
Editorial synthesis © ReadGlobe 2026, drawing on the mental-models tradition (Charlie Munger, Farnam Street) and the primary sources for each model. · Last reviewed 2026-05-29.