The Judgment Gap what closes it, and what that costs › Reducing what needs judgment is the only move that scales 12 steps, no labs
10 — part 4, what closes it, and what that costsreasoning

Reducing what needs judgment is the only move that scales

The only remedy that gets bigger as the problem does is making less of the work need somebody to judge it.

One move gets bigger as the problem does, and it is the only one. Make less of the work need somebody to judge it.

work produced work examined the only change that makes the level fall the remainder, falling narrower intake: less of what is produced needs somebody to judge it narrower tasks outputs checkable without understanding them failures that surface themselves less produced on purpose each one trades some capability for checkability. That is a real trade and it is presented as one. and this is the only scene in the volume where it goes down.
The same rig with a narrowed intake rather than widened checking. This is the only scene in the volume where the level goes down.
What moves: the intake narrows and the reservoir drains across the cycle, with four moves that narrow it listed below.
the movewhat it trades awaywhere it works best
narrower tasks — ask for less at oncesome capability, and some convenienceanywhere the output is currently large enough that judging it means reading all of it
outputs checkable without understanding themexpressiveness. A structured answer is easier to check and says lessanything where the result can be tested rather than read
failures that surface themselvesengineering effort, up frontanywhere a wrong answer currently looks like a right one
producing less on purposethroughput, visibly, and it is the least popular row herewhere the marginal work was not worth judging and therefore is not worth having

Each of these is a trade and the volume says so

None of them is free, and presenting them as free is how the plan gets adopted and then resented. Narrower tasks mean more round trips. Checkable outputs are less expressive. Self-surfacing failures cost engineering time that could have gone to features. Producing less is producing less.

What makes them different from part three's remedy is not that they are cheap. It is that they scale: each one reduces the amount of judgment needed per unit of work, so the benefit grows with production instead of having to keep pace with it.

The second row is where most teams have the largest gain available. A great deal of output is currently free-form because nothing forced it not to be, and structuring it converts judgment into a check. That is not a small engineering project and it is the one with the clearest payback.

Every term this page uses

produced-to-examined
How much work your team produced, divided by how much of it somebody actually looked at.
examined
Looked at by somebody with enough context to have caught a problem. Not the same as having passed through a review step.
remainder
Work that was produced and not examined. It does not go anywhere — it merges into what everything after it is built on.
judgment
Deciding whether a piece of work is good, which needs knowing the domain well enough to recognize a wrong answer.
inspection
Checking finished work at the end, rather than changing how the work is made.
checkable
Able to be judged without understanding the whole of it. The property that decides how much needs judgment at all.
constraint
The thing that limits output. Adding more of anything else does not help until it moves.
rework
Work that had to be revisited after somebody called it done.
vigilance
Staying alert for a rare problem across a long stretch of time.

Taken as already known, and so not defined here: agent, model, review, throughput, headcount. That list is a claim about who is reading, and it is printed so it can be argued with.