I did not read The Goal because I was interested in manufacturing theory.
I read it because I was trying to get better at my job. I was deep in the analysis work at a large electric utility. I knew how to pull the data, build the model, find the story. But I kept running into the same wall. I could show an executive a report and walk away with no decision made. The numbers were right. The logic was sound. Nothing moved.
I wanted to know how to close that gap. How do you take solid analysis and turn it into influence? How do you get from the data to the decision?
I looked for books to read to start to bridge that gap. I found Goldratt. I picked up the book expecting strategy. What I found was something I did not have a word for yet.
The Goal is a novel about a factory manager named Alex Rogo whose plant is failing. His mentor, Jonah, keeps asking him one question: what is the goal of a business?
The answer Goldratt keeps returning to is deceptively simple. The goal is to make money. Not to ship product. Not to hit utilization targets. Not to keep machines busy. To make money. Everything else is a means to that end, or it is noise.
From that foundation, Goldratt builds the Theory of Constraints. Every system has a constraint. One bottleneck that limits the output of the entire operation. You can optimize everything else in the plant and it will not matter if the constraint is not moving. The constraint is the only number that matters.
The corollary is the part that stuck with me. If you are not the constraint, running faster does not help. A machine upstream of the bottleneck that runs at full capacity is not being productive. It is building inventory that sits in front of the bottleneck and goes nowhere. Work in front of a constraint is not progress. It is pressure.
Ever since I have started doing operations intelligence work, I have been measuring productivity. Inspector performance. Crew Performance. Are you getting enough done compared to what your history says? All of it measured independently, all of it reported with equal weight.
Goldratt’s argument is that this is exactly wrong. Utilization at a non-constraint is a vanity metric. The only utilization that matters is at the constraint. Everything else should be subordinated to keeping the constraint fed and moving.
That reframe hit hard.
It meant that the executive who wanted to see every machine at 90% utilization was asking the wrong question. It meant that the shift supervisor who was proud of how fast their upstream station was running might be making things worse. It meant that the dashboard I had been building, which showed every metric at every level with equal prominence, was not helping anyone find the constraint. It was hiding it.
This is where The Goal connects directly to how the OIM is designed.
The throughput-first metric hierarchy is a direct application of Goldratt’s thinking. Throughput is the headline number because throughput is the closest proxy to the goal. Not OEE. Not utilization. Not cycle time in isolation. How much did we make, and how does that compare to what we should have made?
Everything else in the reporting hierarchy exists to explain the gap between those two numbers. Downtime explains lost throughput. Data quality explains where the measurement breaks down. The constraint flag surfaces which line is limiting the plant.
The goal of the report is not to show everything. The goal is to help someone find the constraint and remove it. That is it. That is what Goldratt taught me, and that is what I tried to build.
I am getting ready to read The Goal again. I expect to find things I missed the first time.
The first read gave me throughput. It gave me the constraint. It gave me a language for why some metrics matter and others are noise. It gave me a way to talk to executives that was not just “here is what the data says” but “here is the one thing that is limiting us and here is what it costs every day we do not fix it.”
That is how you close the gap between analysis and decision.
Find the constraint. Name it clearly. Show what it costs. The decision usually follows.