What decision rights actually are
A decision right is the explicit answer to a simple question:
Who decides?
Not who should probably decide. Not who usually handles things like this. Not who is most senior in the room.
Who has the authority to make the call? And who owns the outcome once the call is made?
Most growing businesses have never answered that question for the decisions that matter most.
They have organization charts. They have titles. They have reporting structures.
But an organization chart tells you who reports to whom. It does not tell you who decides. The gap between those two things is where a lot of organizational friction lives.
The org chart is not enough
Here is what happens in a business that has reporting lines but not decision rights.
A decision comes up. Something needs to happen. People start talking about it. The conversation includes whoever is most available, most vocal, or most senior.
Sometimes a decision gets made. Sometimes the conversation loops: same question, different meeting, same people, no resolution.
Eventually something happens. Not because someone made a deliberate call. Because someone got tired of waiting and acted. Or because the deadline passed. Or because the decision made itself.
That is how critical decisions quietly get made in growing businesses: by default, exhaustion, or circumstance.
And because nobody explicitly decided, nobody explicitly owns the outcome. When something goes wrong, accountability gets blurry. The decision did not have an owner. So the consequence does not either.
The three roles that actually matter
For any decision that matters, there are three distinct roles. Mixing them up is where the meeting fog rolls in.
Role
Decides
Has the authority to make the final call. Listens to advice. Considers input. But when the moment comes, they decide and everyone else moves based on that decision. There is exactly one person in this role for any given decision.
Role
Advises
Has relevant expertise or perspective. Is asked for input before the decision is made. Their advice matters. But they do not have veto power, and they are not responsible for the outcome.
Role
Informed
Needs to know the decision was made and what it was. May need to act on it. But is not part of making the decision.
Most organizations I see at an inflection point collapse all three roles into one undifferentiated group of “stakeholders.” Everybody has a say. Nobody decides. Meetings loop. Work stalls.
What usually goes wrong
Four patterns show up consistently.
01
Too many deciders
When three people all think they decide, what you have is not a decision right. It is a committee. Committees can advise. They can pressure-test. They can surface risk. But they do not create clean authority.
FixOne person decides. Others advise.
02
The decider is not named
“Usually Keisha handles this, but sometimes it is Marcus, depending on the situation.” That is not a decision right. That is a guess wearing a blazer.
FixName one person. Make it visible.
03
Advisors are not asked
The process says someone advises, but when the moment comes, nobody asks them. They find out after the fact. They feel bypassed. Confidence in the process drops.
FixBuild the ask into the process. Make it a step, not an afterthought.
04
Informed people find out last
Decisions get made and communicated to the people directly involved. Days later, someone who needed to know finds out through a forwarded email, a hallway conversation, or a meeting recap they were not invited to read. By then, they may have already made plans that conflict with the decision.
FixInformed people get told when the decision moves, not after the ripple effects have already started.
The question that changes the conversation
Every assessment starts with the same question across critical functions, major decision types, and recurring cross-team friction points:
Who is the someone who will do this?
Not who should do this. Not who could do this. Who will actually do it, and who owns the outcome if it does not happen?
The answer, made explicit and visible, is a decision right.
Most organizations discover that the answer is less clear than they thought. Some decisions have multiple owners. Some have none. Some have been delegated so many times that the chain of authority has gone foggy.
Once those answers are mapped, the path forward becomes easier to see. Meetings get shorter. Loops stop sooner. People start moving.
The business consequence of getting this right
Decision rights are not a governance formality. They are a speed mechanism.
The businesses that move fastest are not always the ones with the smartest people or the thickest strategy deck. They are the ones where everyone knows who decides.
Advice gets heard. Decisions get made. Execution follows.
The businesses that move slowly are the ones where decision rights are fuzzy. Meetings loop because nobody is sure who has the authority to close the conversation. Accountability fades because the decision did not have a clear owner.
Mapping decision rights for the decisions that actually matter, including hiring, pricing, client commitments, strategic direction, and operational changes, is one of the highest-leverage structural changes a growing business can make.
It does not require a reorganization. It does not require another tool. It requires an honest conversation, a visible record, and the discipline to use it when the moment comes.
Three questions. Start here.
For each decision that matters, answer three questions:
- 01
Who decides?
One name. Not a title. A name.
- 02
Who advises?
The two or three people whose input should be sought before the decision is made.
- 03
Who is informed?
Everyone who needs to know the outcome and may need to act on it.
Write it down. Make it visible. Revisit it when the business changes.
That is a decision right.
And once those are in place, the board meeting that ran for ninety minutes can take twenty minutes and end with someone moving.
That conversation is exactly what The Structure Read is built for.
Structure creates confidence. Visibility protects growth.