What is the Theory of Constraints?
Most improvement effort in most organisations changes nothing, and the reason is uncomfortable: the effort lands somewhere other than the one place that sets the pace. Eliyahu Goldratt built an entire management philosophy from that observation, and had the good sense to publish it as a novel. The Goal(1984) follows a plant manager discovering that his factory’s output is governed not by how hard everyone works but by a small number of bottlenecks, and that every hour lost at a bottleneck is an hour lost to the entire system, while an hour saved anywhere else is largely an illusion.
The chain, not the links
The Theory of Constraints starts from an image simple enough to be dangerous: a system is a chain, and a chain has exactly one weakest link. Strengthen any other link and the chain holds precisely as much as before. In business terms, every system, a factory, a delivery pipeline, a sales motion, has at any moment one constraint (occasionally a few) that governs its throughput. Everything upstream of it can only queue; everything downstream of it can only starve.
The corollary is the part managers resist: if the constraint governs throughput, then improving anything else does not improve the system. Improve the constraint and you improve the business; improve anywhere else and you mostly improve the appearance of the numbers. High utilisation at a non-constraint is not efficiency; it is inventory being manufactured for a queue. Local optima do not add up to a global optimum, which is why an organisation can get measurably better at almost everything and no better at the only thing that pays.
The five focusing steps
Goldratt’s method is a cycle of five steps, and the discipline is in the order:
- Identify the constraint.Find the point that actually limits the system’s output. It is often not where the noise is.
- Exploit it. Before spending anything, get the most out of the constraint as it stands: keep it fed, keep it working on the right things, stop wasting its time on work anything else could do.
- Subordinate everything else. Run the rest of the system at the pace of the constraint and in service of it, even where that means non-constraints sit idle. This is the step organisations find culturally hardest, because it looks like waste.
- Elevate the constraint. Only now invest: add capacity, hire, buy, re-engineer, until the constraint breaks.
- Go back to step one. The constraint has moved somewhere else. Beware inertia: the rules built for the old constraint are now costing you at the new one.
One concrete example
Clearly illustrative, with no customer implied. A consulting firm of a few hundred people cannot start engagements as fast as it sells them. The instinctive diagnosis is a hiring problem, so recruitment accelerates and the bench grows, and start dates do not move. The actual constraint is a review step: every solution design must pass through a small group of senior architects, and their calendars are the narrowest point in the whole system. Exploiting the constraint means protecting those architects from everything that is not design review, and sequencing their queue by value rather than arrival. Subordinating means the sales team stops promising start dates the architect queue cannot honour, and delivery stops booking kick-offs ahead of approved designs. Elevating means training two more architects, at which point the constraint moves, perhaps to client-side approvals, and the firm must notice that it has moved, or it will keep optimising a step that no longer sets the pace.
From throughput to decision dates: the ONX connection
The Theory of Constraints is a theory of flow: it tells you what governs how much a system produces. The same logic, applied to a single commitment rather than a pipeline, tells you what governs when a promise can be kept, and that application has its own entry: why the worst constraint decides. A commitment is ready on the date the last binding constraint clears, not on the average of its dimensions, for exactly Goldratt’s reason: strength elsewhere cannot compensate for the link that fails. In decision intelligence terms, every candidate option carries the earliest date it clears every constraint that binds it, the overall date is set by whichever clears last, and delivery confidence is composed the same way, so the constraint is named before the commitment is made rather than discovered after. Goldratt taught operations to stop averaging a chain. Decision intelligence asks the same of every promise the business signs.
Common questions
What is the Theory of Constraints?
The Theory of Constraints is Eliyahu Goldratt’s management principle that every system has one constraint (occasionally a small number) that governs its overall throughput, the way the weakest link governs the strength of a chain. Improvement effort applied anywhere other than the constraint does not increase what the system produces. The theory’s method is the five focusing steps: identify the constraint, exploit it, subordinate everything else to it, elevate it, and when it moves, start again.
What are the five focusing steps?
First, identify the constraint: find the point that limits the whole system’s output. Second, exploit it: get the most from the constraint as it stands, without new investment. Third, subordinate everything else: run every other part of the system to serve the constraint, even if that leaves other resources idle. Fourth, elevate the constraint: invest to add capacity at that point. Fifth, when the constraint breaks and moves elsewhere, return to step one, and do not let inertia leave old rules in place.
What is the difference between a constraint and a bottleneck?
A bottleneck is the narrow case: a resource whose capacity is less than the demand placed on it. A constraint is the general case: whatever most limits the system’s performance, which may be a bottleneck resource but may equally be a policy, a market, a decision-approval step or the availability of one scarce skill. The Theory of Constraints deliberately uses the wider word, because the thing setting your pace is often not a machine.
Who created the Theory of Constraints?
Eliyahu M. Goldratt, an Israeli physicist turned management thinker, developed the Theory of Constraints and popularised it through The Goal (1984, written with Jeff Cox), a business novel about a plant manager discovering that his factory’s performance is governed by its bottlenecks. Goldratt extended the theory across later books to project management, distribution and strategy.