The Allocation Gap

Sometimes the judgment an organization needs is already in the room.

It still doesn't make the decision.

Someone understands the customer. Someone sees the technical constraint. Someone recognizes the consequence of a choice before it is made. Sometimes they even say exactly what later turns out to have been true.

And the organization chooses differently.

When that happens, it is tempting to conclude that something was missing. Maybe the team needed better data. Maybe the right expertise wasn't involved. Maybe leadership didn't understand the customer well enough.

Sometimes that's exactly what happened.

But sometimes the capability was present. The organization simply couldn't convert it into consequence.

That creates a different kind of problem.

If the person closest to the problem understands something important but doesn't have the authority to act on it, perhaps the answer is straightforward: put the decision where the judgment is.

Clarify ownership. Establish decision rights. Give capable people the authority to decide.

There is a lot to like about that answer.

Until you remember that organizations with perfectly clear decision rights still make terrible decisions.

Authority doesn't make someone's judgment good. A person can have unquestioned ownership of a decision and still misunderstand the customer, work from incomplete information, optimize for the wrong outcome, ignore contrary evidence, or simply be wrong.

So judgment and authority are not the same organizational resource.

And having both somewhere in the organization isn't enough.

They have to meet.

That space between the judgment an organization possesses and the legitimate authority that allows it to become consequential is what I think of as the Allocation Gap.

The gap can be surprisingly difficult to see because nothing on either side necessarily looks broken.

The organization may have extraordinarily capable people. It may also have clearly defined leaders, responsibilities, approval processes, and governance.

Yet the person with the strongest understanding of a particular problem may not be the person who can decide what happens next.

This becomes especially visible when work crosses organizational boundaries.

A customer problem rarely arrives neatly divided according to the structure of the company trying to solve it. The customer experiences one problem. Inside the organization, that problem may pass through Product, Engineering, UX, Sales, Marketing, Legal, Operations, Support, or any number of other functions.

Each may possess legitimate expertise.

Each may also possess legitimate authority over some part of the work.

The difficulty appears when those boundaries don't correspond to the decision that actually needs to be made.

Then everyone can be behaving rationally within their own responsibilities while the larger decision remains strangely ownerless.

The obvious response is more clarity.

But I don't think the answer is perfect clarity.

I've seen teams create enough local clarity to make good decisions even when the larger organization remained ambiguous. Someone was explicitly delegated authority. A group agreed who would make a particular call. A person's credibility gave their judgment legitimate weight. People working across different functions established enough shared understanding about where a decision belonged that the work could move.

None of those required redesigning the entire organization.

What mattered was less whether authority had been perfectly formalized than whether relevant judgment had enough legitimate authority to affect what happened next.

That distinction is important because otherwise the Allocation Gap can easily become an argument for more governance.

And more governance isn't always the answer.

Not every decision needs an explicitly named owner. Many decisions are reversible, low consequence, or sufficiently understood that distributed autonomy is more useful than carefully specified authority.

There are also moments when ambiguity is doing useful work.

Early in discovery, a team may still be learning what the problem actually is. Assigning authority too quickly can harden one interpretation before competing possibilities have been explored.

Sometimes the right question isn't yet who should decide?

It may be are we ready for this to be a decision yet?

That makes allocation more complicated than moving authority closer to expertise.

Too little legitimate authority and capable judgment may never influence the outcome.

Allocate authority too early and the organization may constrain the discovery required to develop good judgment in the first place.

And even when the timing and allocation are right, there is still no guarantee of a good decision.

Clear authority cannot compensate for poor judgment.

It cannot manufacture customer understanding, eliminate distorted incentives, correct incomplete information, or make someone willing to reconsider what they believe when the evidence changes.

Authority can make judgment consequential.

It cannot make judgment sound.

Which may be why some decision failures are so difficult to diagnose.

After a consequential decision goes badly, organizations naturally ask whether they had the right information, whether the right expertise was involved, or who owned the decision.

Those are useful questions.

But there may be another one worth asking:

Where did the relevant judgment actually live, and did we create the conditions for it to matter?