Key Lessons from “The Goal”: Theory of Constraints and Operations Management

During the National Day holiday the author read the novel‑style management book The Goal and shares a detailed reading note, noting that the book’s narrative approach inspired DevOps classics like The Phoenix Project and that its lessons apply well to software development and operations.

The author, Dr. Eliyahu M. Goldratt, a physicist turned management guru, uses a fictional factory to illustrate simple logical reasoning that solves complex management problems.

Key Indicators

The three metrics that determine whether a company makes money are:

Effective output (throughput) – the speed at which the system generates cash through sales.

Inventory – the money tied up in purchased goods that are intended to be sold.

Operational expense – the cost of turning inventory into throughput.

The goal is to increase throughput while reducing inventory and operational expense, with the priority order: throughput > inventory > expense.

The story uses a hiking analogy to explain the relationship between bottlenecks, work‑in‑process, and throughput.

Match‑stick Game

A five‑person simulation demonstrates statistical variation and dependency: each player rolls a die and passes a number of matches to the next bowl, showing how later stages receive fewer matches than the average 3.5, illustrating cumulative variance.

Bottleneck Resources

Identifying bottlenecks is essential; the bottleneck is simply the current constraint in the system. The simplest way to locate it is to go where inventory piles up.

Once identified, the bottleneck should be placed at the front of the production line, and all other resources should be sequenced by capacity to mitigate the accumulation caused by dependency and statistical variation. In practice, the only viable solution is to increase bottleneck capacity without additional investment.

Bottleneck Loss Calculation

The plant’s capacity equals the bottleneck’s capacity, so losing one hour of bottleneck time loses one hour of overall system output.

Solutions to Improve Throughput

Check if spare machines can raise capacity.

Move inspection before the bottleneck to reduce waste.

Control downstream processes to avoid defects that waste bottleneck output.

Consider subcontractors for bottleneck operations.

Stop producing unnecessary parts (reduce inventory).

After applying these measures, the team noticed that non‑bottleneck stations were over‑processing, crowding the bottleneck. They introduced a demand‑driven release system to balance flow.

Further Improvements

By halving batch sizes at non‑bottleneck stations, the plant achieved:

Much shorter production cycles and delivery times.

Significant inventory reduction and better cash flow.

Higher sales revenue offsetting labor costs, thus lowering operational expense.

Potential increase in logistics cost due to more frequent supplier deliveries.

These changes earned the protagonist a promotion to oversee the business unit, giving him two months to prepare for new challenges.

Results Summary

The real constraint is never the machines themselves but the policies and how the machines are used.

Improvement Process

Identify the system’s bottleneck.

Decide how to exploit the bottleneck’s full potential.

Align all other activities to support that decision.

Elevate the bottleneck (e.g., bring back older equipment, adjust lines).

If the bottleneck shifts, return to step 1 and avoid inertia.

Management Capability

Effective management answers three questions:

What needs to change?

In which direction should it change?

How should it be changed?