What are decision rights?
Decision rights are agreed rules allocating authority for a defined choice. They state who decides, recommends, agrees, contributes evidence, implements and escalates.
A sales manager may approve discounts up to 10% when margin and contract conditions are met. Larger discounts move to a commercial director. Finance provides data but does not own the customer choice.
Bain describes these tools as a way to organize decisions and execution through clear roles and accountabilities.1 Authority must attach to a specific choice; “the manager owns pricing” is too broad.
Why do decision rights matter?
Organizations lose time when several people believe they can decide, or nobody does. Clear authority makes delegation safer, reduces escalation and lets employees act near customers while leaders retain material risk control.
- Speed: fewer approval loops and repeated meetings
- Accountability: one visible owner for the final choice
- Quality: relevant evidence reaches the decider
- Execution: responsibility continues after the choice
- Control: authority stays inside agreed financial and risk limits
McKinsey reports that explicit authority and accountability support decentralized, transparent and customer-focused decisions.2 These rules separate people with a voice from the final decider.
Which decision roles should be defined?
Define only necessary roles. Most choices require one decider, a recommendation, focused input and an implementation owner. Regulated, contractual or high-risk choices may require formal control agreement.
| Role | Authority or duty | Key question |
|---|---|---|
| Decide | Makes the final choice | Who has the final call? |
| Recommend | Builds the case and proposes an option | Who does the analysis? |
| Agree | Provides required approval in a defined area | Whose formal agreement is necessary? |
| Input | Provides facts, expertise or affected views | Whose evidence improves the choice? |
| Perform | Implements the decision | Who turns the choice into action? |
Bain’s RAPID framework uses recommend, agree, perform, input and decide for complex choices.3 Use it selectively. Routine work rarely needs five roles, and too many agreements recreate delay.
How do you define decision rights in 7 steps?
Start with choices creating the most value, risk or delay. Define the question, assign one owner, select contributors, set limits, write escalation rules and test real cases before expanding.
- Inventory decisions. List choices affecting strategy, customers, cash, people and risk.
- Write the decision question. Define the exact choice, scope and required deadline.
- Name one decider. Match authority with evidence and accountability.
- Select contributors. Include necessary expertise, evidence, controls and implementers.
- Set limits. Define financial, contractual, regulatory, privacy and customer-impact thresholds.
- Define escalation. State which condition moves the choice upward and who then decides.
- Test and review. Run real examples, record delays or conflicts and adjust the design.
BDC recommends delegation so owners can focus on strategy and long-term planning.4 Defined authority specifies what employees decide and which exceptions require the owner.
How do decision rights differ from roles and responsibilities?
A role is a position, while responsibilities describe its work. Decision authority defines which choices the role may make. Someone can perform work, advise or own an outcome without the final vote on every related choice.
A procurement manager may evaluate suppliers but require an operations decision on technical suitability and finance agreement above a spending threshold. Document roles and responsibilities, then map high-value choices.
“Delegation fails when leaders transfer the task but keep every decision. People need a clear result, defined authority and known limits. Otherwise, the work moves down while the bottleneck stays at the top.”
What mistakes should leaders avoid?
Common errors include several final deciders, responsibility without authority, too many contributors, authority without limits and poorly communicated changes. Mapping every small choice also creates administration instead of clarity.
- Do not confuse consultation with approval.
- Do not give several people the final vote.
- Do not require executive approval for routine work.
- Do not delegate regulated or material risks without controls.
- Do not leave implementation ownership undefined.
McKinsey cautions that RACI can blur authority when participants debate labels or assume accountability means the final vote.5 Write “who decides” plainly and connect authority to faster decision-making processes.
How should the effectiveness of decision rights be measured?
Measure whether choices move faster, stay within limits and produce the intended result. If reversals, losses or compliance issues rise, improve evidence or guardrails rather than adding approval layers.
- Time from question to final decision
- Number of approval levels and escalations
- Percentage of decisions reopened without new facts
- Implementation completed by the agreed date
- Outcome compared with the recorded assumptions
Review delegated choices after 30 to 90 days. Check maps annually or after major business changes. Keep them easy for affected employees to find.
What does this look like in a Canadian SME?
Consider an Ontario supplier where branch managers wait for head office to resolve customer credits. Managers may approve within a dollar limit when evidence is complete. Larger claims move to the operations director.
Finance supplies account data, sales provides context and quality investigates concerns. One branch manager decides within limits. Monthly reviews track credit value, resolution time, repeat claims and retention.
What should executives do first?
Select ten choices that often wait, escalate or reopen. Record the decider, input, authority limit, escalation trigger and implementation owner. Test for one month and remove steps adding delay without value.
When several business units repeat the same support work, leaders can assess how shared services improve efficiency without weakening local accountability.
Praevion Consulting Inc helps Canadian organizations connect decision rights, structure, governance and performance. If unclear authority is slowing execution, contact Praevion Consulting Inc for a focused operating-model discussion.
Frequently asked questions
These answers address authority, accountability, delegation and review. They help executives introduce clarity without creating another process layer.
Can two people share final decision authority?
Usually no. Shared final authority makes conflict harder to resolve. One person should decide after required contributors provide evidence and any formal control approvals are complete.
Are decision rights the same as an approval matrix?
No. An approval matrix mainly shows financial or procedural approval limits. A decision map also identifies who recommends, provides input, decides, implements and escalates a business choice.
Should decision authority sit at the lowest level?
It should sit at the lowest qualified level with access to the necessary information and ability to own the result. Material enterprise risks and legal duties may require higher authority.
How often should decision rights be reviewed?
Review them annually and after major changes in strategy, structure, leadership, technology or regulation. Review sooner when decisions repeatedly wait, escalate or conflict.
References
This guide draws on Canadian delegation advice, organizational research, governance standards and established decision-role frameworks. The sources below support the definitions, design steps and controls used in the article.
- Bain & Company, “Decision Rights Tools.”
- McKinsey & Company, “Untangling your organization’s decision making.”
- Bain & Company, “RAPID Decision Making Framework.”
- Business Development Bank of Canada, “How to delegate effectively.”
- McKinsey & Company, “The limits of RACI and a better way to make decisions.”
- International Organization for Standardization, “ISO 37000 Governance of organizations.”
