Most improvement programmes spread effort across the entire value stream. The theory of constraints says the opposite: every organisation must have at least one constraint, and improving anything other than that constraint changes nothing at the system level. That single idea, applied consistently, turns TOC from a bottleneck-finding exercise into a prioritisation discipline. It tells you where not to spend improvement effort, which is the harder and more valuable lesson.
What is the theory of constraints?
TOC is an organisational change method focused on profit improvement. It defines a constraint as any factor that limits the organisation from getting more of whatever it strives for, which is usually profit.
The model is a chain. TOC conceptually models the organisation as a chain and applies the familiar principle that a chain is only as strong as its weakest link. Strengthening any other link does nothing for the chain's overall capacity. All of TOC flows from that observation.
Who invented it, and why it came from physics
The theory of constraints was developed by Eliyahu M. Goldratt (1947 to 2011), who introduced it in his 1984 book The Goal. The book was a best-selling novel, rare for business and management theories, and it became a bestseller in the 1980s that has influenced countless businesses worldwide.
What made Goldratt's perspective unusual was its origin. TOC originated from Goldratt's background in physics and his understanding of systems thinking, not from manufacturing tradition. A physicist looks at a production line the way they look at any system: find the binding constraint, and everything else is secondary. That lens was new to manufacturing managers trained to optimise each department independently.
Today, TOC is included in the curricula of more than two hundred institutions of higher learning.
The key insight: improving a non-constraint changes nothing
This is the part most summaries rush past.
Goldratt's insights shifted the focus from optimising individual processes to improving the entire system by addressing its constraints. If your paint booth runs at 40 units per hour and your assembly line runs at 100, speeding up assembly to 120 produces exactly zero additional output. You just build work-in-progress inventory faster.
Constraints are not always machines. They are not limited to elements within the company. A constraint might well be in the form of a market competitor. It could be a policy, a sales capacity limit, or market demand itself. Recognising that a constraint can be external changes where you direct your improvement projects entirely.
The five focusing steps
TOC's practical method is a five-step cycle that concentrates all effort on the constraint.
1. Identify the system constraint
Find the weakest link. Business owners should look for areas that have an excess of work in progress. Equipment, tools, and electronic systems merit attention because all of these elements, if not working properly or consistently, or if they have redundancies, can negatively influence efficiency. Where WIP piles up, the constraint sits just downstream.
SimplicityHub's bottleneck analysis template gives you a structured format for this step: mapping each process stage, logging queue sizes, and flagging the stage where throughput drops.
2. Exploit the constraint
Before spending money, squeeze more from what you have. Goldratt instructs the change agent to obtain as much capability as possible from a constraining component, without undergoing expensive changes or upgrades. An example is eliminating downtime on the bottleneck operation. If the constraint machine sits idle during shift changes or waits for materials, fixing those gaps is free capacity.
3. Subordinate everything else
Adjust non-constraint processes to serve the bottleneck. This is the step that feels counterintuitive. It may mean deliberately slowing a faster upstream process so it stops flooding the constraint with WIP. The non-constraint components of the system must be adjusted to a setting that will enable the constraint to operate at maximum effectiveness.
Understanding your cycle time vs takt time vs lead time relationships matters here. If a non-constraint stage has a cycle time far below takt, it is overproducing relative to the constraint's capacity.
4. Elevate the constraint
Only now do you invest capital. Elevating the constraint refers to taking whatever action is necessary to eliminate the constraint. This step is only considered if steps two and three have not been successful. Buy the second machine, hire the extra shift, or redesign the process, but only after you have proven that exploitation and subordination are not enough.
5. Repeat (and beware inertia)
Once the constraint is broken, a new one emerges somewhere else. Return to step one. Goldratt cautions practitioners about becoming complacent. TOC is an ongoing process, and the inertia that can build up after a change occurs can actually serve to prevent continuous improvement.
The good news: most organisations have very few true constraints. Since the focus only needs to be on the constraints, implementing TOC can result in substantial improvement without tying up a great deal of resources, with results after three months of effort.
The three TOC measurements: Throughput, Inventory, Operating Expense
This is where TOC diverges most sharply from conventional management. Goldratt correctly realised that conventional accounting systems do not support TOC, or lean-based efforts. Standard cost accounting rewards local efficiency (keep every machine busy, absorb overhead into unit cost), which directly contradicts the subordination step above.
Goldratt proposed replacing all traditional measures derived from the product cost accounting paradigm with three measures:
| Measure | Definition |
|---|---|
| Throughput (T) | The rate at which the entire organisation generates money through sales |
| Inventory (I) | All the money the organisation invests in things it intends to sell |
| Operating Expense (OE) | All the money the organisation spends turning Inventory into Throughput |
The formula: maximise Throughput while minimising Inventory and Operating Expense. All improvement opportunities should be prioritised by their effect on these three measures, especially Throughput, for which the only limit on how high it can be increased is market size.
That reframing matters. Cost reduction has a floor (you cannot cut below zero). Throughput does not.
The three underlying principles
TOC rests on three core principles:
- Convergence highlights the interconnectedness of business systems. A change in one area ripples through others, which is why local optimisation fails.
- Consistency addresses the importance of clear communication and assumptions. If different departments measure success differently, they will optimise in conflicting directions.
- Respect recognises employees' potential for improvement and contribution to the organisation. The people closest to the constraint usually know what is wrong before management does.
These principles underpin the methodology's "thinking process," which poses three questions: What to change? What to change to? How to cause the change? Those questions frame every TOC project from diagnosis through implementation.
TOC vs Lean: same goal, different lever
Both TOC and Lean aim at profit improvement. The difference is which side of the equation they pull.
The objective of lean thinking, as with TOC, is to increase profit. Lean uses the equation Profit = Selling Price - Cost, and since selling price is dictated by the market, Lean focuses on reducing cost. TOC focuses on increasing throughput.
| Theory of Constraints | Lean | |
|---|---|---|
| Primary lever | Increase Throughput | Reduce Cost |
| Starting point | Find the constraint | Map the value stream |
| Scope of change | Constraint only (then repeat) | Entire flow |
| Accounting model | T, I, OE | Standard cost / value stream costing |
| Speed to results | ~3 months for initial gains | Varies by scope |
They complement each other. TOC tells you where to focus. Lean gives you the toolkit (5S, standard work, pull systems) to execute once you know the target. Running Lean across every process without identifying the constraint first risks improving a non-bottleneck, which TOC would call wasted effort.
Where TOC is applied today
TOC started in manufacturing, but today the constraints theory applies in all sorts of manufacturing and development areas, including lean, agile, and more. Software teams use it to find deployment bottlenecks. IT operations teams apply it to incident queues. Project managers use Critical Chain (a TOC derivative) to schedule around the scarcest resource.
The principle holds regardless of industry: no system is free from constraints, but constraints can be managed. The question is never whether you have one. It is whether you know which one it is, and whether your improvement effort is pointed at it or at something else entirely.