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
A record of who has authority over each decision, the required input and any approval limits.
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. Start with the recurring decisions whose authority is unclear. Ten to thirty rows can be a practical first draft, not a universal limit. Record discretion thresholds so routine work does not need unnecessary escalation.
- Names the deciders. For an operating decision, name the person or role authorized to close it. Where a board or committee decides, name that body and its applicable decision rule. Do not replace required collective authority with an invented individual decider.
- 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 maps responsibility and accountability for work. The four-role version used here focuses on deciding authority, consultation, information and vetoes. They can be used together; neither removes the need to explain what each role can do.
- 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 repeated situations
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 owner 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:
- Decision authority is already clear and the document would add no useful information. Headcount alone is not the test.
- The matrix would be performance, not structural change.
- Decisions are closing fast and the pattern is healthy.
Method and limits
The four-role version on this page is a working model, not the only decision-rights framework. Bain's RAPID framework separates Recommend, Agree, Perform, Input and Decide, and allows the deciding role to belong to a person or a group. Choose a model that makes your real authority usable; the matrix records that authority rather than creating it.
Common questions
- How long should a decision rights matrix be?
- Keep it readable enough for the people using it. A short first version can cover the decisions causing delay; there is no universal two-page or thirty-row limit. Larger organizations can separate related decisions by function while preserving shared approval rules.
- Where should the matrix live?
- Keep the current version where decision-makers can access it, such as the operating manual or company wiki. Link it to the agreements and policies that actually grant authority.
- How often should the matrix be updated?
- Review it on a cadence appropriate to the business, and update it when authority, roles or governance change. A quarterly review is one practical starting point.
- Who should sign off on the matrix?
- Have the people who actually hold the relevant authority approve that part of the matrix. Operational delegation and board-reserved decisions may follow different approval processes.
- When should an owner use Business Owner Coaching?
- When the matrix exposes a live business problem and you still do not know the next business move. Bring the repeat decisions, the current approval path, and the places where work keeps coming back to the owner.