Skip to content

Bottleneck Identification (Theory of Constraints)

Why It Matters

Most optimization effort is wasted on non-constraints. Finding the true bottleneck focuses effort where it matters.

The Key Move

Trace the flow through the system. Where does work pile up? Where do things wait? The queue forms before the bottleneck, not after. Improve only that constraint until it's no longer the bottleneck; then find the new one.

Classic Application

Manufacturing. A factory's output is determined by its slowest machine. Speeding up other machines just builds work-in-progress inventory before the slow one.

Surprising Application

Personal productivity. Your output is constrained by one binding factor - maybe deep work time, maybe decision fatigue, maybe a key collaborator's availability. Optimizing non-constraints (better todo apps, faster typing) doesn't move throughput.

Failure Modes

  • Optimizing what's easy to measure rather than what constrains
  • Assuming the bottleneck is obvious (often it's hidden)
  • Treating all constraints as equal
  • Relieving a constraint without preparing for the next one to become binding

Go Deeper

Goldratt's "The Goal" (novel form, surprisingly readable). Theory of Constraints literature.