Decision Rights: Core Work

Why this matters

In most founder-led businesses, every decision routes through one person. The team is competent. The problem is that nobody knows what they are allowed to decide on their own, because the founder never made it explicit. So the team asks for permission on things that should not require it, and makes independent calls on things that absolutely should.

A purchase order for AED 2,000 (USD 545) waits three days for founder approval. Meanwhile, a team member promises a client a revised timeline without checking capacity. One decision is too controlled. The other is too loose. Both happen because decision authority was never defined.

This maps directly to the Power audit in the ARCAS diagnosis. If your score flagged escalation overload or authority gaps, start here. It also connects to risk leakage in the Five Levels model. When decisions concentrate in one person, every absence creates a risk event.

A founder you might recognise

Last year, the founder of a 28 person commercial cleaning services firm in Dubai was starting every morning with 15 to 20 WhatsApp messages from team leads asking for approval on things he thought they already had authority to handle. Should we send the team to the JLT site or the Marina site first? Can we order replacement supplies for the office contract? Should we give the client a one-week extension?

He answered each one. It took 45 minutes. None of these decisions required his expertise. They required his permission, because he had never clarified where his authority ended and theirs began.

Last month, while he was at a client meeting, a building manager called about an urgent maintenance issue. The team lead waited two hours for him to respond. The client escalated to management. The fix cost AED 800 (USD 218). The relationship damage was harder to measure.

The decision rights framework

Decision rights answers one question: who decides what, and at what level of independence? This is about making speed possible by removing ambiguity, not about creating bureaucracy.

Level 1: Decide and act

The person decides and acts without informing anyone. These are routine operational decisions within their role. The team lead schedules the maintenance crew. The account manager responds to a standard client query. The office coordinator orders supplies below a set threshold.

Most founders keep too many decisions above this level. If a decision is routine, low-risk, and reversible, it belongs here.

Level 2: Decide and inform

The person decides and acts, then informs the relevant people afterwards. These are decisions that affect other team members or have a moderate impact. The team lead reassigns a project member to handle a priority job. The account manager offers a small scope adjustment to keep a client satisfied. The finance coordinator approves an expense below AED 5,000 (USD 1,362).

The key word is "afterwards." The person does not wait for permission. They act and then share what they did.

Level 3: Recommend and wait

The person gathers the information, forms a recommendation, and brings it to the decision maker. These are decisions that are significant, hard to reverse, or set a precedent. Hiring a new team member. Changing a client contract. Approving a budget above the set threshold.

The person does the work. The founder (or manager) makes the call. The value is that the person frames the decision, not just dumps it.

Level 4: Escalate immediately

The person flags the issue to the founder or a senior manager without delay. These are decisions involving safety, legal risk, significant financial exposure, or client relationship threats. A workplace injury. A client threatening legal action. A compliance violation.

Very few decisions belong here. If your team escalates more than 3 to 5 issues per week to this level, most of them probably belong at Level 2 or 3.

Building your authority matrix

This exercise takes about 60 minutes the first time, but it saves hours every week afterwards.

Step 1: List the 20 most common decisions in your business.

Go through the last two weeks. What decisions were made? What decisions were waiting for you? What decisions were made without you that should not have been?

Common decisions in service businesses:

• Scheduling and resource allocation
• Client communication and follow-up
• Purchase approvals (supplies, tools, services)
• Scope adjustments on active projects
• Pricing and quoting for new work
• Hiring and firing
• Expense approvals at different thresholds
• Quality sign-off on deliverables
• Deadline extensions or changes
• Vendor and subcontractor selection

Step 2: Assign each decision to a level.

For each of the 20 decisions, ask:

• Is it routine and low-risk? Level 1.
• Does it affect others but is not high-stakes? Level 2.
• Is it significant enough to need a recommendation? Level 3.
• Could it cause serious harm if handled wrong? Level 4.

Most founders discover that 60% to 70% of the decisions currently reaching them belong at Level 1 or Level 2. That is your recoverable time.

Step 3: Assign an owner for each decision.

The owner is the person closest to the work. Not the most senior person. The person who has the most context about that specific decision.

Step 4: Set the thresholds.

For financial decisions, set clear numbers. Below AED 2,000 (USD 545): Level 1 (decide and act). AED 2,000 (USD 545) to AED 10,000 (USD 2,723): Level 2 (decide and inform). AED 10,000 (USD 2,723) to AED 50,000 (USD 13,620): Level 3 (recommend and wait). Above AED 50,000 (USD 13,620): Level 4 or founder decision.

