Book summary · Theory of constraints · Beginner
The Goal: summary and review
A Process of Ongoing Improvement
By Eliyahu M. Goldratt and Jeff Cox. First published 1984.
The short answer
The Goal is a 1984 novel in which plant manager Alex Rogo has about three months to rescue a failing plant while a physicist mentor, Jonah, steers him with questions. Its argument: a plant's output is set by its constraints, so an hour lost at a bottleneck is lost to the whole plant, and local efficiency targets push people to build inventory that never ships. It judges decisions by throughput, inventory and operating expense. It is the quickest way to teach flow logic to supervisors and engineers, and it is not a scheduling manual.
Read it if
- You supervise or engineer a line where one station always has a pile in front of it and improvements elsewhere have not moved shipments.
- You need a story that gets operators, finance and sales to see why local efficiency targets backfire.
Skip it if
- You want formulas for sizing buffers, WIP caps or lot sizes. Use a quantitative text or kanban and CONWIP design instead.
- Your bottlenecks move between products and shifts all day. The book shows one plant with clear bottlenecks.
When it pays off: Early, before or alongside your first lean work, because it explains why a kaizen at a non-constraint station can leave output flat. Reread it when output stalls despite a run of improvement events.
The core ideas, in plain language
- 1
The constraint sets the plant's pace
Jonah's test is simple: a bottleneck is any resource that cannot do more than the demand placed on it. Every hour it stands idle is output the whole plant loses, and an hour saved elsewhere does not raise shipments.
- 2
Three measures replace local efficiency
Throughput is the rate at which the system generates money through sales. Inventory is the money tied up in things it intends to sell. Operating expense is the money spent turning inventory into throughput. Decisions get tested against all three, not against machine utilization.
- 3
Five focusing steps
Identify the constraint, decide how to get the most from it, subordinate everything else to that decision, elevate it, and when it breaks go back to step one. The publisher says the 30th anniversary edition weaves the steps through the story.
- 4
Variation and dependency compound
On a scout hike, Alex uses dice, matches and bowls to show that when each stage depends on the one before it, random low rolls pile up behind. Averages do not rescue a chain of dependent steps. Putting the slowest hiker, Herbie, at the front keeps the line from stretching.
- 5
Idle time at a non-constraint is not the enemy
Letting a non-bottleneck station wait costs less than speeding it up, which only builds work-in-process that the constraint cannot absorb. That is the part supervisors find hardest to accept.
- 6
Improvement never finishes
Once you lift one constraint, another resource becomes the limit. Constraints can also be policies, not machines, which is why the subtitle says process of ongoing improvement.
How to use it on Monday morning
- 1
Find the constraint with a clipboard
Pick one part family and walk its routing at the start, middle and end of a shift, counting jobs waiting in front of every station. Then work out each station's capacity per shift from cycle time, availability and yield. The station at or below demand with the biggest pile is your candidate.
- 2
Log every lost minute at the constraint
For three shifts, record each minute it is not producing and why. Stagger breaks and lunches, stage material before the machine needs it, and inspect before the constraint so none of its time goes into scrap.
- 3
Cap what feeds it
Agree with the scheduler on a visible limit for work waiting in front of the constraint, in hours of constraint work, marked on the floor. Upstream releases material only when space opens. Colored zones showing how much of the buffer is used tell you when to react.
- 4
Stop scoring efficiency at non-constraints
Tell upstream supervisors in advance that idle time there is acceptable this week. Post one number: constraint output per hour against plan.
- 5
Attack the biggest loss, then look again
Take the top reason from the log (changeover, waiting for an operator, a quality hold), fix it, and re-measure. If the constraint moves, repeat from the first step.
What to be careful about
One plant, clear bottlenecks
The novel's plant has identifiable constraints. Christoph Roser, in a critique of drum-buffer-rope, argues that shifting bottlenecks are the norm, that the method ignores blocking downstream, and that it gives little guidance when many variants run. He prefers kanban or CONWIP in most cases.
Method claims are contested
D. Trietsch has argued drum-buffer-rope is inferior to competing approaches, and Noreen, Smith and Mackey noted that several key TOC concepts had been in management accounting textbooks for decades. Take the intuition, then test the scheduling method against your own floor.
Often misread as ignore everything else
Kevin Meyer faults Goldratt's institute for first positioning TOC as an alternative to lean, and Sergio Rattner argues the two fit together, with TOC between lean's second and third steps. Improvements outside the constraint can still cut inventory and operating expense, but they will not raise output until the constraint is relieved.
A novel, with the usual costs
A marriage subplot runs alongside the plant story and only occasionally touches the main thread. The publisher calls the 2014 edition the first substantial narrative update, so older printings may read as more dated and state the five steps less directly.
The Goal compared with Factory Physics
The Goal gives you the intuition and a vocabulary to argue with accountants and schedulers. Factory Physics is the quantitative treatment of the same flow questions. Read The Goal first, and move to Factory Physics when you need to size buffers and WIP with numbers.
Read the summary of Factory Physics.
What to read next
- Factory PhysicsThe math behind variability, queues and WIP that The Goal shows with matches and dice.
- Lean ThinkingThe other half of the lean-versus-TOC conversation, with waste elimination across the whole stream.
- It's Not Luck (Eliyahu M. Goldratt)The sequel to The Goal, which Wikipedia names as the follow-up novel.
Tools and templates on LeanSuite that go with it
- Bottleneck analysis worksheetWorks out effective capacity per station and walks through the five focusing steps.Open
- Process capacity sheetFinds the step in a routing that limits a cell against demand.Open
- Hour-by-hour production boardLogs plan, actual and the reason for each miss at the constraint.Open
- Six big losses worksheetRanks where the constraint's time goes, to pick the first loss to attack.Open
Book details
| Title | The Goal: A Process of Ongoing Improvement |
|---|---|
| Author | Eliyahu M. Goldratt and Jeff Cox |
| First published | 1984. First published by North River Press in 1984; revised editions followed (1986, 1992, 2004 and the fourth revised edition, 30th anniversary, in 2014). |
| Edition shown | 30th Anniversary Edition (fourth revised), paperback, includes Goldratt's essay Standing on the Shoulders of Giants, North River Press, 2014 |
| ISBN-13 | 978-0884271956 |
| Pages | 362 |
Details checked against public records on 7 October 2026. Other editions have other ISBNs. We carry no affiliate links.
FAQ
Questions about The Goal
More lean books
- The Machine That Changed the World
- Lean Thinking
- Lean Production Simplified
- Toyota Production System
- Workplace Management
- The Toyota Way
- Kaizen: The Key to Japan's Competitive Success
- Gemba Kaizen
- Managing to Learn
- Understanding A3 Thinking
- Toyota Kata
- Learning to See
- Making Materials Flow
- Creating Level Pull
- Value Stream Mapping
- Creating a Lean Culture
- The Lean Manager
- Gemba Walks
- Introduction to TPM
- Out of the Crisis
- Zero Quality Control
- Understanding Variation
- The Six Sigma Way
- Lean Six Sigma
- Getting the Right Things Done
- Hoshin Kanri for the Lean Enterprise
- A Revolution in Manufacturing
- Factory Physics
Back to the lean books hub for reading paths and filters.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

