Canonical definition
What is a decision rights matrix?
A decision rights matrix names who can decide, who must be heard, who must be informed, and who can stop the call.
Use the matrix when pricing exceptions, hiring approvals, discounts, customer escalations, or budget calls keep coming back to the owner after they were supposedly delegated.
In one sentence
One page that names who carries each consequential decision in the company.
What this means for the owner
If the same decision keeps returning to you, the issue may not be trust or work ethic. It may be that nobody can see who owns the call. Check repeat decisions first: pricing, hiring, discounts, budget exceptions, customer escalations, and board approvals.
Do not buy another workflow tool or add another approval meeting until the deciding right is named.
What it actually does
The matrix is a single document that does four things:
- Names the decisions. Lists the ten to thirty decisions that actually matter in the company. Operational decisions below a discretion threshold are not listed.
- Names the deciders. One name per decision. The decider closes the call.
- Names the consult and inform roles. People whose input is mandatory before the call, and people who must be told once the call is made.
- Names the veto holders. Often the board, a co-founder, or a regulatory function. The decisions on which veto applies are listed explicitly.
What it is not
- Not RACI. RACI splits responsibility from accountability and confuses teams. The four-role matrix isolates the deciding question.
- Not a process diagram. It describes who decides, not how the decision is made. Process diagrams are downstream of the matrix.
- Not an org chart. The org chart shows manager lines. The matrix shows deciding lines.
- Not a one-time document. The matrix updates when authority transfers, roles change, or governance shifts.
- Not exhaustive. Decisions below the discretion threshold of each role are not in the matrix. Only consequential decisions are listed.
Three common patterns
Pattern 1
The pricing decision that needed a deciding column.
Pricing seems to belong to the head of sales. The matrix shows that pricing also touches margin, delivery cost, and founder exception authority. The first check is who owns the final call.
Pattern 2
The hire that the board could veto.
A senior hire looks like an operating decision until the agreement gives the board veto rights. The first check is whether the person making the offer also has the authority to complete it.
Pattern 3
The exception that became a manager call.
A discount request keeps escalating because nobody knows the threshold. The matrix names which exceptions a manager can close and which ones still belong with the owner.
When to use it
Build a decision rights matrix when:
- The same decisions are being re-litigated in different meetings.
- Senior hires are failing because their rights are unclear.
- Investors have joined and the historical structure no longer fits.
- Cross-functional decisions are stalling.
- A capital event or governance change is imminent.
Skip the matrix when:
- The team is below ten people and authority is naturally clear.
- The matrix would be performance, not structural change.
- Decisions are closing fast and the pattern is healthy.
Common questions
- How long should a decision rights matrix be?
- One page if possible, two at most. Ten to thirty rows. Each row a consequential decision. If it gets longer, the threshold for inclusion was too low.
- Where should the matrix live?
- In the governance binder, the operating manual, or the company wiki. Readable in five minutes by a new exec hire.
- How often should the matrix be updated?
- Quarterly review. Immediate update at any authority transfer, role change, or governance shift.
- Who should sign off on the matrix?
- The principals (founders, owners) and the board. The exec team executes against it; the principals own it.
- When should an owner bring this into Business Problem Review?
- When the matrix exposes a live business problem and you still do not know what to fix first. Bring the repeat decisions, the current approval path, and the places where work keeps coming back to the owner.