Decision Rights Are an Operating Issue, Not an Org Chart Issue
Organizations often try to solve decision problems by clarifying reporting relationships.
Sometimes that helps.
But knowing who reports to whom does not necessarily tell people:
who decides;
who recommends;
who must be consulted;
who needs visibility;
or when a decision should move upward.
That is why decision rights are not simply an org-chart issue.
They are an operating issue.
The symptoms usually appear before the diagnosis
Unclear decision rights often show up as:
decisions taking too long;
the same issue being discussed repeatedly;
leaders escalating matters they should be able to resolve;
executives discovering that decisions were made without the right stakeholders;
committees revisiting decisions already made elsewhere;
staff waiting for approval that may not actually be required;
leaders exercising authority and then having it informally reversed;
multiple people believing they own the same decision.
None of those problems may look like a structural issue on paper.
But together they create friction throughout the operating system.
Authority is not the same as accountability
One of the most common problems is assigning accountability without matching authority.
A leader is told they “own” an outcome, but important decisions related to that outcome still sit somewhere else.
Or authority has been formally delegated, but the organization continues to behave as if permission is required.
That creates a predictable pattern:
responsibility moves downward while decision authority remains ambiguous.
Over time, leaders compensate.
They escalate more than necessary.
They seek informal approvals.
They build workarounds.
They delay action until they are certain they will not be second-guessed.
The organization becomes slower without anyone explicitly deciding to make it slower.
The question is not only “Who decides?”
That question matters, but it is not enough.
Good decision-rights design also clarifies:
What decisions belong at what level?
Which decisions require consultation versus approval?
What should trigger escalation?
What information is necessary before a decision is made?
When should the board exercise oversight rather than operational authority?
When should a senior executive decide rather than seek consensus?
What happens after authority has been delegated?
That final question is especially important.
Delegation is not meaningful if every consequential decision eventually returns to the delegating body.
Decision rights shape culture
Over time, unclear authority creates organizational habits.
People stop acting because they are unsure what is allowed.
Senior leaders become approval bottlenecks.
Boards move closer to operations because management does not appear to be making decisions.
Management hesitates because the board repeatedly revisits delegated decisions.
The result can look like a leadership problem, a trust problem, or a communication problem.
Sometimes it is all three.
But often the operating system has never clearly defined how authority is supposed to move.
Better decision rights create better accountability
Clear decision rights do not mean centralizing or decentralizing everything.
They mean being explicit about:
where authority sits;
where judgment is expected;
when escalation is appropriate;
and how accountability follows the decision.
When those elements align, organizations move faster without becoming less disciplined.
Clarity about who decides is one of the simplest ways to reduce friction without adding more process.
Related Carnot Advisory work
Executive & Board Advisory Organizational Assessment & Operating Model Review