Skip to content
Systems & Complexity

Bottlenecks (Systems)

Model #1009Category: Systems & ComplexityDepth to apply:

By Updated

4 min read
Systems & Complexity
Section 1

Core Idea

A bottleneck is the narrowest point in a system — the constraint that limits the throughput of everything downstream. In a factory, it's the slowest machine. In an organisation, it's the approval that everything waits on. The key insight: optimising any part of the system other than the bottleneck produces zero improvement in total output. Adding capacity before the bottleneck just creates larger queues at the constraint. Adding capacity after it leaves resources idle. The only leverage is at the bottleneck itself. This means the first job of any systems thinker is identification — finding the single point that governs the whole.

Get Faster Than Normal by email

Ideas from founders and companies.

Free newsletter. Unsubscribe anytime.

Or open the full subscribe page.

Section 2

How to See It

Operations
You're seeing it when your engineering team ships features fast but every release waits two weeks for a single QA engineer's approval. The bottleneck isn't engineering velocity — it's the QA stage that governs total throughput.
Growth
You're seeing it when you double your marketing spend but revenue barely moves because your sales team can't handle more inbound leads. The bottleneck is sales capacity, not demand generation.
Section 3

How to Use It

Map your system end to end and measure throughput at each stage. The stage with the longest queue or the lowest processing rate is your bottleneck. Focus all improvement efforts there first. Only when that constraint is elevated should you look elsewhere. Resist the temptation to optimise the parts that are easiest to improve — optimise the part that matters.
Decision filter
"Where is the constraint that limits total system output? Am I investing resources at the bottleneck, or somewhere that won't change the outcome?"
As a founder
Identify the single biggest constraint in your company right now. Is it hiring? Sales capacity? Product velocity? Ship speed? Focus disproportionate resources on that one constraint. Everything else is noise until the bottleneck moves.
Section 5

Founders & Leaders

Elon MuskCEO, Tesla and SpaceX
Musk's approach to Tesla manufacturing was a masterclass in bottleneck thinking. During Model 3 production hell, he personally moved onto the factory floor to identify constraints. He discovered the bottleneck wasn't the main assembly line but the battery module production in the "tent" — a single sub-process that governed the entire factory's output. He redirected engineers, redesigned the process, and slept at the factory until throughput at that stage improved. Once the battery bottleneck broke, overall production surged. Founders should learn: when output stalls, resist the instinct to push everything harder. Find the one constraint, break it, then find the next one. Systems improve sequentially through their bottlenecks, never uniformly.
Section 7

Connected Models

Reinforces
Theory of Constraints
Theory of Constraints formalises bottleneck thinking into a management discipline: identify, exploit, subordinate, elevate, repeat. Bottlenecks (Systems) provides the diagnostic lens; Theory of Constraints provides the action framework.
Pairs-with
[Throughput](/mental-models/throughput)
Throughput measures the rate at which a system produces output. Bottlenecks determine the ceiling of throughput. You cannot increase throughput without addressing the bottleneck that caps it.
Tension
[Slack](/mental-models/slack)
Slack advocates for excess capacity as a buffer. Bottleneck thinking focuses on eliminating constraints. The tension: you need slack everywhere except the bottleneck, where you need maximum utilisation.
Section 8

One Key Quote

"A chain is no stronger than its weakest link."
Eliyahu Goldratt
Section 11

Summary & Further Reading

A bottleneck is the single constraint that limits total system output. Optimising anything other than the bottleneck is waste. The discipline is identification first, then focused improvement at the constraint — repeated as each bottleneck is elevated and the next one emerges.

Why this matters next

Frequently asked questions

What is Bottlenecks (Systems)?

Bottlenecks (Systems) is a mental model used for better thinking and decision-making.

How do you apply Bottlenecks (Systems)?

To apply Bottlenecks (Systems), identify situations where this framework is relevant, then use it as a lens to evaluate your options and decisions. The model is most useful when combined with other complementary mental models.

What category does Bottlenecks (Systems) fall under?

Bottlenecks (Systems) falls under the Systems & Complexity category of mental models. Other models in this category can be found on the Systems & Complexity hub page.

Why is Bottlenecks (Systems) important?

Bottlenecks (Systems) is important because it provides a structured way to think about problems that would otherwise be approached with intuition alone. Understanding this model helps you avoid common reasoning errors and make better decisions.

Continue exploring

Get Faster Than Normal by email

Ideas from founders and companies.

Free newsletter. Unsubscribe anytime.

Or open the full subscribe page.

Popular Mental Models