Adjust these to your business. The exact numbers matter less than having them written down.

Step 5: Write it down and share it.

The authority matrix only works if people can see it. Put it in a shared document. Review it in a team meeting. The conversation about the matrix is almost as valuable as the matrix itself, because it surfaces assumptions that were never discussed. The first handoff tool includes a decision rule you can share with your team as a starting point.

Escalation vs delegation

These are different and founders confuse them constantly.

Delegation means giving someone the authority and the accountability to make a decision. You are not involved unless they ask for help.

Escalation means someone brings a decision to you because it exceeds their authority. You make the call.

The problem: when delegation is informal and escalation is the default, you end up making 50 decisions a day that other people could handle while the 3 decisions that actually need your judgment get buried.

The authority matrix fixes this. When someone knows their Level 1 and Level 2 decisions, they stop asking. When they know what requires Level 3 or Level 4, they stop guessing.

Common mistakes

1. Making the matrix and not sharing it. If the authority matrix lives in your head, it does not exist. Write it. Share it. Post it where people can reference it.

2. Overriding the matrix after publishing it. If you assign a decision to Level 1 and then second-guess the person who made it, you have destroyed the system. Either the decision belongs at Level 1 or it does not. If the outcome is wrong, coach on decision quality. Do not revoke the authority.

3. Setting thresholds too low. An AED 500 (USD 136) approval threshold means everything comes to you. Start higher than you are comfortable with. You can always lower it.

4. Forgetting to include yourself. Which decisions do you make alone? Which ones should you consult your team on? Which ones need outside input? Write your own decision rights alongside your team's.

When to move on

Move to the next chapter when you have created an authority matrix for at least the top 20 decisions, shared it with the people involved, and seen a visible reduction in the number of approvals reaching your desk. The team should be making Level 1 and Level 2 decisions without your involvement.

---

Where to focus by team size

• 10 to 19 people: Define 10 key decisions and assign levels. This alone will reduce your daily decision load by half.
• 20 to 34 people: Your team leads should own all Level 1 and Level 2 decisions. You should only see Level 3 and 4.
• 35 to 50 people: Department heads need their own authority matrices. The founder matrix is no longer enough.

---

Working prompts

People prompts

• Which decisions does your team make that should come to you? Which ones come to you that should not?
• If you were unavailable for a week, which decisions would stall?
• Who on your team has the judgment to make good calls but lacks the explicit authority?

System prompts

• Is there a written record of who decides what in your business?
• When the team escalates, do they bring a recommendation or just the problem?
• What is the financial threshold below which purchases should not require your approval?

AI prompts

• Which routine decisions (scheduling, routing, standard approvals) could eventually be handled by automated rules?
• Where would a decision support dashboard reduce escalations?
• What data does the team currently lack that forces them to escalate instead of deciding?

---

Founder exercise

Set aside 60 minutes. Do this with one or two of your most operationally senior team members.

Part A: Decision audit (20 minutes)

1. List every decision that came to you in the last two weeks. Include WhatsApp messages, emails, meetings, and verbal requests.
2. For each one, write whether you needed to be involved or whether someone else could have handled it.
3. Count the total. Count the ones that did not need you. That percentage is your current decision load waste.

Part B: The authority matrix (25 minutes)

1. Take the 20 most common decisions from your list.
2. Assign each one a level: decide and act, decide and inform, recommend and wait, or escalate immediately.
3. Assign an owner for each decision.
4. Set financial thresholds.
5. Write this into a one-page document.

Part C: The handoff (15 minutes)

1. Share the authority matrix with the relevant team members.
2. Ask: does this match how you think decisions should work? What is missing?
3. Agree on a two-week trial. At the end, review what worked and what needs adjusting.

---

ARCAS lens

Decision Rights bridges delegation (Chapter 2) and the team structure work in Part 3. You cannot build a team that operates without you if they do not know what they are allowed to decide.

This also connects to Part 4. When decision rights are clear, processes can be documented with decision points built in. When they are unclear, every process routes back to the founder as the default decision maker.

People build clarity. Systems make it repeatable. AI can support decisions with data. But first, someone has to say: this is who decides what, and here is how much authority they have.

---

Start now: Quick self-assessment

Rate each statement from 1 (never true) to 5 (always true):

Score 24 or above: Your decision rights are clear. Move to the next chapter. Score 15 to 23: There are gaps worth closing. Work through the authority matrix exercise. Score below 15: Decision overload is one of the biggest drains on your time and your team's speed. Do the full exercise before moving on.