PDF Summary:The Goal: A Process of Ongoing Improvement, by Eliyahu M. Goldratt
Book Summary: Learn the key points in minutes.
Below is a preview of the Shortform book summary of The Goal: A Process of Ongoing Improvement by Eliyahu M. Goldratt. Read the full comprehensive summary at Shortform.
1-Page PDF Summary of The Goal: A Process of Ongoing Improvement
Want to increase your personal output, or the output of your team? Do you feel like there’s a bottleneck constraining you, but you don’t know how to improve it? Have you tried working harder, with little results?
The Goal explains why optimizing activities that seem productive can actually be pointless. This classic management book (recommended by Jeff Bezos as required reading for new Amazon managers) introduced the idea of identifying the bottleneck in a production system and restructuring the organization around it. It upends traditional obsessions with cost efficiency to focus on what really matters.
(continued)...
- Net profit (the more positive the better)
- ROI (relative, to tell what the base is)
- Cashflow (to make sure the company stays alive)
You can convert these highest-level metrics to ones that are more actionable day-to-day:
- Throughput: the rate at which the system generates money through sales
- Inventory: the money the system has invested in purchasing things to sell. Any investment that you can sell is inventory. R&D that can be sold, like a patent, is inventory. In contrast, R&D to improve throughput can’t be sold and isn’t inventory.
- Operational Expense: the money the system spends in order to turn inventory into throughput. This includes labor, leases, and R&D to improve throughput. It’s better not to consider where value is added—don’t get caught up over whether a dollar is investment or expense. If it’s not part of the packaged product being sold, it’s an operational expense.
Ideally, you should try to improve all three at once. For example, if you install robots, it should increase throughput by increasing sales, decrease inventory needed, and/or reduce labor costs. Be wary of a change that affects only one of these metrics—there may be second-order effects that backfire. For example, reducing labor to reduce operational expense may decrease throughput.
The Importance of the Bottleneck
The authors’ critical concept is identifying the bottleneck, or the key constraint that holds back throughput. It’s any resource whose capacity is equal to or less than the demand placed on it. Constraints can be equipment, people, or policies.
The bottleneck of the system determines the throughput of the entire system. By definition, the throughput of the system cannot be greater than the capacity of the bottleneck. This means the value of an hour lost at the bottleneck is equal to the value of the entire system. Even if a bottleneck costs $5/hour to run, if the factory is producing $1,000 in goods per hour, then an hour of the bottleneck idling is costing $1,000/hour.
The 5-Step Process for Continuous Improvement
Goldratt and Cox describe a five-step process for continuously improving the bottleneck’s capacity:
- Identify the system’s constraint.
- Optimize the system’s constraint. Squeeze more capacity out of the constraint.
- Subordinate all the non-constraints to the above decisions.
- Elevate the system’s constraint—add more capacity to it.
- If in the previous steps, the constraint no longer remains, go back to step 1 for the new constraint.
We’ll discuss these steps in detail in the following sections.
Identifying the Bottleneck
The first step is to identify the bottleneck. You can do this by seeing where you have the greatest upstream inventory piling up, and low inventory at the next step. If the non-bottlenecks are producing at equal rates (for example, 100 parts/hour), the slowest step will have the largest upstream inventory.
Alternatively, see which downstream steps are most in demand of upstream parts and are idling. If you decrease inventory sizes, you’ll see which work center, if stopped, halts the whole line.
Another way to identify it is by defining your market demand (by sales) then comparing the productivity of each step of the chain to this demand.
The authors list some common contributors to bottlenecks:
- The machine is running inefficiently, performing unnecessary steps or with high setup/switching costs.
- The machine is running efficiently, but there aren’t enough machines.
- The machine isn’t being run for the maximal number of hours.
- The step requires a long batch period, and batches are not fully fulfilled.
- Poor quality upstream parts waste bottleneck time because the bottleneck processes them into a product that is later rejected.
- Working on parts you don’t need urgently diverts capacity from the more important backlog.
- Occasionally, the bottleneck doesn’t have the upstream inventory to work at full capacity (and technically isn’t the bottleneck at that moment).
- Machines are idle because people are redistributed to work on non-bottlenecks.
Increasing Capacity at the Bottleneck
In this section, we’ll discuss what you can do to fix bottlenecks.
First, you can improve the bottleneck itself. You can do this by skipping unnecessary steps or decreasing setup/switching costs, and adding supplements to increase bottleneck capacity, even if they’re less efficient. The authors also say you should guarantee round-the-clock production at the bottleneck and permanently staff it with people to decrease idle time.
Second, you can improve what the bottleneck is working on. Focus the bottleneck only on parts that are needed today, not for safety’s sake tomorrow. Order the work in terms of first in, first out—clear the backlog first to guarantee important work is being done. Allow parts to skip the bottleneck step if it’s not necessary. Collect accurate statistics on bottleneck operations to make better decisions.
Finally, you can optimize the system for the bottleneck. Redistribute capacity from non-bottlenecks to the bottleneck, maintain extra inventory ahead of the bottleneck to keep it running continuously, and redistribute work when possible. Prioritize parts that will go to the bottleneck, and prevent substandard parts from contributing to the bottleneck. Announce the importance of the bottleneck to the entire team. Check upstream steps to see if adjustments can be made that decrease load on the bottleneck and, if necessary, outsource the bottleneck.
Structuring Around the Bottleneck
Once you identify the bottleneck and improve its capacity, you may find other problems arising that decrease throughput. To avoid this, you must synchronize the non-bottlenecks with the bottleneck, which means idling at non-bottlenecks is acceptable. If both the bottleneck and non-bottleneck go full steam ahead, the non-bottleneck will produce surplus inventory, which adds cost and causes traffic jams.
To coordinate this, use Drum-Buffer-Rope method:
- Drum: Pace non-bottlenecks’ production rates with bottleneck rates.
- Buffer: Provide enough buffer inventory upstream of bottleneck to prevent idling.
- Rope: Allow up to a threshold max surplus inventory, after which the non-bottleneck is idled.
Want to learn the rest of The Goal: A Process of Ongoing Improvement in 21 minutes?
Unlock the full book summary of The Goal: A Process of Ongoing Improvement by signing up for Shortform .
Shortform summaries help you learn 10x faster by:
- Being 100% comprehensive: you learn the most important points in the book
- Cutting out the fluff: you don't spend your time wondering what the author's point is.
- Interactive exercises: apply the book's ideas to your own life with our educators' guidance.
Here's a preview of the rest of Shortform's The Goal: A Process of Ongoing Improvement PDF summary: