You delegated the work. Not the judgement.

Here's one of the biggest lies in delegation: "just give people more ownership."

Ownership without judgement creates mistakes.

Delegation says: "You now own client onboarding."

Judgement transfer says: "Here is how we think about client onboarding, what good looks like, what trade-offs matter, what you can decide, and when your judgement should override the process."

That is how you eventually make yourself unnecessary in your business. Only if you want to.

Why delegation keeps failing

People struggle with delegation because most delegation is really task transfer without decision transfer.

The founder says: "You own this now."

But what they actually mean is: "You own it, as long as you do it roughly the way I would."

That creates a pretty trap. The employee has responsibility without the founder's context, standards, pattern recognition or permission to make trade-offs.

So they either make bad decisions, keep asking for approval, or the founder keeps correcting them. Then the founder concludes:

• "Delegation doesn't work."
• "I need better people."
• "Something's wrong, I don't know what."

The main reasons it fails are pretty predictable:

• The outcome isn't clear. People are told what to do, not what success actually means.
• The founder's standards are invisible. The founder has hundreds of unwritten rules in their head.
• Decision rights are fuzzy. The employee doesn't know what they can decide without permission.
• The founder delegates work but keeps exceptions. Normal cases go to the team; anything difficult comes straight back.
• People are punished for reasonable mistakes. They quickly learn that asking permission is safer than exercising judgement.
• The founder intervenes too early. The team never gets enough repetitions to develop pattern recognition.
• The wrong person was hired. Some roles require far more judgement than the employee actually possesses.
• The founder confuses difference with incompetence. If the employee does it differently, they assume it's wrong.
• There is no feedback loop. People make decisions but never understand why they were good or bad.

Delegation vs judgement transfer

They're not really competitors.

Delegation transfers ownership. Judgement transfer transfers decision quality. You need both.

But judgement transfer becomes especially important when the work is ambiguous. Traditional delegation works very well when the task is predictable:

• Send invoices every Friday
• Publish this report
• Follow this onboarding checklist
• Upload these assets
• Schedule these meetings

Judgement transfer matters when the person has to answer "what should we do?" rather than "what are the steps?"

A useful distinction

Low variability plus low consequence, delegate the task. High variability plus meaningful consequence, transfer judgement.

For example:

• Running the onboarding checklist. Delegation.
• Deciding whether a difficult new client should bypass the normal onboarding. Judgement transfer.
• Posting approved content. Delegation.
• Deciding how to respond to a public client complaint. Judgement transfer.
• Scheduling interviews. Delegation.
• Deciding whether a candidate has leadership potential. Judgement transfer.

When do you hire for judgement instead?

The reality is that when we want better judgement inside our business, we hire for it. So in what cases do we hire for it, and when do we simply transfer it?

The cleanest rule is: hire for judgement capacity, transfer company-specific judgement.

You should not try to teach someone from scratch to become commercially sharp, emotionally mature, analytical, decisive, and comfortable with ambiguity. That is largely what hiring is for.

But even a brilliant operator cannot walk into your company and instantly know how your business should make decisions. That part has to be transferred.

Think of judgement as having two layers:

1. General judgement. How good is this person at thinking?
2. Company judgement. Do they understand how we think?

You mostly hire for the first and develop the second. I'll explain this part in depth in one of the next newsletters.

Seniority changes the ratio

The more senior the role becomes, the less useful pure delegation becomes.

A junior person's job may be 80% execution and 20% judgement. A Head of Delivery might be 40% execution and 60% judgement. A COO is effectively a professional decision-maker.

At that point, giving them more SOPs doesn't solve the problem. You have to teach them what matters, what doesn't, what trade-offs the company accepts, when rules can be broken, how much risk is acceptable, and how the founder reasons when information is incomplete.

That's why I think the progression looks like this:

The final stage is not "my Head of Ops can do my tasks."

It's "my Head of Ops can face a situation neither of us has seen before and still make a decision I trust."

That's real autonomy.

And this also explains why judgement transfer is particularly valuable in founder-led businesses. The founder is often not the bottleneck because they physically do too much work. They're the bottleneck because the organisation believes: "when something unusual happens, Romans needs to think about it."

Judgement transfer attacks that dependency directly.