Practice : Decision Rights Mapping
Purpose and Strategic Importance
Decision Rights Mapping is the practice of making explicit who has authority to make specific categories of decisions — removing the ambiguity that causes decisions to stall, escalate unnecessarily, or be made by the wrong person. When decision rights are unclear, organisations default to the safest behaviour: waiting for someone more senior to decide. This creates delays, bottlenecks, and a culture of dependency.
Clear decision rights do not remove leadership judgment — they establish the framework within which judgment is exercised. By mapping who can decide what, leaders unlock the speed and confidence that autonomous teams need to operate effectively.
Description of the Practice
- Decision categories are mapped to authority levels: who can decide alone, who needs to consult, who needs to inform, who approves.
- DACI (Driver, Approver, Contributor, Informed) or equivalent frameworks are used to make roles explicit.
- Decision rights are documented and shared — not held informally in the leader's head.
- When decision rights are unclear, they are clarified through explicit conversation, not assumption.
- Decision rights are reviewed when team structure, strategy, or risk profile changes.
How to Practise It (Playbook)
1. Getting Started
- Map your team's most common decision types: operational, investment, people, product, architecture.
- For each type, ask: "Who currently decides this? Who should decide this? What level of consultation is appropriate?"
- Identify where decisions are stalling or escalating unnecessarily — these are likely rights that are unclear or misaligned.
- Document the rights and share them with the team: "Here is how we make decisions — here is your authority."
2. Scaling and Maturing
- Review decision rights after major organisational changes — structure, strategy, or team composition changes typically invalidate existing rights mapping.
- Use retrospectives to surface decisions that took too long or created confusion — these often indicate rights that need clarification.
- Extend the rights mapping across team boundaries where frequent cross-team decisions create delay.
- Coach leaders and teams on the difference between consulting (seeking input before deciding) and approving (holding veto power).
3. Team Behaviours to Encourage
- Teams make decisions at the lowest appropriate level without seeking unnecessary approval.
- When decisions require escalation, individuals know clearly when and why to escalate.
- Leaders are consulted rather than required to approve in cases where the team has the necessary context.
- Decision-making becomes faster because the rights are clear and trusted.
4. Watch Out For…
- Rights mapping that exists on paper but is overridden in practice by leaders who reassert control.
- Over-narrow decision rights that recreate a bottleneck by requiring approval for routine choices.
- Confusion between "I was informed" and "I consented" — clarity on the difference prevents later disputes.
- Rights that are never updated, becoming obsolete as the organisation evolves.
5. Signals of Success
- Decisions happen faster because authority is clear and trusted.
- Leaders spend less time approving decisions that the team is capable of making.
- Escalations decrease in volume and improve in quality — teams escalate the right things.
- Teams feel empowered and accountable, not constrained by ambiguous authority.
- Decision-making is perceived as fair and consistent rather than arbitrary.