Where Is Your Best Judgment Going?

Every good business should depend on capable people.

That is not a flaw.

A strong account lead should notice what a checklist cannot.

A senior operator should recognise patterns that a new hire misses.

A commercial leader should know when an unusual deal deserves flexibility.

A creative director should be able to distinguish technically correct work from work that is actually good.

Expertise matters precisely because not every decision should be reduced to a rule.

The operating problem begins somewhere else.

It begins when the organisation spends that expertise on questions that should no longer require expertise.

Where is the latest version?

Who approved this?

Was this included in scope?

Which price applies?

Who owns the handoff?

Did the client confirm?

Why does this number not reconcile?

Can somebody remind the team what was decided last time?

A capable person answers.

Work continues.

The result may be excellent.

But something important has happened.

The organisation has used scarce human judgment not to create additional value, but to compensate for missing structure.

Those are two very different uses of competence.

Two kinds of judgment

Consider two situations.

In the first, a long-standing customer asks for an unusual commercial arrangement.

The decision involves relationship history, future opportunity, margin, precedent and trust.

There may be no formula capable of producing the correct answer.

A strong commercial leader should probably make that judgment.

Now consider another.

The same commercial leader is asked whether a standard service includes three revisions or five because nobody can find the current scope document.

Both situations consume an experienced person’s time.

Both may involve a decision.

But they are not the same kind of work.

The first is value-creating judgment.

The second is compensatory judgment.

Value-creating judgment exists because reality is genuinely ambiguous.

Compensatory judgment exists because the organisation is ambiguous.

That distinction matters.

One is why experienced people are valuable.

The other is how experienced people become infrastructure.

Competence is not the problem

There is an increasingly common operating argument that businesses should stop relying on heroes.

There is truth in it.

But taken too far, it produces another bad idea:

that a mature organisation should somehow become independent of individual excellence.

It should not.

Great businesses should still benefit disproportionately from great people.

A brilliant salesperson should outperform an average one.

An exceptional operator should see more.

A strong manager should make better trade-offs.

A craftsperson should bring judgment no SOP can manufacture.

The objective is not to make competence unnecessary.

It is to stop wasting competence on avoidable ambiguity.

That is a different design problem.

The question is not:

Does this business depend on talented people?

Of course it does.

The better question is:

What does it depend on those talented people for?

Some expertise expands the business. Some merely keeps it intact.

This becomes easier to see when the work is separated by function.

A senior operator might spend Tuesday morning redesigning a delivery model that could improve margin across every future project.

That is leverage.

Tuesday afternoon, the same person spends two hours reconciling why three teams have different understandings of the same client deadline.

That is compensation.

A finance leader may model the cash implications of several strategic choices.

Leverage.

Then manually reconstruct a commercial decision because the approval exists across an email, a WhatsApp thread and somebody’s memory.

Compensation.

An account director may recognise that a client's repeated requests point to a larger opportunity nobody has yet framed.

Leverage.

Then chase four internal people to determine who is supposed to approve the next step.

Compensation.

From a timesheet, all of it can look like senior work.

From an operating perspective, it is not.

Some senior attention is producing judgment the organisation could not cheaply obtain elsewhere.

Some senior attention is being consumed because the organisation never removed a recurring reason to need it.

The strongest people make compensation look effortless

This is part of what makes the problem difficult to see.

Competence is efficient.

An experienced employee knows who to call.

They remember the precedent.

They understand which rule matters and which one can safely bend.

They can reconstruct missing context quickly.

They know that the CRM says one thing but the email from March contains the real answer.

They understand why the founder will reject a proposal before anyone sends it upstairs.

So they solve the problem.

Often in minutes.

The organisation experiences very little visible friction.

That is precisely why the underlying cost can survive.

A weak employee may expose an unclear process immediately.

A strong employee can absorb it for years.

The result still arrives.

The client remains happy.

The dashboard stays green.

And a badly designed question continues consuming good judgment.

Look at what your strongest people are interrupted for

Job descriptions are not particularly useful here.

