Decision Rights Matrix

Purpose

The Decision Rights Matrix eliminates ambiguity about who makes which decisions. Using a RACI-style framework (Responsible, Accountable, Consulted, Informed), the team maps key decisions to roles, reducing bottlenecks, duplication, and frustration.

At a glance

How to run

1. List key decisions (10 min): Brainstorm the team’s most important recurring decisions (e.g., hiring, architecture choices, sprint priorities, budget allocation). Aim for 10–15.
2. Define the framework (5 min): Explain RACI (or a simpler variant like Decide / Advise / Inform). Clarify: only one person can be Accountable for each decision.
3. Map the matrix (25 min): For each decision, the group discusses and assigns roles. Use a large grid: rows = decisions, columns = roles/people. Work through one row at a time. Where there is disagreement, facilitate until consensus.
4. Identify conflicts and gaps (10 min): Review the completed matrix: Are any roles overloaded with accountability? Are there decisions with no clear accountable? Are there "consultation bottlenecks" (one person consulted on everything)?
5. Agree and publish (5 min): Finalise the matrix and commit to posting it visibly. Schedule a review in 3 months.
6. Close (5 min): Each person names one decision that is now clearer.

Materials needed

• Large matrix grid (flipchart, whiteboard, or spreadsheet)
• Sticky notes or markers
• Pre-prepared list of candidate decisions (optional)
• Timer

Pitfalls & common mistakes

• Too granular: Map strategic and recurring decisions, not every micro-choice. 10–15 is enough.
• Multiple accountables: If two people are accountable, nobody is. Enforce single accountability.
• Skipping the conversation: The value is in the discussion, not just the output. Disagreement is a feature.
• Never updating: As the team evolves, so should the matrix. Review quarterly.

Inclusion & accessibility

• Ensure all roles are represented in the room, not just leadership.
• Allow written input before the live session for people who need preparation time.
• In remote settings, use a collaborative spreadsheet for real-time mapping.
• Be mindful that power dynamics can skew the conversation — facilitate equitably.

Variations

• DACI variant: Use Driver, Approver, Contributor, Informed for a slightly different framing.
• Delegation Levels Game: Combine with the Delegation Levels Game from agile leadership practices for a gamified approach.
• Cross-team version: Map decisions that span team boundaries to reduce inter-team confusion.

When NOT to use this

• When the team is too small (2–3 people) and a simple conversation suffices.
• When the organisation is undergoing a reorg and roles are in flux.
• When it is used to centralise control rather than distribute it.

Source & further reading

• RACI Matrix (project management standard)
• Jurgen Appelo, *Management 3.0* (Addison-Wesley, 2011) — delegation matrices
• Patrick Lencioni, *The Advantage* (Jossey-Bass, 2012)