FAQ: The Goal for Busy Plant Leaders

You read the novel—or this series—and production still asks hard questions. Here are concise answers grounded in The Goal (Goldratt & Cox, 1984) for plant managers who need ammunition in stand-ups, not another slide deck.

This is Lesson 6. For depth on any topic, follow the links to earlier lessons. For a printable reference, jump to the TOC operator cheat sheet.

#What is the ultimate goal?

Make money through net profit, ROI, and cash flow. Quality, efficiency, and technology are means, not ends. If a "quality" initiative builds WIP without sales, it fails the productivity test.

#How is throughput different from production?

Throughput is money generated through sales. Building unsold parts is inventory, not throughput. A machine can run three shifts and the plant can still lose money if nothing ships and collects.

#Why remove labor value from inventory?

So managers stop treating WIP as an asset to maximize. Labor is operating expense, not buried inventory value. When WIP looks like an asset on the balance sheet, operations gets rewarded for building piles finance cannot invoice.

#What is the local efficiency illusion?

Pushing every machine to high utilization without regard to the constraint creates excess WIP and misses ship dates. Cost-per-part can fall while the plant loses money. See The Flow Engine and Local Efficiency Trap.

#Activating vs utilizing?

Activating runs the machine. Utilizing does work that increases system throughput. They are not synonyms. Keeping a non-bottleneck busy often creates inventory that hurts the goal.

Why are non-bottlenecks idle? Because idle beats WIP floods that hide the constraint.

#Why can't we balance capacity to demand?

Dependent events plus statistical fluctuations cause slowness to accumulate. Balanced capacity without reserve drops throughput and raises inventory—proven in Alex's matchstick game. See Why Balance the Plant Backfires.

#What is a bottleneck?

Any resource with capacity less than or equal to demand placed on it. WIP piles point to it. When in doubt, follow the inventory.

#Why is constraint downtime so expensive?

It caps entire plant output. Roughly: total operating expense divided by constraint hours available. A lunch break at the constraint costs the whole plant an hour of throughput—not one machine's labor rate.

#What are the five focusing steps?

1. Identify the constraint
2. Exploit constraint time
3. Subordinate everything else to constraint pace
4. Elevate capacity if still stuck
5. Repeat—fight inertia when the constraint moves

Full walkthrough: Five Focusing Steps.

#Should we cut batch sizes?

Halving batches often shortens lead time, improves responsiveness, and frees cash—without raising operating expense at non-bottlenecks. Setup time saved at a non-bottleneck is usually mirage time; it does not buy throughput.

#What is inertia in TOC?

Keeping old rules—buffers, tags, inventory targets, batch policies—after the constraint moved, creating a new choke point. Step five exists because humans preserve what worked yesterday even when the system changed.

#What three questions must managers answer?

What to change? What to change to? How to cause the change? Alex Rogo's summary of the improvement process. The five focusing steps answer the first two; subordinate and training answer the third.

#Why not 100% utilization everywhere?

Dependent events plus variation make that mathematically toxic. See the matchstick game in Balanced Plant. High utilization everywhere is a reliable predictor of late shipments and WIP floods.

#How does this relate to lean and six sigma?

Compatible, not competing. Lean waste reduction and six sigma variation reduction help—especially at the constraint. TOC adds one priority: identify the constraint first, then improve there before spreading effort across the line.

Tip. When someone says "we already do lean," ask whether they can name the current constraint and show release policy subordinated to it. If not, TOC vocabulary still adds value.

#Accounting pushback

Prepare a one-pager for finance: throughput-world priority order (throughput, inventory, expense) and why inventory reduction improves cash even when assets on paper shrink. Pair it with Three Measurements.

#How do drum-buffer-rope and the five steps relate?

Drum-buffer-rope (DBR) is the scheduling mechanism. The five focusing steps are the improvement loop. DBR implements subordinate (step 3); the five steps tell you when and how to change the drumbeat.

• Drum — the constraint sets the pace (consumption rate)
• Buffer — material/time reserve that protects the constraint from starvation
• Rope — release signal that prevents upstream from over-producing

You can run the five steps without formal DBR software. You cannot run DBR honestly without completing identify, exploit, and subordinate first.

#What about multiple constraints?

Most plants have one dominant constraint at a time. When two resources compete:

1. Pick the one that most directly caps shipped orders this month
2. Subordinate to it
3. Re-evaluate when WIP piles shift

Trying to manage three constraints simultaneously usually means you have not identified the real one. Follow the piles.

#Does TOC replace lean?

No. Lean eliminates waste; six sigma reduces variation; TOC tells you where to aim first. The best plants use all three—concentrated at the constraint.

Lean tools (5S, standard work, kanban) work better when scoped to the constraint and its feeder operations. A kanban loop that subordinates release to consumption rate is TOC in practice even if nobody uses the label.

#What if our constraint is a person or a policy?

Constraints are not always machines. A single skilled operator, a required sign-off, a regulatory hold, or an inspection step can be the constraint. The five steps still apply:

• Identify — where does work wait for a person or approval?
• Exploit — eliminate wait time, cross-train backup, pre-stage decisions
• Subordinate — do not flood the queue ahead of the approval step
• Elevate — add capacity, automate the approval, or delegate authority
• Repeat — when the person constraint breaks, find the next one

Tip. When the constraint is a policy, ask physics or habit? Policies that exist for historical cost targets are elevate candidates.

#How long before we see results?

Most pilots show WIP reduction within two weeks of honest subordinate. Throughput gains often follow one constraint cycle later—because exploit actions take time to compound. Plants that expect overnight revenue jumps usually skipped subordinate and wonder why inventory still grows.

Start with one family, two weeks, three measurements. Proof on the floor beats debate in the conference room.

#Union and labor context

Exploit/subordinate conversations must respect agreements. The physics of constraints still applies; implementation is collaborative. Frame idle time at non-bottlenecks as flow protection, not headcount reduction.

#Where to practice

Start one value stream, one constraint, two weeks. Proof on the floor beats debate in the conference room. Use the series intro roadmap to pick your starting lesson.

Need a printable reference? The TOC operator cheat sheet closes the series.

← Start the series · ← Five Focusing Steps · Next: TOC Cheat Sheet →