Calendars are better.

Slack messages are better.

Escalations are better.

Questions are better.

Take several of the people considered highly dependable inside the business.

Then examine what repeatedly reaches them.

Not the work they were hired to own.

The interruptions.

“Can you quickly check this?”

“Do you remember what we agreed?”

“Who normally approves this?”

“What should we do here?”

“Can you speak to them?”

“Can you fix this before it goes out?”

“Does this look right?”

Some of those interruptions will be entirely appropriate.

Others will expose a pattern.

The same questions.

The same missing context.

The same handoff.

The same interpretation.

The same rescue.

That is useful evidence because repeated requests for judgment often indicate one of two things:

the decision genuinely belongs with expertise;

or

the system has failed to make a repeatable decision cheap.

The job is to tell the difference.

Ask whether the uncertainty is inherent or manufactured

This may be the cleanest test.

Some uncertainty is inherent in the work.

A difficult customer negotiation.

A novel technical problem.

A strategic trade-off.

An unusual people decision.

A genuinely new market condition.

No operating system should pretend these can be completely standardised.

Then there is manufactured uncertainty.

Nobody knows which document is current.

Two functions have overlapping authority.

A threshold was never defined.

The same exception has occurred fourteen times but remains unofficial.

Information exists but does not reach the person who needs it.

A decision was made previously but no principle travelled with it.

A handoff technically exists but nobody agrees when ownership actually transfers.

These situations feel like judgment calls because somebody must still decide what to do.

But the need for judgment was created by the organisation itself.

That is the difference.

Good systems reduce manufactured uncertainty so people can spend more judgment on inherent uncertainty.

That is a far more realistic objective than eliminating judgment.

The best person is not always the right diagnostic sample

There is another trap here.

When leadership wants to understand whether a process works, it often asks the most experienced person.

“How does this normally happen?”

The expert explains it.

The process sounds perfectly coherent.

Of course it does.

The expert has already filled in every missing part.

They know that Step 4 actually requires checking something not mentioned in Step 3.

They know which customer type requires a different rule.

They know not to trust a certain field until another team confirms it.

They know which manager really has authority.

Much of that knowledge may be so familiar that it no longer feels like a workaround.

So the organisation documents the expert’s description and concludes the process is healthy.

A more revealing test is to watch someone competent but less embedded attempt the same work.

Where do they stop?

What do they have to ask?

Which answer exists only in another person’s head?

What do they interpret differently?

Where does the documented process cease to be enough?

The gap between expert fluency and competent repeatability is often where the operating debt lives.

Do not automatically turn expert judgment into an SOP

This is where the diagnosis can easily become too mechanical.

A senior person repeatedly makes a decision.

Therefore document the decision.

Problem solved.

Not necessarily.

Some judgment should remain judgment.

Turning every expert decision into a rule can remove exactly the discretion that made the expertise valuable.

Suppose a senior account lead repeatedly resolves delicate customer issues.

The wrong intervention may be a twenty-page escalation manual.

Perhaps the useful system change is much smaller:

make the relevant commercial context visible;

clarify what decisions account leads can make independently;

define the conditions that genuinely require escalation;

and let experienced people continue exercising judgment inside that space.

The purpose of operating design is not to convert people into executors of rules.

It is to determine where rules create leverage and where judgment creates value.

Compensation can become part of somebody’s identity

There is also a human complication.

Some people become exceptionally good at being needed.

They are the person who knows.

The person who fixes.

The person everyone calls.

That can carry status.

Trust.

Influence.

A sense of importance.

Sometimes even career progression.

So removing compensatory work is not always experienced as relief.

A stronger system can feel like territory disappearing.

This does not make the person difficult or selfish.

It simply means dependency can become culturally reinforced from both directions.

The organisation praises someone for repeatedly saving the situation.

The person becomes increasingly skilled at saving it.

Nobody gains much status from ensuring the situation no longer needs saving.

This is why the behaviour an organisation celebrates deserves attention.

If rescue is visible and prevention is invisible, competence will naturally accumulate around rescue.

