Operations · System Thinking

Lean and TOC: rivals or partners?

Mohit Saini · 26 Oct 2019 · 4 min read

Lean and TOC: rivals or partners?

Whenever I talk about Theory of Constraints in a plant that already runs a Lean programme, one question comes up within the first ten minutes: “We already do Lean. Why do we need TOC?” Sometimes it comes the other way round: “We tried Lean. It didn’t work. Is TOC the replacement?”

Both questions assume the two are competitors. In my experience, that assumption causes more confusion than any difference between the methods themselves.

What each one asks

The simplest way to see the difference is to look at the first question each approach asks.

  • Lean asks: Where is the waste? Overproduction, waiting, transport, excess inventory, motion, over-processing and defects. Then it removes that waste through value-stream mapping, 5S, set-up reduction, standard work, kaizen and pull systems.
  • TOC asks: What limits the whole system from getting more of its goal? Then it focuses all effort on that one point (the constraint) through the Five Focusing Steps, and makes the rest of the system subordinate to it.

Both care about flow. Both dislike excess inventory. Both reject the idea that every machine should be kept busy. They are much closer than their supporters sometimes admit.

Where Lean programmes often struggle

I have seen many Lean programmes deliver real gains in specific areas: cleaner shop floors, faster changeovers, fewer defects. But I have also seen a common pattern:

  • Too many projects at once. When waste is everywhere (and it always is), the list of improvement projects is endless. Teams spread their effort thin.
  • Local gains that don’t reach the bottom line. A changeover time halved on a machine with spare capacity improves that machine’s numbers, but the company ships no more product and makes no more money.
  • Priority conflicts. Each department chases its own waste. There is no clear answer to “Which improvement first?”
  • Fatigue. After two or three years, people see a lot of activity and not much change in results. Enthusiasm fades.

None of this is a flaw in the Lean tools. It is a focusing problem.

Where TOC adds value

TOC answers exactly the question that Lean leaves open: where to focus.

Remember the logic of a chain. Strengthening any link other than the weakest one does not make the chain stronger. In the same way, an hour saved at a non-constraint is (in Goldratt’s words) a mirage: it doesn’t increase output, it only adds idle time. An hour saved at the constraint is an hour gained for the entire plant.

Picture a line with three machines in sequence. Machine A can make 1,000 parts a day, machine B 600, and machine C 900. The line ships 600 a day, because B is the constraint.

A Lean team spends a month halving set-up times on machine A and gains 10% capacity: A can now make 1,100 a day. The line still ships 600. The only visible effect is more parts waiting in front of B.

The same month spent on machine B gains 10% there: B now makes 660 a day. The whole line ships 60 more parts a day. If each part contributes ₹200 over its material cost, that is ₹12,000 more throughput every working day, roughly ₹3.6 million a year, from the same people and the same Lean tools. The only difference is where they were applied.

So TOC tells the Lean team:

  • Start with the constraint. Set-up reduction, 5S, quality at source, preventive maintenance: apply them first where they add capacity to the whole system.
  • Protect the constraint. Make sure it never waits for material, operators or drawings, and that defects are caught before they reach it, not after.
  • Use buffer data to pick the next project. In a TOC plant, every late order is recorded with the reason it was late. The most frequent reasons tell you exactly which improvement will have the biggest effect on delivery and output. Lean tools are then the right instruments to fix them.
  • Don’t over-improve non-constraints. Spare capacity there is protection, not waste.

Where Lean adds value to TOC

The partnership works both ways. TOC tells you where to act; Lean gives you a rich, proven toolbox for how to act there.

When the constraint is a machine, Lean’s set-up reduction and preventive maintenance are often the fastest ways to exploit it. When the constraint is the market, Lean’s focus on quality and short lead times helps build the reliable delivery that customers will pay for. When TOC’s buffer reports point to a recurring cause of delay, a kaizen event is a good way to fix it.

TOC says where to look. Lean helps you fix what you find there.

A practical way to combine them

If your plant already has a Lean programme, you don’t need to abandon it. You need to point it.

  1. Identify the constraint of the system, whether a resource or the market.
  2. Stop or pause improvement projects that don’t affect the constraint or the flow to customers.
  3. Redirect Lean tools to the constraint and to the main causes of delay shown by buffer management.
  4. Change the measures: judge improvements by their effect on throughput, inventory and operating expense for the whole plant, not by local efficiency gains.
  5. Repeat when the constraint moves.

In short

The question is not “Lean or TOC?” It is “Lean where?” A focused Lean programme, aimed at what limits the whole system, delivers results faster than an unfocused one, and keeps people motivated because they can see the effect of their work.

Mohit Saini

Strategy, supply chain & sales transformation consultant. About · Book a discussion