A bottleneck is the narrowest point in a system – the limiting factor that restricts output. Like the neck of a bottle that limits how fast liquid flows, bottlenecks constrain how much value a system can produce.
They aren’t always obvious. A person who insists on making every decision becomes a human bottleneck. a worn-out tool, a slow database query, or a lack of skilled labor can block the entire system. What matters is not effort or capacity elsewhere – but what can pass through the most restricted point.
Bottlenecks tend to create waste. They cause backups, build pressure, and absorb resources. As Shane Parrish writes in The Great Mental Models Vol. 3:
“Every system has a bottleneck. You cannot completely eliminate them because once you do, another part of the system will become the new limiting factor. You can, however, anticipate bottlenecks and plan accordingly… Sometimes you can overcome bottlenecks by adding more of the same, such as dedicating more resources to ease the pressure on a bottleneck. But sometimes the sole solution is to rethink that part of the system.”
While bottlenecks seem problematic, Parrish argues against that mentality. Instead, he concludes the following:
“Although we tend to view bottlenecks as something negative, they can nudge us toward new ideas and better ways of solving the same problems. Using bottlenecks as a mental model not only helps us conceptualize them in the literal sense when looking at a system but also teaches us that they are not something to fear.”
Applications
In manufacturing, 
one faulty machine within the assembly line cuts production across-the-board. In startups, a founder who refuses to delegate delays every decision. In tech startups, bottlenecks often hide within the code. Consider a fast growing app that slows during peak hours. The problem isn’t the team, the server count, or the interface – it’s a single poorly optimized database query. That query becomes the constraint on growth.
In personal productivity, the bottleneck might be energy. You have time, tools, and motivation – but poor sleep ruins output. Fixing time management wont’ help if the true issue is physical recovery. False dependencies also may appear: “I’ll launch my project once I build the perfect website.” But often, the real constraint is fear of judgment or lack of clarity – not the tech.
How to Apply
- Identify the Bottleneck: Find the slowest, most overloaded, or most failure-prone part of the system.
- Validate it’s Real: Ask if it’s a constraint (unmovable) or a bottleneck (fixable). Don’t waste energy solving the wrong issue.
- Watch for Shifting Constraints: If you fix one bottleneck, another may appear. Systems adapt – so should you.
- Avoid False Dependencies: Don’t let excuses masquerade as bottlenecks. Question all assumptions.
- Anticipate Problems: Simulate systemic stress; find where the system breaks before it matters.
- Track Side Effects: Don’t trade one problem for a worse one later.
- Use Bottlenecks to Drive Innovation: Nylon, synthetic rubber, and wartime medicine were all born from constraints and shortages.