Authority · Vocabulary
What Are Decision Rights?
Every organization allocates decision rights, whether it means to or not. When the allocation is implicit, authority defaults to rank - and the people with the knowledge wait for permission.
Definition
Decision rights are the explicit allocation of who decides, who must be consulted, who executes, and who is informed, for a given class of decisions - the organizational answer to "whose call is this?", written down before the decision arrives rather than negotiated while it waits.
Decision rights exist whether or not anyone designed them. Every decision an organization makes is made by someone, under some understanding of who was entitled to make it; the only question is whether that understanding was chosen in advance or improvised under pressure. Improvised rights resolve to rank, precedent, and persistence, and they announce themselves in symptoms: decisions that stall while their owner is discovered, approval chains no one can reconstruct, and calls that are made, unmade, and remade as each newly surfaced stakeholder weighs in.
The vocabulary comes from decision science and from management practice. Rogers and Blenko's Harvard Business Review article "Who Has the D?" argued what its subtitle states: clear decision roles enhance organizational performance. Herbert Simon's Administrative Behavior located the deeper reason decades earlier, treating the organization as, at bottom, a structure for making decisions - and a decision is made well where knowledge and authority meet. Decision rights are the instrument that either honors that principle or violates it. Most organizations violate it by default rather than by choice, because rights that are never allocated pool at the top. Whether the labels come from a RACI chart or from the organization's own vocabulary matters far less than the fact of explicitness: four roles, named in advance, per class of decisions.
The Four Roles
Who decides
One named role owns the call. Not a committee, not "leadership", not whoever feels most strongly: a single decider whose yes or no ends the deliberation. When the decider is a group, the right has not been allocated, it has been dissolved - and the class of decisions will be settled by stamina rather than judgment.
Who must be consulted
The people whose input is owed before the call, named in advance. Consultation is a right to be heard, not a right to veto: the decider must seek the input and may overrule it. Leaving this role implicit produces two familiar failures - decisions that blindside the person who held the missing fact, and "alignment" rounds that expand until everyone with an opinion has been treated as an approver.
Who executes
The people who carry the decision out. Naming them at allocation time forces the question of whether the decision is executable at all, and it separates commitment from agreement: executors are entitled to have been consulted where their knowledge was relevant, and are expected to execute a call they argued against once it is made.
Who is informed
The people told after the decision, deliberately, rather than left to discover it. The informed list is what keeps the consulted list honest: most of the people added to approval chains "for visibility" belong here. Moving them from the approval path to the notification path is often the largest single recovery of decision speed available to an organization.
The Core Failure: Rights Held Where the Knowledge Is Not
Nearly every allocation failure reduces to one pattern: the right to decide is held at a distance from the knowledge the decision requires. The person who has spent months inside the problem prepares a recommendation; the person who has spent an hour with the summary makes the call. The organization pays twice. Senior attention is consumed re-deriving context that already existed below, and the decision itself is made on compressed information, stripped of exactly the detail that made it hard. The Knowledge-Authority Gap examines this separation in depth: how it forms, why it persists, and what it costs.
The repair is not pushing every decision down, and it is not heroic delegation. It is matching: authority placed at the level where the relevant knowledge actually lives, with constraints, budgets, and guardrails sent down instead of decisions sent up. Match Authority to Responsibility works through what that looks like in practice, including the cases where the knowledge genuinely does sit at the top. In the Four A's of Organizational Readiness™, this is the heart of the Authority dimension: not how much authority an organization has, but whether it sits where the knowledge is.
The failure now has a modern variant. When an AI model produces the recommendation and a human clicks approve, the formal decision right sits with the approver while the substance of the decision has migrated to the model - and a signature is not a decision. Decision Rights When the Model Recommends takes up that case directly: what the human must genuinely be deciding for the right to remain real.
The Escalation Test
Take the most recent decision that escalated to you and name what you added to it beyond consent. If the analysis was complete before it reached you, the options were framed below you, and your contribution was a yes, then for that class of decisions the right sits with you but the knowledge does not. Every recurring escalation in your organization is this test running in production - and its result is written in your calendar.
How to Allocate Decision Rights
Allocate by class, not by decision
Rights attach to recurring classes of decisions: pricing exceptions, hiring against an approved plan, vendor selection, scope changes. Allocating one decision at a time means renegotiating authority every time a decision arrives, which is exactly the tax explicit rights exist to remove.
Give every class exactly one decider
Someone has to hold the D. Shared ownership is unallocated ownership: when two people can each plausibly claim the call, the decision waits while they discover which of them will make it, and the discovery process is escalation.
Put the right where the knowledge is
Ask, for each class, where the relevant detail actually lives, and place the decision there. Send constraints down, not decisions up: a budget, a risk boundary, a definition of done all travel well; a decision compressed into a summary does not.
Audit escalations, not org charts
The org chart shows where authority is supposed to sit; the escalation pattern shows where it actually operates. Each class of decisions that repeatedly travels upward is either unallocated or allocated above its knowledge, and the pattern tells you which classes to fix first.
Research basis: Rogers, P. & Blenko, M. (2006). Who Has the D? How Clear Decision Roles Enhance Organizational Performance. Harvard Business Review, 84(1), 52-61. Simon, H.A. (1947). Administrative Behavior. Macmillan.
Frequently Asked Questions
What are decision rights?
The explicit allocation, for a given class of decisions, of who decides, who must be consulted, who executes, and who is informed - written down before the decision arrives rather than negotiated while it waits.
Why do decision rights matter?
Unclear rights turn every significant decision into two pieces of work: the decision itself and a negotiation about whose call it is. Clear decision roles remove the second piece, which is why they are so closely tied to decision speed and clean ownership of outcomes.
What is the most common decision rights failure?
Rights held where the knowledge is not: the person with the detail prepares a recommendation while a person working from a summary holds the call. The modern variant is AI-assisted work, where a model recommends and a human approves without genuinely deciding.
How do you clarify decision rights?
Name the recurring decision classes that matter; give each class exactly one decider plus consulted, executing, and informed roles; place the right at the level where the knowledge lives; and audit recurring escalations to find the classes still unallocated.
Diagnose Your Authority Condition
Whose call is it in your organization?
The Executive Diagnostic assesses the Authority dimension - including decision rights clarity, escalation load, and whether authority sits where the knowledge is.