Ask two teams what they own and you'll usually get answers that overlap. Ask who has final say on a specific class of decisions and you'll usually get answers that conflict.
That is where a lot of organizational noise comes from: duplicated effort, stalled initiatives, passive resistance, and arguments mislabeled as personality problems. Most of the time, people are not fighting about the idea. They are fighting about who has the authority to choose.
Until decision rights are explicit, you're managing symptoms.
The Three Modalities
Every participant needs one of three roles:
Final say. The person who commits resources, signs off, or moves the initiative. They own the call and the consequences.
Input. The people whose information is required before the call. They do not control the outcome, but the owner must hear them.
Veto. The person or function that can stop the decision because the risk is outside the owner's mandate.
Veto rights should be rare, explicit, and scoped. Legal, security, privacy, compliance, and finance sometimes need veto power. But a healthy veto has boundaries: what risk it covers, what evidence is required, how long the veto holder has to respond, and where escalation goes if the business and control function disagree.
A veto without scope becomes empire-building. A veto without an SLA becomes a queue. A veto without escalation becomes a hidden final-say right.
A Lightweight Operating Pattern
Do not build a giant decision registry unless you enjoy maintaining abandoned spreadsheets.
Use a lightweight decision card for recurring, high-friction decisions. Name it in plain language: Launch readiness, Pricing exceptions, Roadmap tradeoffs, Enterprise escalation, Headcount approval.
Each card should fit on one page:
- Decision type
- Final say
- Required input
- Veto scope, if any
- SLA for input and veto
- Escalation path
- Review date
The point is not documentation. The point is reducing decision latency, escalation frequency, and performative alignment meetings.
How to Map Your Decision Rights
Start with your ten most frequent cross-functional stalls. For each one, ask:
- What is the actual decision being made or avoided?
- Who thinks they have final say?
- Who actually has final say in practice?
- Who provides required input?
- Who has explicit veto power?
- What is the SLA?
- Where does escalation go?
You'll often find accountability without authority, authority without accountability, or veto power pretending to be input. That mismatch is where the conflict lives.
