Taste Note - Amazon Production & Operations Best Sellers
The Goal: Bottlenecks, Throughput, and Procurement Thinking
A Kurums Book Taste review of The Goal for operations leaders and procurement teams managing constraints.
Why this book fits Kurums
Use it to find bottlenecks in supplier flow, category management, and operational throughput.
For the Kurums Procurement audience the novel format is the point: Goldratt teaches the Theory of Constraints through a plant manager's ninety-day rescue, which makes the physics of flow memorable in a way no textbook manages.
What the book argues
Alex Rogo has ninety days to save his plant, a failing marriage, and no idea that the two problems share a cause. His physicist mentor Jonah teaches by Socratic ambush: what is the goal? Not efficiencies, not cost per part - making money, measured operationally as throughput (money in through sales), inventory (money stuck inside), and operating expense (money out). Every local metric that conflicts with those three is decoration, and most plant metrics do.
The famous scenes carry the theory: the Boy Scout hike, where slow Herbie sets the troop's pace and the only fix is to put him first and lighten his pack - dependent events plus statistical fluctuations mean the constraint dictates system output. Back in the plant, the bottleneck machines get the same treatment: an hour lost at the bottleneck is an hour lost for the whole system; an hour saved at a non-bottleneck is a mirage. Batch sizes get cut, quality inspection moves before the constraint, and 'efficient' machines are allowed to sit idle - each move heretical by cost accounting, each one raising throughput.
The book closes with the process of ongoing improvement: identify the constraint, exploit it, subordinate everything else to it, elevate it, and - when it moves - go back to step one without letting inertia become the new constraint. Goldratt's real target is cost-world thinking itself: optimizing every resource independently guarantees a slow system, because the optimum of the system is not the sum of local optima. Procurement readers will recognize their own KPIs in the villains.
Key ideas, translated to your desk
Find your Herbie
Every process has one pace-setter. Until you know which supplier, machine, or approval step it is, every other improvement is rearranging the hike.
Bottleneck hours are system hours
Protect the constraint with buffers, quality gates before it, and priority everything. Its lost hour can never be recovered downstream.
Idle can be optimal
Running non-bottlenecks at full speed produces inventory, not throughput. Efficiency metrics that reward busyness are paying people to clog the system.
Use it at work
- Map one order-to-delivery flow and mark the constraint with data, not opinion.
- Move inspection before your bottleneck so it never wastes capacity on defective inputs.
- Cut batch sizes on one line and measure lead time against the efficiency-report protests.
- Rewrite one supplier KPI from unit cost to throughput contribution and watch behavior change.
Read it if
- You own operations, supply chain, or any flow with a hidden pace-setter.
- Your metrics reward local efficiency while delivery dates slip.
- You want the foundation under Toyota Way and Phoenix Project.
You can skip it if
- Business novels test your patience - though this is the genre's best argument.
- You know TOC cold; the five steps are the whole doctrine.
- You need service-industry translations ready-made; the mapping is yours to do.
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.