Decision Rights Don't Fail — Interpretation Does

When the Decision Is Clear

When decisions don't translate into action the way leaders expect, one of the first places organizations look is decision rights.

Who owns the decision?

Who provides input?

Who needs to be consulted?

Who has the final say?

Those are important questions. And when authority is genuinely unclear, answering them can eliminate a lot of confusion.

But sometimes everyone already knows who gets to decide.

Imagine a leadership team debating priorities between two products competing for the same people and resources. After plenty of discussion, the decision is made:

Product A takes priority over Product B.

The decision owner is clear. The right people were involved. The outcome is documented and communicated.

No ambiguity about who decided.

And yet, a few weeks later, the organization isn't behaving as though everyone heard the same decision.

One team has shifted resources to Product A. Another is still working against its existing Product B commitments. A functional leader assumes Product A gets priority only when new work is assigned. Someone else assumes Product B should stop taking on work altogether.

Nobody is openly challenging the decision.

Nobody is confused about who had the authority to make it.

They just don't agree on what the decision means.

The decision right worked.

Something else didn't.

What Exactly Did We Decide?

“Product A takes priority over Product B” sounds clear.

It probably felt clear in the meeting too.

But what happens to Product B now?

Does its funding change?

Do people move immediately?

Do existing commitments still hold?

Can the team take on new work?

What happens the next time both products need the same engineer?

The original decision may not have answered any of those questions.

But someone has to.

So people do what people always do.

They interpret.

The product leader hears accelerate Product A.

The functional leader hears protect Product A when resources conflict.

The Product B team hears finish what we've already committed to, but don't add anything new.

None of those interpretations is obviously unreasonable.

And nobody has ignored the decision.

They're trying to follow it.

That's what makes the problem harder to see.

The decision may be clear. Its implications may not be.

What Leaves the Room

There's another reason this happens.

The people in the room where a decision is made know much more than the decision itself.

They heard the debate.

They know which alternatives were considered.

They understand the tradeoffs.

They know why Product A became the priority and what leadership was trying to accomplish by making it one.

Some of that context was probably written down.

A lot of it probably wasn't.

Then the meeting ends.

And what leaves the room might be:

Product A is now the priority.

That's accurate.

But it's also incomplete.

The decision travels farther than the conversation that produced it.

Now someone who wasn't in the room has to decide whether to move an engineer from Product B.

Someone else has to decide whether to delay a milestone.

Another leader has to decide whether a new Product B request should be approved.

They aren't making the original decision again.

They're deciding what it means here.

For this team.

For this commitment.

For this resource conflict.

A single decision has started producing dozens of smaller ones.

Most of them will be made by people who weren't in the room.

Decision Rights Solve a Different Problem

Clear decision rights still matter.

If nobody knows who can decide whether Product A or Product B gets priority, the decision can stall.

People escalate.

More people get pulled into meetings.

The same question gets discussed again because nobody is quite sure whether the last answer was final.

Clarifying authority helps.

But notice what it clarifies.

Who gets to decide?

The decision-rights model might work perfectly.

The right person made the decision.

The right people provided input.

The right stakeholders were informed.

And engineering, product, finance, and operations can still walk away with different ideas about what happens next.

Because knowing who made the decision doesn't necessarily tell everyone else what to do with it.

That's a different question.

What does the decision require from me?

The Decision Interpretation Gap

We tend to think of decisions as though they move through organizations intact.

A decision is made.

It's communicated.

People act on it.

But there's a step hiding in the middle.

Decision Made → Decision Communicated → Decision Interpreted → Decision Acted Upon

That third step matters.

Ten teams can hear the same decision.

All ten can understand the words.

And all ten can walk away with a slightly different idea of what they're supposed to do.

Usually those differences are small.

Often they don't matter.

Until they do.

A resource stays committed here.

A deadline doesn't move there.

One team stops accepting new work while another assumes nothing has changed yet.

Weeks later, leadership looks across the organization and wonders why the decision isn't being executed consistently.

The instinct may be to communicate it again.

Or clarify ownership.

Or reinforce the decision.

But the decision itself may have traveled just fine.

Its meaning didn't.

That's the Decision Interpretation Gap: the distance between what a decision meant when it was made and what people believe it means when they act on it.

And the farther a decision travels from the context that produced it, the more room there is for that gap to grow.

One Decision Becomes Many

And decisions don't just travel outward.

They multiply.

The Product A decision won't be executed once.

It will be executed again and again through smaller decisions made across the organization.

Move this engineer.

Delay that milestone.

Approve this request.

Decline that one.

Protect this commitment.

Escalate that conflict.

Each choice may seem small on its own.

But each one is also an interpretation of the original decision.

And then those choices start affecting other choices.

An engineer stays on Product B, so Product A's schedule changes.

That schedule change affects another team's dependency.

The dependency forces someone else to reconsider a commitment.

That commitment affects a customer conversation.

Before long, one leadership decision has become a chain of decisions spread across teams, functions, and levels of the organization.

Nobody decided to change the original decision.

Nobody necessarily disagreed with it.

They just kept making reasonable choices based on what they believed it meant.

That's how a small interpretation gap can become something much larger.

Not all at once.

One decision at a time.

Who Decides Is Only Half the Question

Organizations need clear decision rights.

They need to know where authority sits.

Who provides input.

Who makes the call.

When the decision is final.

None of that goes away.

But the original decision is only the beginning.

Knowing who decided doesn't tell everyone else what the decision changes.

What stays the same.

Where discretion remains.

Or what they should do differently tomorrow.

That's where a decision becomes real.

Not when it appears in the meeting notes.

Not when it's added to the decision log.

Not even when everyone has heard it.

When people begin making decisions of their own because of it.

A decision can be perfectly clear in the room where it was made and increasingly fragmented everywhere else.

Not because people ignored it.

Not because the decision rights failed.

But because decisions don't execute themselves.

Organizations don't execute decisions. They execute their interpretation of them.