The reality

A 25 person team should not need the founder to approve a AED 4,000 (USD 1,090) software renewal. It does, because nobody ever wrote down who decides what. So every decision routes to the founder by default, the founder becomes the bottleneck by accident, and the team learns the safest move is to ask. Speed in a service business comes from how clearly decision rights are mapped before the decision arrives, not from working harder. Most UAE founders have never drawn that map.

Read this if

The team asks the founder to approve decisions worth less than a senior team member's daily rate
A decision that should take two days takes two weeks because it sat in someone's inbox waiting for permission
The founder says yes to nearly every recommendation that crosses their desk
A new hire learns the boundaries of their authority by guessing, getting it wrong, and being corrected
Two team members make conflicting decisions on the same workflow because nobody owns it formally
The founder cannot point to a written decision rights map for the business

What dysfunction costs

Quality cost. Decisions made by the founder under pressure (during a client call, between two meetings) are worse than decisions made by the team member closest to the work, with the time to think. The founder's bottleneck position guarantees suboptimal quality on the marginal decision.

What success looks like

When decision rights are mapped:

Every recurring decision in the business has a named owner with the authority to act
The founder's signature is required only on decisions where the founder's judgment genuinely changes the outcome
A new hire receives a one-page decision rights map in their first week
A team member can name the threshold above which a decision escalates and below which they act
When two people disagree on who owns a call, the map answers the question instead of the louder voice
The founder spends time on the decisions where their input changes the outcome and stops rubber-stamping decisions the team made well

The framework

Decision rights run as four layers. Each layer answers a different question about who decides what.

Layer 1: Categories of decision

Every decision in a service business falls into one of four categories. Each category has a different appetite for delegation.

Strategic decisions. Business model, major pricing changes, key partnerships, equity decisions. The founder owns these. They are rare.
Financial decisions. Spend approvals, hires, contract terms. These are sortable by dirhams: small spend goes to the team, large spend goes to the founder, with a defined threshold in writing.
Operational decisions. Day-to-day choices about how the work runs. These should sit with the team that runs the work, with the founder informed at a regular checkpoint.
People decisions. Performance issues, promotions, terminations, hiring above a level. These are typically shared between the founder and a team lead, with the rule written down.

The behaviour to adopt this week: list five recent decisions in the business. Sort each one into a category. Notice which category accumulates the most founder time.

Layer 2: Thresholds

Every category needs a threshold that says when a team member decides and when the founder decides. Without the threshold, every decision escalates by default.

For financial decisions: a dirham value. For operational decisions: a category (this kind of change is the team's, that kind requires founder approval). For people decisions: a level (manager-level hires are team leads, senior leadership hires are founder).

The behaviour to adopt this week: write the threshold for one financial decision category. Software spend, supplier contracts, or expense reports. Below the threshold the team acts. Above it, the founder approves. Communicate it.

Layer 3: Owners

Every recurring decision has a named owner. Not "the team." Not "the operations function." A specific person. If the owner leaves, the decision is reassigned within 48 hours.

The behaviour to adopt this week: pick the three highest-volume decision categories in the business. Name the owner for each, in writing, with the threshold attached.

Layer 4: The review cadence

A decision rights map decays. Thresholds stop matching the business as it grows. Owners change. The map needs a quarterly review where the founder and the senior team review the past quarter's decisions and ask three questions: which decisions came to the founder that should not have? Which decisions were made by the team that should have escalated? Where did ambiguity slow the work down?

The behaviour to adopt this week: schedule the first quarterly decision rights review. 60 minutes. Add it as a recurring entry in the calendar.

A founder you might recognise

A founder runs a 30 person fitout business in Dubai. AED 9M (USD 2.4M) last year. In Q1 2026 the founder noticed that the senior project managers were asking permission on variation orders the founder approved without question 95 percent of the time. The founder asked the operations lead to map every recurring decision in the business onto a single page over the next two weeks.

The page came back with 47 decisions. 12 were strategic and stayed with the founder. 18 were financial, mostly tied to thresholds: under AED 10,000 (USD 2,720) the senior PM acted, between AED 10,000 and AED 50,000 (USD 2,720 to USD 13,615) the operations lead approved, above AED 50,000 (USD 13,615) the founder approved. 11 were operational, all reassigned to the team lead closest to the work. 6 were people decisions, jointly held between the founder and the team lead.

The map went up on the operations lead's wall and into the team's onboarding folder. Three months later the founder counted decisions touched: 38 in the quarter, down from roughly 220 the previous quarter. The team had not slowed down. They had simply stopped asking permission for things that were already theirs to decide.

Working through it

List 20 recurring decisions in the business. Pull them from the last month: vendor selections, hires, expense approvals, contract changes, scope decisions, scheduling conflicts.
Sort each decision into a category. Strategic, financial, operational, or people. The category decides the appetite for delegation.
Set thresholds. For financial decisions, write the dirham figures. For operational and people decisions, write the categories or levels.
Name owners. One person per recurring decision. Not a team. Not a function. A name. If the owner leaves, the decision is reassigned within 48 hours.
Schedule the quarterly review. 60 minutes on the calendar, recurring. The review tunes the map as the business grows.

Common mistakes

Skipping the threshold step. Categories without thresholds default to founder approval. The threshold is what makes the map operational.
Naming a function instead of a person. "The operations team owns this" produces ambiguity inside the team. "Sara owns this" produces clarity.
Building the map and not communicating it. A decision rights map that lives in the founder's head changes nothing. Print it. Walk through it with the team. Put it in the onboarding folder.
Treating the map as static. The business at 20 people needs different thresholds from the business at 40. The quarterly review is what keeps the map matched to the business.
Re-approving decisions the team owns. When a Rung 4 (recommend and proceed) decision arrives in the founder's inbox, the founder's job is to redirect. Approving teaches the team that the rung was theatre.

Self-assessment

Y or N for each.

Does the business have a written decision rights map covering at least 20 recurring decisions?
Are thresholds (dirham values, levels, or categories) defined for every category of decision?
Does every recurring decision have a single named owner with a 48 hour reassignment rule?
Has the team had a briefing on the map in the last 90 days?
Does a new hire receive the map in their first week?
Is there a quarterly review of the map on the calendar?
Has the founder reduced the number of decisions they touch each quarter compared to a year ago?

Five or more "yes" answers means decisions move at the speed of the team. Three or four is the band where the map exists in part but the team is still defaulting to escalation. Two or fewer means the next 90 days belong to drawing the map and teaching the team to use it.

Decision Rights