Theory of Constraints

Find the one constraint that sets the pace, exploit it fully, subordinate everything else, then elevate it.

Time45 min
FormatSmall group
StageMake

Theory of Constraints: what it is and why it works

The Theory of Constraints (TOC) treats a production system as a chain whose output is limited by its weakest link, the constraint. The five focusing steps guide improvement. First, identify the constraint, the resource whose capacity caps total throughput. Second, exploit it: make sure it never waits for material, operators or decisions, and that it only works on good, needed parts, usually by placing a time buffer in front of it. Third, subordinate everything else to its pace, so upstream resources release work only as fast as the constraint consumes it. Fourth, elevate the constraint by adding capacity, offloading work or redesigning. Fifth, when the constraint moves, start again.

TOC works because improvement on a non-constraint does not increase system output; it only moves inventory or idle time elsewhere. Focusing on the single limiting resource concentrates effort where each gained hour becomes an hour of output for the whole plant, and cheap exploitation and subordination steps often deliver large gains before any investment is needed. Drum-buffer-rope scheduling applies the logic: the constraint sets the drum beat, a buffer protects it, and a rope limits release upstream. TOC relies on a bottleneck walk to find the constraint, uses OEE to reveal its losses, and uses WIP control to prevent upstream overproduction.

What you need

A process flow with capacity and load data for each major resource
Observations of queues and starved resources, ideally from a bottleneck walk
Downtime and loss data for the suspected constraint
Release and scheduling rules currently used upstream of the constraint

What you get

An identified constraint with supporting data
Actions to exploit the constraint: buffer, staffing through breaks, quality checks before it
Release and scheduling rules subordinated to the constraint's pace
An elevation option with its cost and expected throughput gain

When to use it

When every workstation is “optimized” and the plant still underdelivers.

How to do it, step by step

Identify the constraint: the resource whose capacity caps total throughput.
Exploit it: never let it starve or sit idle — buffer before it.
Subordinate everything else to its rhythm; other stations follow its drumbeat.
Elevate it: add capacity, offload work or redesign.
Repeat: once elevated, the constraint moves — start again.

Worked example: Unlocking a spray dryer in a food ingredients plant

Illustrative scenario — figures are realistic but not from a real company.

A plant producing powdered dairy ingredients ran mixing, evaporation, spray drying and packing. Management had funded upgrades to the evaporators and packing line, yet shipments stayed around 42 tons per day and customers were on allocation.

The team confirmed that the spray dryer was the constraint: evaporators regularly idled waiting for dryer capacity, and packing waited for powder.
To exploit it, they staggered breaks so the dryer ran through shift changes, moved concentrate quality checks upstream so off-spec feed never reached it, and kept a buffer of approved concentrate ready.
To subordinate, evaporator schedules were set to the dryer's hourly rate instead of running at maximum and then shutting down when tanks filled.
They compared elevation options: a second dryer or debottlenecking the existing one with a larger exhaust fan and improved nozzles.

Result. Exploitation and subordination alone raised output to about 47 tons per day within two months, without capital spending. The debottleneck project added about 5 tons more. Soon afterward the evaporators became the new constraint, and the team started the cycle again. They learned that earlier investments on non-constraints had added capacity nobody could use.

Open it in the FieldKit Supply Chain app → Get the Supply Chain template pack — join the waitlist

Common pitfalls and how to avoid them

Identifying the constraint from utilization reports alone.Confirm it with queues, starved downstream resources and a capacity versus load comparison.
Jumping to elevation, such as buying equipment, before exploiting the existing constraint.First remove idle time, poor-quality input and unnecessary work at the constraint; these are usually cheaper.
Letting non-constraints run at full speed and flood the system with inventory.Tie release upstream to the constraint's pace and accept that non-constraints will have idle time.
Stopping after the first cycle.Check where the constraint has moved and repeat the five steps, including constraints in policy or market demand.

Frequently asked questions

What are the five focusing steps of the Theory of Constraints?

Identify the constraint, exploit it, subordinate everything else to it, elevate it, and repeat when the constraint moves. Goldratt also warned against letting inertia become the constraint, meaning that policies set for the old constraint should be revisited once it moves. The steps apply to physical, policy and market constraints.

What is drum-buffer-rope?

Drum-buffer-rope is a TOC scheduling method. The drum is the constraint, whose schedule sets the pace for the whole system. The buffer is a time or inventory cushion in front of the constraint, protecting it from upstream disruptions. The rope ties the release of new work to the drum's consumption, so upstream resources do not overproduce.

What is the difference between Theory of Constraints and Lean?

Both aim to improve flow, but they start differently. TOC focuses first on the single constraint and on throughput, accepting idle time at non-constraints. Lean aims to remove waste everywhere and create smooth, continuous flow across the value stream. In practice they combine well: TOC shows where to focus first, and Lean tools such as SMED and standard work provide ways to improve there.