Recognition can accidentally preserve the problem

Imagine two employees.

One notices that client approvals repeatedly arrive late.

Every week, they chase the customer, alert Delivery, rearrange schedules and protect the deadline.

They become known as incredibly dependable.

Another employee redesigns the approval point so late approval becomes visible before resources are committed.

The recurring rescue disappears.

Who appears busier?

Who receives more public thanks?

Who seems indispensable?

Often the first person.

The second employee has removed the evidence of their own value.

That creates an operating paradox.

The person who solves incidents creates visible performance.
The person who removes the recurring cause can make their contribution disappear.

A mature organisation needs to recognise both.

Otherwise it can unintentionally reward compensation more than improvement.

The objective is not redundancy. It is leverage.

There is a crude test often proposed for key-person dependency:

What happens if this person disappears for two weeks?

Useful.

But incomplete.

A business should care if an exceptional commercial leader disappears.

A great designer leaving should matter.

Deep expertise leaving should have consequences.

If nothing changes when an excellent person leaves, perhaps the organisation was not receiving much benefit from their excellence in the first place.

The better test is narrower:

What stops because this person’s expertise is genuinely valuable—and what stops because basic operating structure followed them out of the building?

Those should not be confused.

The first is a talent risk.

The second is an operating design risk.

One may require succession, development or retention.

The other requires the organisation to reclaim responsibilities it has quietly outsourced to a person.

Build a judgment ledger

There is a practical way to make this visible without launching a transformation programme.

For one week, ask a few highly depended-on people to note every time somebody comes to them for a decision, clarification, rescue or interpretation.

Nothing elaborate.

Record:

what the question was;

why it reached them;

whether it had occurred before;

whether someone else could reasonably have answered it;

and what would have had to exist for the question not to require them.

Then classify the requests.

Expert judgment — the value genuinely sits in experience.

Transferable judgment — others could develop the capability with exposure, context and authority.

System compensation — the question exists because information, ownership, standards or process are missing.

Noise — the decision did not meaningfully require judgment at all.

The exercise will not produce a perfect taxonomy.

It does not need to.

Its purpose is to expose where scarce judgment is being spent.

That can change the operating conversation.

Instead of:

“Sarah is overloaded.”

the problem may become:

“Sarah receives fifteen recurring questions a week that should never need Sarah.”

Those diagnoses lead to very different interventions.

Do not remove all compensatory behaviour at once

There is counter-evidence worth respecting.

Workarounds can be intelligent.

In young organisations, informality can be faster than premature structure.

During a crisis, exceptional people may need to absorb work the system was never designed to handle.

A temporary customer issue may be cheaper to solve through judgment than through process redesign.

And some recurring work remains too variable to standardise economically.

The presence of compensation is therefore not proof of failure.

The useful questions are frequency, consequence and persistence.

Is this happening often enough to matter?

Does it consume scarce capability?

Does it expose the business when the person is unavailable?

Has the workaround survived long enough that “temporary” is no longer credible?

Would removing the underlying ambiguity create more leverage than the redesign costs?

That is the threshold for intervention.

Not ideological purity.

A good system makes excellent people more valuable

This is perhaps the most important distinction.

Systems are sometimes discussed as though their purpose is to protect a company from its dependence on people.

That is too defensive.

A good operating system should make strong people more valuable, not less.

It should stop asking a commercial leader where the latest document is.

So they can spend more time making commercial judgments.

It should stop asking a senior operator to reconnect routine handoffs.

So they can redesign the way work moves.

It should stop asking experienced managers to answer the same ambiguity repeatedly.

So their experience can be spent on situations the organisation has not encountered before.

That is leverage.

Not replacing judgment.

Protecting it.

Because the scarce resource in a growing business is not simply talent.

It is what that talent gets to spend itself on.

Before celebrating how much the strongest people can handle, look at what they are actually handling.

Some of it may be the reason they were hired.

Some of it may be evidence that the organisation is using expensive judgment to pay for cheap ambiguity.

The distinction is worth finding.