The Goal: A Process of Ongoing Improvement
Busy everywhere is not the same as moving anywhere.
Essence (why this landed for me)
Inside the Box sent me here, and the detour paid off. A business novel from 1984 that reads fast and teaches one thing deeply: the bottleneck sets the pace of the whole system, so everything else should serve it. The Herbie hike made it stick, the slowest scout decides when the troop arrives. It changed how I look at busy teams: high utilization everywhere can mean the system is barely moving. Forty years on, the questions still fit product, design, and engineering work.
Insights (mapped to mental models)
Takeaways grouped by mental models, with a short action you can use now.
Name the goal before measuring anything else
Three numbers tell the truth about a system
The bottleneck sets the pace of the whole system
An hour lost at the bottleneck is lost forever
Efficiency at a non-bottleneck is a mirage
A plant where everyone is always busy is inefficient
Dependent events amplify statistical fluctuations
Exploit the constraint before spending to elevate it
Cut the batch and the whole system speeds up
Drum, buffer, rope keeps the flow honest
Measurements drive behavior more than intentions
Questions teach better than answers
When a constraint breaks, inertia becomes the next one
Ongoing improvement is a loop, not a project
The plant is not the only system that needs attention
Absorption Notes (short essay)
Start any stuck project by asking where the work piles up. That is the constraint. Keep it busy on the right things: move quality checks in front of it, stagger breaks around it, take anything off it that another step can do. Do not spend on new capacity until the cheap moves run out. Watch for busy teams that are not the constraint. Let them sit idle rather than build a pile. When lead times feel long, cut one batch size in half and see what happens. In reviews, check the three numbers: what is flowing out, what is stuck inside, and what we spend to run it. After every fix, ask where the constraint moved. Simple moves, steady rhythm.
Reflection Prompts (product × design × engineering)
Questions to apply the ideas across projects. Pick one or two and use them today.
Goal check
What is the actual goal here and does this task move it
Goals vs MetricsName the goal.
Find Herbie
Where does the work pile up in this flow
BottlenecksLook for the pile.
Feed it
Is the constraint ever idle or working on the wrong thing
Leverage PointsKeep it fed.
Mirage
Which team looks efficient without moving the system
Local vs Global OptimaStop polishing.
Slack
Where do we need idle capacity to absorb the swings
Margin of SafetyAllow the slack.
Batch
Which batch, sprint, or release could be half the size
Queuing TheoryHalve one.
Metric audit
What behavior does this measurement actually reward
IncentivesFollow the metric.
Exploit first
What can I squeeze from what exists before asking for more
SequencingSqueeze first.
Moved constraint
Where did the constraint go after the last fix
Path DependenceRe-check now.
Home system
Which system outside work is running on neglect
Systems ThinkingTend it.