People adapt quickly to where authority actually lives.
They learn who can say yes, who can quietly say no, whose opinion must be pre-cleared, which decisions can be made locally, which decisions will be reopened, and which forums are theater because the real decision happens somewhere else.
That map shapes behavior faster than any values statement because people optimize for the path that actually moves a decision.
Formal authority is only part of the system
The org chart says who manages whom. It does not fully explain who decides.
In most companies, decision authority is distributed across titles, expertise, founder trust, customer proximity, budget ownership, tenure, politics, and informal credibility. Some of that is healthy. Companies need judgment and context, not just boxes.
The problem begins when the authority map is hidden, contradictory, or different from the accountability map.
A team is told it owns the roadmap, but sales can commit roadmap changes through executive escalation. A functional leader is told to run their department, but every meaningful hire requires founder intuition. A cross-functional initiative has an owner, but every function retains veto power. A strategy is approved, but anyone with enough influence can reopen the core tradeoff.
People see this quickly. Then they optimize around it.
Ambiguous decision rights create political behavior
When people do not know who decides, they do not stop caring. They build influence paths.
They pre-wire decisions. They gather allies. They delay commitment. They ask for more alignment. They escalate indirectly. They interpret silence as disagreement. They treat meetings as performances rather than decision forums.
Leaders may call this politics. Sometimes it is. But often political behavior is a rational response to unclear decision rights.
If the operating system does not tell people how decisions get made, they will invent a system.
Veto power is the hidden authority
The most important authority is not always who can approve. It is who can block.
A legal team may not own product strategy, but it can effectively veto product choices. Finance may not own hiring strategy, but it can shape every plan through headcount control. A founder may not officially own every product decision, but a raised eyebrow can stop a team cold. A large customer may not sit inside the company, but their threat to churn can override internal priorities.
Some veto power is necessary. The issue is whether it is explicit, bounded, and reviewable.
Unclear veto power creates learned helplessness. Teams stop making decisions because they expect the decision to be reopened by someone with shadow authority.
Decision rights must match consequence
The person who decides should usually be close to the consequences of the decision, with appropriate constraints.
Reversible, local decisions should be made close to the work. Irreversible or brand-risk decisions need higher scrutiny. Cross-functional tradeoffs need a forum with authority over the tradeoff, not just representatives from each function. Strategic allocation decisions belong with leaders who can actually move resources.
Problems arise when decision rights are assigned by habit rather than consequence. Too many decisions route upward because leaders are anxious. Too many decisions stay local because leaders want empowerment without alignment. Too many decisions require consensus because no one wants to own the tradeoff.
Useful decision design names the DRI, required input, veto boundaries, escalation path, and review point. Without those five pieces, "empowerment" often becomes abandonment or politics.
After the decision matters as much as before
Decision rights are not only about who makes the call. They are also about what happens after.
Can the decision be reopened? By whom? Under what conditions? What new information would justify reconsideration? What is expected from people who disagreed? How is the decision recorded? How will the company know if it was wrong?
If these rules are unclear, disagreement migrates into execution. People comply slowly, hedge, revisit, or wait for the next forum.
A decision that cannot survive implementation was not actually decided. The company only held a meeting.
Run the decision-rights reality map
Pick five recurring decision types:
- Product prioritization.
- Pricing exceptions.
- Hiring approvals.
- Customer escalations.
- Quality gates.
- Resource reallocation.
- Incident response.
- Strategic tradeoffs.
For each, map:
- Who is supposed to decide?
- Who actually decides?
- Who has input?
- Who has veto power?
- Who can reopen the decision?
- Where is the decision recorded?
- Who absorbs the consequences?
- What new information is sufficient to reopen it?
The gap between supposed and actual authority is where behavior gets distorted.
Authority is culture in motion
A company that says it values ownership but centralizes every meaningful decision teaches dependency. A company that says it values alignment but allows side-channel vetoes teaches political navigation. A company that says it values speed but requires consensus on reversible calls teaches hesitation.
Fixing decision rights is not administrative cleanup. It is culture work through operating design.
