TOC Operator Cheat Sheet (Series Finale)

Print this. Tape it near the daily management board. This is the series finale reference for The Goal (Goldratt & Cox, 1984)—throughput thinking in one place for shift handoffs.

If you are new to the series, start at the intro. This page condenses three measurements, flow, bottleneck rules, balanced plant warnings, five focusing steps, and the FAQ into operator-ready form.

#The goal

Make money: net profit, ROI, cash flow. Everything else is a means.

#Three measurements

Term	Floor meaning	Question
Throughput	Money in via sales	Will this ship and collect soon?
Inventory	Money stuck in the system	Where is cash parked in WIP/FG?
Operating expense	Money out to convert inventory	What did we spend—including idle time?

Productivity test: Increase throughput without raising inventory or expense—or reduce inventory/expense without hurting throughput.

Throughput · Inventory · OE — three words, one language from gemba to HQ.

#Five focusing steps

1. Identify the constraint (WIP piles)
2. Exploit constraint time (QC before, no idle waste)
3. Subordinate non-bottlenecks to constraint pace
4. Elevate capacity if still stuck (reuse, outsource, engineer around)
5. Repeat—do not let inertia preserve old rules

Every improvement idea must name which step it serves—or it waits.

#Bottleneck rules of thumb

• Hour lost at constraint ≈ hour lost for plant
• Non-bottleneck idle time beats WIP floods
• Release material at consumption rate, not to "keep busy"
• Balance flow, not every machine's utilization
• Scrap after the bottleneck is unrecoverable throughput

Tip. Schedule PM on the constraint like flight hours—defer only when you account for throughput risk.

#Anti-patterns

Anti-pattern	Why it fails	See also
Balanced plant capacity = demand	Matchstick disaster—throughput collapses	Balanced Plant
Utilization hero with flat sales	Local efficiency illusion	Flow Engine
Red-tag priority without release control	Expediting rearranges WIP, not throughput	Local Efficiency
Finished-goods buffer after constraint moved	Inertia preserves dead policy	Five Steps
Capital before exploit/subordinate	Rebuilds the swamp faster	Five Steps

#Three manager questions

1. What to change?
2. What to change to?
3. How to cause the change?

The five focusing steps answer the first two. Training, metrics, and release policy answer the third.

#Gemba walk prompts

Use these on Monday's walk:

• Where is the longest wait?
• Which machine's calendar drives ship date?
• What would we stop if throughput were the headline KPI?
• Does release match constraint consumption—or keep upstream busy?

#Shift handoff line

One sentence, every shift change:

"Constraint status, WIP at constraint, release rate today, top blocker."

#When to escalate to capital

Only after exploit and subordinate are honest for two full cycles. Buying capacity before fixing release policy rebuilds the swamp faster. Elevate is step four, not step one.

#Pocket version

Seven words on a sticky note until habits form:

Throughput · Inventory · OE · Five steps · Herbie · Inertia · Flow

#Laminate and teach

New supervisors learn TOC in ten minutes from this sheet plus one gemba walk. Teach weekly until vocabulary sticks. Pair with the FAQ when someone pushes back in a meeting.

#Activating vs utilizing (quick reference)

	Activating	Utilizing
Definition	Resource is running	Work moves the system toward the goal
Metric	Uptime, hours run	Throughput contribution
Risk	Creates WIP at non-bottlenecks	Aligns with constraint pace
Example	Running upstream flat out	Releasing to consumption rate

#Dependent events and fluctuations (quick reference)

Dependent events: Step B cannot start until step A finishes. Delays pass downstream; recoveries do not fully pass upstream.

Statistical fluctuations: Task times vary even with standard work. Averages deceive on dependent lines.

Combined effect: Throughput falls below theoretical capacity; inventory waves through the line. Balancing capacity to demand makes it worse—not better.

See Balanced Plant for the matchstick simulation.

#Productivity test (quick reference)

An action is productive if it:

• Increases throughput without raising inventory or operating expense, OR
• Reduces inventory or operating expense without hurting throughput

If it improves one measurement while damaging another, it fails the test—no matter how good the local KPI looks.

#Five steps vs three measurements

Three measurements	Five focusing steps
What to measure	What to do
Throughput, inventory, OE	Identify → Exploit → Subordinate → Elevate → Repeat
Diagnostic vocabulary	Improvement loop
Answers "Are we making money?"	Answers "How do we make more?"

Use measurements in every review. Use the five steps in every improvement cycle.

#Weekly rhythm for shift leaders

Day	Action
Monday	Name constraint status; set release rate for the week
Wednesday	Mid-week WIP check at constraint; one exploit action
Friday	Three-measurement review: throughput, inventory, expense
Every shift	Handoff line: constraint status, WIP, release rate, top blocker

#Common pushback and responses

"Why are non-bottlenecks idle?" Because idle beats WIP floods. Show the WIP pile that idle prevents.

"Why not 100% utilization everywhere?" Run the matchstick game. Dependent events plus variation make it mathematically toxic.

"We need to hit our production target." Production target without shipped-and-collected throughput is inventory, not success.

"Setup reduction saved us hours." At which operation? Hours at a non-bottleneck are mirage time unless they feed the constraint.

#Where to go next

• Series intro & course teaser
• HR systems edge metaphor for cross-functional leaders
• Join the waitlist for our hands-on manufacturing course

#Series completion

You now have vocabulary shared with millions who read The Goal. Teach it on your line. The physics of constraints does not change with ERP upgrades or automation—only the vocabulary and release policy do.

← Start the series · ← FAQ