Question
What does it mean that decision rights design?
Quick Answer
Clarifying who can make which decisions restructures organizational behavior. Decision rights — the formal and informal authority to commit the organization to a course of action — are the most consequential element of organizational design. When decision rights are clear, decisions are made.
Clarifying who can make which decisions restructures organizational behavior. Decision rights — the formal and informal authority to commit the organization to a course of action — are the most consequential element of organizational design. When decision rights are clear, decisions are made quickly by the people best positioned to make them. When decision rights are ambiguous, decisions are delayed by confusion, escalated by uncertainty, and duplicated by multiple people who each believe they have the authority (or obligation) to decide. Redesigning decision rights — clarifying who decides what, and moving decisions closer to the relevant information — is one of the highest-leverage systemic interventions available.
Example: A media company, Vantage, experienced chronic decision delays. Feature prioritization decisions took three to four weeks because they escalated through four levels of management. Hiring decisions took six to eight weeks because every hire above entry level required VP approval. Budget allocations took two to three months because they required quarterly committee review regardless of size. A decision rights audit revealed the root cause: the company had never formally defined decision authority — every significant decision was escalated to the highest level of management because no one at lower levels knew whether they had the authority to decide. The CEO assumed the VPs were making operational decisions. The VPs assumed the CEO wanted to approve everything. Directors assumed VPs would override their decisions. Managers assumed they needed approval for anything beyond the routine. The decision rights redesign created a simple framework: decisions below a dollar threshold were made by the team lead, decisions below a higher threshold were made by the director, and only decisions above that threshold or involving cross-functional commitments required VP approval. Hiring decisions were delegated to hiring managers with HR advisory support. Feature prioritization was delegated to product teams with quarterly strategic alignment reviews. Decision cycle times dropped by 60% — not because people worked faster but because decisions were no longer traveling through unnecessary approval chains.
Try this: Audit the decision rights for your team or function. List the ten most common decisions your team makes. For each decision, identify: (1) Who currently makes this decision? (2) Who should make this decision? (the person closest to the relevant information and most affected by the outcome). (3) What approval is currently required? (4) What approval is actually necessary? (5) How long does the decision currently take from initiation to resolution? For each decision where the current decision-maker is not the optimal decision-maker, or where unnecessary approvals add delay, design a revised decision right that moves the decision closer to the information and reduces unnecessary approval layers. Implement one revision this week.
Learn more in these lessons