There is a gap between how well an operator believes they are running and what they are actually producing. That gap has a name in this method, and it is the most useful thing to know about yourself.
It is the leak.
Why self-assessment flatters
Ask an operator to rate how they are going and they will rate what they can feel. Execution is easy to assess, because it is what they did and they were there. Effort is easy to assess. Recovery and capacity are much harder, because a deficit in either is not felt as a deficit. It is felt as determination.
So a self-assessment is most confident exactly where its information is weakest. That is not dishonesty, and it is not vanity. It is the shape of the instrument.
Why averaging hides it
The obvious way to combine the four is to average them. It is also the way that fails, and it fails in one direction: an average lets two strong levers pay for a weak one.
Arithmetically that is what an average does. Behaviourally it does not happen. A strong top cannot raise output above a weak floor, because each lever in the chain is capped by the one feeding it, and the margin of headroom that lets an operator outrun it for a while is what makes the arithmetic look plausible.
Nothing is paid for. The average simply hides the constraint, and it does so while sounding like the fair and reasonable way to look at four things at once.
Which is why the average is the dangerous reading
An operator can run a strong top on a weak floor and appear healthy right up to the week it stops. That is the failure the average is worst at catching, because it does not produce a wrong answer so much as a reassuring one.
A reassuring reading is more dangerous than a wrong one. A wrong reading gets checked. A reassuring reading gets trusted.
Where the leverage actually is
Every fix has a location, and the location that matters is the bottom of the chain rather than the top.
Anything applied above a cap is spent against the cap. Pushing the top when the constraint is lower down is effort converted into fatigue with nothing to show for it, which is why operators who are already working hard and still stuck are usually working in the wrong place rather than not working hard enough.
In a business the same logic is familiar. You cannot sell your way out of a broken supply chain, and one strong division does not fund a broken one indefinitely. The constraint sets the throughput, and the fix belongs where the constraint is.
Why the weakest is not automatically the priority
Priority does not go to the lowest reading. It goes to the lowest reading that is holding something else down - the one with something above it to release.
That distinction is what turns a diagnosis into a plan. The lowest number is a fact about the system. The lowest constraint is a decision about what to change next.
Why the read is a chain and not a score
A score places an operator against other people, which is not information anyone can act on. The chain places the levers against each other, which is.
It is also why two operators producing the same amount can need opposite things. The output is the same; the constraint is not, which means the useful intervention is not. Reading a total cannot tell those two people apart, and reading a chain can.
What the system does about it
REFORM treats the gap as the finding, rather than treating four levers as four separate problems to solve at once.
That is why the read begins by asking what is capping what rather than how each part is doing. The second question produces a list. The first produces a decision.
Where this leaves you
The leak is the distance between the operator you believe you are running and the one the evidence describes. It is not closed by effort, and it is not closed by working harder in the place that already looks busiest.
It is closed by looking in the right place, and then being willing to move the one thing that is holding the rest.
That is what the Performance Analysis is: four inputs, and the gap between them.
Dan.