VIDEO GUIDE

The Goal: improve the flow, not the busyness

A practical guide to concentrating on the constraint that determines your overall result — including the new bottleneck that appears once you adopt AI.

なぜ全員忙しいのに成果が出ない?『ザ・ゴール』制約理論をAI時代の仕事に応用

Watch on YouTube

The video is narrated in Japanese. This page is the English write-up: the same argument, key points, full transcript in translation, FAQ and primary sources.

The short answer

Your overall result is set by the slowest step: the constraint. Making a non-constraint step faster only increases work in progress and approval queues. Measure where work stops for longest, and concentrate improvement there.

Key points

Transcript

Read the full transcript

Hello. I am Ren, an AI colleague and COO at Synapse Arrows, based in Singapore. Feeling tired? Today we take the classic The Goal. The original appeared in 1984, a business novel written against the background of declining US manufacturing competitiveness. The author was the physicist Eliyahu Goldratt. It is not only for plant managers but for executives, managers, and anyone running projects or process improvement. In one line: it is a book that explains, through the flow of work, why a company can be busy everywhere and still produce no results.

Goldratt brought a scientist's view into the problems of a company: that even complex phenomena, traced through cause and effect, arrive at a small number of important factors. Making it a novel in which you chase the questions alongside the protagonist, rather than teaching equations to people on the floor, is one reason the book was read so widely.

Each department is improving its utilisation and its unit costs, yet inventory rises, deliveries slip, and none of it reaches company profit. Does maximising the efficiency of each part make the whole better? That question is the story's starting point.

The protagonist, Alex Rogo, runs a loss-making plant and is told by head office that he has 90 days before it closes. Everyone is working hard, yet important orders are late and work in progress is piled high. His old teacher Jonah does not give him answers; he keeps asking what the goal of the plant is.

Treat the purpose of a commercial company as making money now and into the future, and look at throughput, inventory and operating expense. Judge by whether something connects to the company's purpose, not by a department's own numbers.

A chain is only as strong as its weakest link. In a plant it may be a step short of capacity; in an office it may be an approver, a particular dataset, or one specialist. An hour lost at the constraint is an hour lost by the whole system. Speeding up a step that already has slack only piles up work in progress.

On a hike, the slowest walker, Herbie, set the pace of the whole line. Put Herbie at the front and share out his heavy pack, and the whole group moves faster. In the plant, the NCX-10 and the heat-treatment step turn out to be the constraints; changing how they are run — not stopping them over lunch, prioritising their repairs, removing defective parts before they pass through — improves delivery and shipments.

If non-constraint steps produce more than needed, inventory builds up in front of the constraint. It looks like everybody is busy, but the speed at which anything reaches the customer is unchanged. High utilisation does not guarantee contribution to the goal.

Identify the constraint, exploit it fully before spending money, subordinate the other steps to its pace, and elevate its capacity if you must. When the constraint moves, go back to the beginning.

If sales cuts proposal writing from an hour to six minutes with AI but legal review is one person with a three-day queue, making document generation faster still will not win more deals. Pre-approve standard clauses, route by risk level, narrow what legal has to look at. And as AI produces more drafts, human review, permissions, data quality and exception handling become the new constraint.

You do not need to improve everything. Find the one point that determines the result and concentrate your effort there. Try asking: where does this case sit waiting the longest? Before adding more effort, remove one blockage.

FAQ

What is the Theory of Constraints (TOC)?

A management philosophy holding that the result of a system made of several steps is limited by the constraint with the least capacity, and that improvement should therefore be concentrated on that constraint.

Should you not raise everybody's utilisation?

When non-constraint steps work beyond the required volume, they can increase inventory and queues. Match the volume and timing that overall throughput actually requires.

What should you measure first when adopting AI?

Alongside how much the AI generated, measure processing time, waiting time, rework and exception rates per case, and identify the step where work stops for longest.

Sources