Quantitative Methods

The Theory of Constraints and Managing the Bottleneck

One resource sets your throughput. An hour lost there is lost for the whole business; an hour saved anywhere else is worth nothing at all. Learn to find it, run it properly before spending a dollar on it, and rank your products by the only capacity that is scarce.

  • Advanced
  • 13 min total
  • 14 chapters

What decision this helps you make: Where to spend the next improvement dollar and the next hour of management attention — and which products to run when the bottleneck cannot make everything the market wants.

What this topic is

The theory of constraints holds that every system has one resource that limits its output, that the output of the whole system is governed by that resource alone, and that improvement effort anywhere else produces no gain. It supplies five ordered steps for managing that resource, and a decision accounting — throughput accounting — that ranks products by contribution per unit of constrained capacity rather than by margin.

Why it matters

Improvement budgets are typically allocated where a case can be made, which means to whoever writes the best business case, which is almost never the bottleneck. The result is a stream of local efficiency gains that show up in departmental reports and never appear in the output of the business. Naming the constraint changes what gets funded, what gets measured, and — through contribution per constraint minute — which orders you take.

Who should learn it

Plant and operations managers, service delivery leads, agency and professional services partners with a scarce senior resource, and anyone whose improvement programme is producing local wins and flat output.

What you will understand

  • The five focusing steps, and why exploiting the constraint comes before spending money on it
  • How to rank products by contribution per constraint minute, and why margin ranking gives the wrong answer
  • Why the constraint moves after every improvement, and what to do about the step nobody does
  • Where the single-constraint rule is genuinely wrong, and what to use when two resources bind at once

Prerequisites

Common misconception

"Improve everywhere and the system improves." It does not. If a line runs 120, 85, 140 and 100 units a day through four steps, the line produces 85 a day, and a project that doubles the third step's capacity changes output by exactly zero while producing a persuasive efficiency report. The corollary is harsher and less popular: at every non-constraint resource, idle time is not waste. It is the protective capacity that keeps the constraint fed, and eliminating it in the name of utilisation is how a plant ends up with high reported efficiency, growing work-in-progress, and unchanged throughput.