Decision Rights Matrix Template for a Leadership Team: A Copyable Version and How to Keep It Alive
Writing down who decides what is the step that turns a newly built leadership team into one that actually runs the business, and a decision rights matrix template does it on a single page by listing your recurring decisions and naming, for each one, who decides, who must be consulted, who is told, and where the limit sits beyond which it escalates. The template below is ready to copy, and the rest of this article covers how to fill it in with your team and how to stop it going stale.
Why a leadership team needs decision rights written down
A founder who has hired a delivery lead, a sales lead and a finance lead usually expects decisions to start flowing to those people on their own, and they rarely do, because nobody has said out loud which decisions have moved and which are still the founder's, so the safe choice for every new leader is to check first. The result is the pattern of founder-as-routing-layer, where the leadership team exists on the organisation chart but every hire, discount and scope change still passes across one desk, and the founder ends up busier than before the team was hired.
A matrix fixes this not by being clever but by being explicit, since it replaces dozens of unspoken assumptions with a short document that everyone has agreed to and can point to when a question comes up.
Rule of thumb: if two members of your leadership team would give different answers to the question "who signs this off?", that decision belongs in the matrix.
The decision rights matrix template
Copy the structure below into a shared document or spreadsheet, keeping the columns as they are and replacing the example rows with your own decisions. The example limits are illustrations of the kind of line you should draw, not recommendations, because the right threshold depends on your margin, your cash position and how much you trust the systems around each leader.
| Decision | Decides | Must consult | Informed | Limit before it escalates | Forum |
|---|---|---|---|---|---|
| Hire a role already in the approved headcount plan | Hiring manager | Finance lead | Leadership team | Salary above the agreed band | Weekly leadership meeting |
| Hire a role outside the headcount plan | CEO or founder | Finance lead, relevant leader | Leadership team | Always escalates | Weekly leadership meeting |
| Discount on a proposal | Sales lead | Delivery lead | Finance lead | Discount beyond an agreed percentage, or margin below floor | Pipeline review |
| Change of scope on a live project | Delivery lead | Account owner | Finance lead | Change that moves project margin below floor | Delivery review |
| Take on a new client outside your usual profile | Sales lead | Delivery lead | Founder | Any new service line or sector | Pipeline review |
| Resourcing people across projects | Delivery lead | Project leads | Sales lead | Conflict between two client commitments | Resourcing meeting |
| Non-budgeted spend on tools or suppliers | Budget holder | Finance lead | Leadership team | Above an agreed amount or a multi-year commitment | Monthly finance review |
| Annual budget and pricing policy | CEO or founder | Whole leadership team | Board or investors | Board approval where one exists | Quarterly planning |
Most firms of somewhere between 20 and 60 people end up with fifteen to thirty rows, and if yours runs to a hundred it has drifted into a process manual, which is a different and useful document but not this one.
How to fill in the matrix with your team
The version you write alone over a weekend will be tidy and largely ignored, because a matrix only works when the people named in it have argued about it, so the filling-in is as much the point as the finished page.
- List the decisions from evidence, not memory. Ask each leader to note, over a fortnight, every decision they waited on or escalated, which gives you the real list rather than the one you imagine.
- Fill in the founder's current reality first. Mark honestly where each decision is actually made today, because the gap between that column and the one you want is the work.
- Agree one decider per row. Consultation can involve several people, but a row with two deciders is a row with none, and it will quietly default back to the founder.
- Set limits in terms people can check. "Margin below the agreed floor" can be tested on a spreadsheet, whereas "significant risk" invites everyone to escalate just in case.
- Name the forum. Decisions that escalate need a place to land, which is why the matrix works best alongside a weekly leadership meeting agenda that has a standing slot for them.
Expect the hardest conversation to be about the founder's rows, since the founder is usually the person most reluctant to let go of pricing and hiring, and also the person whose time the matrix is meant to release.
How to keep a decision rights matrix alive
Matrices rarely fail on the day they are written, they fail three months later when a new leader joins, a threshold stops making sense, or the founder overrules a decision and nobody mentions that the document has just been made optional.
- Review it on a fixed cadence, quarterly suits most firms, and treat each review as a check on which rows were bypassed and why.
- Log overrides. When the founder steps in on a delegated decision, record it, because a pattern of overrides tells you either that the limit is wrong or that trust has not yet been built, and both are worth knowing.
- Update it when people change, since a matrix that names someone who left in the spring teaches the whole team that it is decorative.
- Keep it where decisions happen, linked from the meeting agenda and the onboarding pack rather than buried in a folder.
A decision rights matrix that is never consulted is not a governance document, it is a record of a good meeting.
Where Vitori fits
Plenty of leadership teams can fill in this template themselves and make it stick, particularly where the founder is genuinely ready to let go, and if that describes you the template above is enough. Where it tends to stall is when decision rights sit inside a wider set of problems, such as unclear roles, a leadership cadence that does not exist yet, or investors asking how the business runs without its founder, and at that point the matrix is one part of an operating model rather than a standalone fix.
Vitori designs operating models covering leadership structure, decision rights, governance and cadence, working inside your leadership team through its Operational Scale Framework and staying accountable until the change holds, whether that is with Vitori or anyone else. If that sounds like the problem you have, you can get in touch with Vitori to talk it through, and the aim is the same either way: a business that runs, and scales, without the founder in every decision.
Common questions about decision rights matrices
Is a decision rights matrix the same as a RACI chart?
A decision rights matrix borrows from RACI but serves a narrower purpose. A RACI chart usually maps responsibility for tasks and projects, whereas a decision rights matrix maps who has authority over recurring business decisions and where the limits sit before a decision escalates, which is why it adds thresholds and a named forum.
Should the founder appear in a decision rights matrix at all?
The founder should appear in a decision rights matrix, but on far fewer rows than they currently occupy in practice. Most founders sensibly keep strategy, the annual budget, senior hires and anything outside the agreed plan, while delegating day-to-day pricing, resourcing and in-plan hiring to the leaders they have appointed to own those areas.
How often should a leadership team update its decision rights matrix?
A leadership team should review its decision rights matrix quarterly and also whenever a leader joins or leaves. The quarterly review should look at which decisions were escalated, which were overridden and which limits no longer reflect the business, since a matrix that stays unchanged while the firm grows soon stops matching how decisions are really made.
