Judgement is the new bottleneck

For most of the history of organised work, the hard part was doing things. Producing a report took days. Building a prototype took weeks. Analysing a market took a team. The limit on what an organisation could achieve was its capacity to execute, and most of management grew up around that limit: planning work, allocating people, tracking delivery.

That limit is moving. A first version of a report, a working prototype, a competitive summary, a set of options — each can now be produced in a fraction of the time it used to take. The output is not always good, but it is fast and it is cheap, and it is getting better.

When one constraint loosens, another becomes visible. If producing things is no longer the bottleneck, the bottleneck becomes deciding which things are worth producing, recognising which of the results are any good, and choosing what to do with them. In a word: judgement.

It is tempting to believe that faster execution makes leadership easier. In practice it makes it harder, because it multiplies the number of choices that need to be made.

A team that used to produce one proposal a month can now produce five in a week. Someone has to decide which one deserves attention. A product team that could test one idea a quarter can now test ten. Someone has to decide what each test was supposed to prove, and whether it did. An analyst who used to deliver one carefully prepared view can now deliver a dozen variations. Someone has to decide which is right.

Every one of those decisions lands on a person whose time and attention have not increased at all. The organisation gains speed in production and loses it in review. Work queues up waiting for someone to say yes, no or not yet. The bottleneck is no longer the factory floor; it is the desk of whoever has to decide.

Judgement is often treated as a mysterious quality that some people have and others lack. It is more useful to treat it as a set of distinct capabilities, each of which can be recognised and improved.

None of these is made obsolete by faster production. All of them become more important, because they are now the only things standing between an organisation and a flood of plausible, unexamined output.

There is a quieter danger alongside the bottleneck. When options are cheap, it becomes easy to let the options do the thinking. A tool proposes three strategies; the team picks the one that sounds best. A summary arrives; nobody reads the underlying material. A recommendation is generated; it is adopted because it is well written.

Each of these is a decision made without judgement — a choice between outputs rather than a view about the problem. Over time, an organisation that works this way loses the capacity it most needs. People stop forming their own view before seeing the options. They stop reading source material. They stop asking whether the question was right.

The defence is simple and slightly old-fashioned: form your view first. Before asking for options, write down what you think the answer is and why. Then compare. Where the options differ from your view, find out why. Sometimes you will learn something; sometimes you will catch an error. Either way, the judgement stays yours.

If judgement is the scarce resource, it deserves the kind of attention that organisations used to give to production capacity.

Judgement is finite. Senior attention, in particular, is the most limited resource in most organisations. Be explicit about which decisions need it and which do not. Push decisions down to the people closest to the information wherever the risk allows, and keep senior judgement for the choices that are hard to reverse, expensive to get wrong or genuinely uncertain.

Write decisions down: what was decided, by whom, on what evidence, and what would cause it to be revisited. A simple decision log does three things at once. It forces clarity at the moment of deciding. It allows the organisation to learn from its decisions later. And it stops the same question being decided several times by different people.

Review processes built for slow production break under fast production. If every document still passes through the same approval chain, the chain becomes the constraint. Better review is lighter and earlier: agree the question and the criteria before the work begins, so that judging the result becomes a quicker comparison against something already agreed.

Judgement grows through practice with feedback. Give people real decisions earlier in their careers, at a scale where mistakes are survivable. Review decisions — not only outcomes — so that a good decision with an unlucky result is recognised, and a poor decision with a lucky result is not rewarded. Ask people to explain their reasoning, and take the explanation seriously.

For a long time, the question an organisation asked of its people was: can you deliver? That question is not going away, but it is becoming easier to answer yes. The question that now separates strong organisations from busy ones is different: can you decide well?

Deciding well means choosing the right problems, recognising good work, weighing what each choice costs, stopping at the right time and owning the result. It cannot be generated on demand. It is built slowly, through experience, attention and honest reflection.

When execution gets cheap, that is where the advantage moves. Not to the organisation that produces the most, but to the one that knows what is worth producing.