When judgement lives in five heads

The thing that makes an expertise-led company valuable is usually the thing that limits it. Judgement built over decades sits with a handful of people. Every difficult decision waits for one of them, and the company cannot grow faster than their calendars allow.

How do you know judgement is the constraint?

The signs are operational rather than financial, which is why they are missed for years.

Work stops when specific people take leave. Juniors produce drafts that are technically correct and commercially wrong. Clients ask for a named person rather than the company. Reviews find the same corrections being made again on different jobs.

Why does hiring not fix it?

Because you are hiring for output and the shortage is in judgement. A new senior hire takes a long time to be trusted with the calls that matter, and the people who could accelerate that are the same people who have no time.

Key person risk, as Mayfly Ventures defines it for expertise-led firms, is the gap between what the company sells and what it can prove it owns without a specific person in the room.

What is actually inside the bottleneck?

Less than people expect, and it is rarely mysterious.

• The questions asked in what order. Experienced people triage differently, and they do it fast.
• The thresholds. What counts as acceptable, what needs escalation, what is refused outright.
• The exceptions. The cases where the standard answer is wrong, and the reason why.

None of that is written down anywhere. It shows up in review comments and corridor conversations.

Can judgement be captured?

Parts of it. Not the relationship, and not the accountability, but the structure underneath the decision can be made explicit and reusable.

The test is simple. If a capable person one level down can reach the same conclusion as your best reviewer, on a real job, without the reviewer being available, the judgement has moved.

What does capturing it look like in practice?

It starts with watching real work rather than running a workshop. Decisions get recorded as they happen, with the reasoning attached. Patterns emerge within a handful of cases.

Then the structure gets built into the work itself, so the next person meets the questions in the right order instead of being handed a document to read.

Documenting knowledge is not the same as capturing judgement. A written procedure describes what was decided. Captured judgement reproduces how the decision was reached.

Where to start

Name the two people every hard job waits for. Take the last ten decisions they escalated or reversed, and write down why for each one.

If a pattern shows up in ten, it will hold across a hundred. That is the beginning of an asset the company owns.