Bottlenecks

The resource whose capacity is less than the demand placed on it. A bottleneck, the constraint, sets the maximum throughput of the entire system: everything downstream waits on it and everything upstream piles up before it.

Why it Matters

A system's output is governed by its single binding constraint, not by the average or total capacity of its parts. An hour lost at the bottleneck is an hour lost for the whole system; an hour saved at a non-bottleneck is worthless.

Signals

• Work piling up in front of one step while others sit idle.
• That step always busy; expediting and overtime concentrated there.
• Adding capacity elsewhere not improving output.

Benefits

Focuses limited improvement effort where it actually changes the result, and clarifies why broad efficiency drives don't help.

Risks

Improving non-bottlenecks because it feels productive while changing nothing; failing to notice the constraint has moved; protecting local efficiency metrics that hide the real limit.

Tensions

Keeping every resource fully utilized conflicts with throughput: non-bottlenecks must sometimes sit idle so the bottleneck never starves. Utilization is not productivity.

Examples

The slowest machine on a line capping daily output; a single review or approval step gating an entire delivery pipeline; the slowest hiker setting the pace of the whole group.