The Delegation Ladder: Core Work

Why this matters

Most founders think delegation is a binary: either you do it yourself or you hand it off completely. That is why it fails. You delegate something, the result is not what you expected, and you take it back. After a few rounds of this, you stop trying. Your team learns that "delegated" really means "I will do it when the founder takes it back."

In the UAE and wider GCC, this problem runs deeper. Many founders built their business on personal relationships. The client knows you. The supplier trusts you. Your team joined because of you. Stepping back feels like putting those relationships at risk. So you stay in the middle of everything, and the business stays stuck at whatever size one person can carry.

The cost is real. If your time is worth AED 400 (USD 109) per hour and you spend 15 hours a week on tasks a team member at AED 100 (USD 27) per hour could handle, that is AED 4,500 (USD 1,225) per week in misallocated founder time. Over a year, that is AED 234,000 (USD 63,700) in lost capacity that could have gone toward growth.

The Delegation Ladder gives you five distinct levels between "I do everything" and "they own it completely." It turns delegation from a leap of faith into a structured climb. This maps to the Power audit in the ARCAS diagnosis and the people layer of the Five Levels model. When the founder is the bottleneck, every function leaks.

A founder you might recognise

Last year, the founder of a 22 person recruitment agency in Dubai tried delegating client proposals to her senior consultant. The first proposal came back with pricing errors and a tone that did not match the brand. She rewrote it from scratch and never delegated proposals again. Six months later, she was still writing every proposal herself, sometimes until midnight, while her senior consultant handled only admin tasks well below her capability.

The pattern is familiar. Her WhatsApp was a 24-hour approval chain. The team sent drafts, she edited and returned them, they revised, she edited again. The team had learned to send rough drafts because she would rewrite them anyway. She had learned that delegation does not work. Both conclusions were wrong. What failed was not delegation. What failed was jumping from "I do everything" to "you own it" with no steps in between.

The core exercise: Map your delegation ladder

Take the three time leaks you identified in the Time Audit. For each one, you are going to place it on the ladder and decide the next rung up.

The five rungs:

1. I do it, they watch. You perform the task while the team member observes and takes notes. This is for brand-new handoffs where the person has never seen the work done.
2. We do it together. You and the team member work on it side by side. They handle the straightforward parts. You handle the judgment calls. You explain your thinking out loud.
3. They do it, I review before it goes out. The team member completes the full task and you review the output before it reaches the client or takes effect. You give specific feedback - not "this is wrong" but "here is what needs to change and why."
4. They do it, I review after. The team member completes and ships the work. You review it afterwards and give feedback for next time. The work goes out on their authority.
5. They own it. The team member has full ownership. They make decisions, handle exceptions, and only escalate true emergencies. You see results in a weekly or monthly review at the relationship level.

Step 1 - For each of your three time leaks, mark the current rung. Be honest. If you are rewriting their work before it goes out, you are at Rung 3 at best, regardless of what you told them about "ownership."

Step 2 - Decide who holds each task. Write the person's name next to each item. If there is no one capable, that is a hiring or training signal - note it but do not let it stop the exercise.

Step 3 - Define the next rung up for each task. You are not jumping from Rung 1 to Rung 5. Pick the single next level. Write down what specifically needs to happen for that move - a checklist, a template, a 30-minute walkthrough, a set of boundaries for decisions they can make without asking you. Start with the first handoff tool to practise on one task, then use the delegation map to expand across your team.

Step 4 - Set a timeline. For each task, write the date by which you will move it one rung up. Two to four weeks per rung is realistic for most service businesses. Put this date in your calendar.

Step 5 - Have the conversation. Sit down with each person and tell them: "I am moving this to you. Here is the level of ownership I am giving you right now. Here is what I need from you. Here is when we will review and move to the next level." Be explicit. Ambiguity is where delegation dies.

What success looks like

Each of your three time leaks has a named owner, a current rung, a target rung, and a date. The people holding those tasks know exactly what level of authority they have and what the boundaries are. You have a clear, time-bound path from "I do everything" to "they own it" - and it no longer feels like a leap.

Common mistakes

1. Jumping rungs. Moving a task from Rung 1 to Rung 4 because you are impatient. The team member fails, you lose trust, and the task snaps back to you. One rung at a time.
2. Delegating the task but not the authority. Telling someone to "own" client scheduling but requiring them to check with you before confirming any booking. That is Rung 3, not Rung 5. Match the authority to the rung.
3. Not giving feedback at the review rungs. Rungs 3 and 4 only work if you actually review and give specific, constructive feedback. If you just silently fix things or say "looks fine" without engaging, the person never improves and never moves up.

When to move on

Move to Role Architecture when at least two of your three time leaks have been assigned to a named person with a clear current rung and a scheduled move-up date. You do not need to wait until they reach Rung 5, the ladder is a living tool you will keep using. What matters is that the structure exists and the first conversations have happened.

---

Where to focus by team size

• 10 to 19 people: Start with 3 tasks. You are handing off for the first time. Keep it small.
• 20 to 34 people: Your team leads should be at Level 3 or 4 on the delegation ladder for their areas.
• 35 to 50 people: If you are still at Level 1 or 2 on any recurring task, something is structurally wrong.

---

Working prompts

People prompts

• Which team member has the capability to take on more but has stopped trying because you keep taking tasks back?
• When the senior consultant sends you a draft for review, do you give specific feedback or silently rewrite it? What message does that send?
• Who on your team has been at Rung 1 or 2 for more than three months on a task they should own by now?

System prompts

• Do you have a written checklist or template for the tasks you are delegating, or does the team rely on verbal instructions and WhatsApp messages?
• Is there a shared tracker where you can see delegation progress (task, owner, current rung, target rung, date) without asking anyone?
• What is the AED cost of your personal time spent on each delegated task per week? Write the number down. It makes the case for moving up a rung.

AI prompts

• Which delegated tasks generate outputs (reports, proposals, schedules) that could be pre-filled by a template or automated first draft?
• Could a weekly digest replace your manual review at Rung 3 or Rung 4, surfacing only items that fall outside normal parameters?
• Where could a shared dashboard give you confidence in someone's Rung 4 or 5 performance without task-by-task review?

---

Founder exercise

Set aside 45 minutes. Do this alone first, then 15 minutes with each person you are delegating to.

Part A: The ladder map (20 minutes)

1. Take the three time leaks from your Time Audit.
2. For each one, write the current rung honestly. If you are rewriting their output before it ships, that is Rung 3 at best.
3. Write the name of the person who holds (or should hold) each task.
4. For each task, define the next rung up. Write down the specific enabler needed for the move: a template, a checklist, a walkthrough session, a decision boundary, or a set of examples.
5. Set a date for the rung move. Two to four weeks per rung is realistic.

Part B: The handoff conversations (15 minutes each)

1. Sit with each person. Say: "I am handing you this task at this level. Here is what I need from you. Here is what you can decide without asking me. Here is when we review."
2. Ask them what they need from you to succeed at this rung. Write it down.
3. Agree on a check-in date. Put it in the calendar so it does not scroll away in WhatsApp.

Part C: The two-week review (15 minutes)

1. At the check-in date, review each task. Did the output meet the standard? Where did the person get stuck?
2. If the rung move worked, schedule the next one. If it did not, ask why and adjust the enabler, not the authority.
3. Update your tracker. The ladder is a living document.

---

ARCAS lens

The Delegation Ladder maps directly to the Power audit and the Skills audit in the ARCAS diagnosis. A low Power score almost always means the founder is doing work that belongs at lower levels. A low Skills score often means team members have not been given the practice and feedback loops that come from Rungs 2 through 4.

In the Five Levels model, delegation failure sits at the people layer. The leak is a missing structure for how authority transfers from the founder to the team. Not a missing tool or a broken process. Until that structure exists, every attempt at delegation resets to the founder.

People create the trust and the conversation. Systems create the templates, checklists, and trackers that make delegation repeatable. AI can eventually automate quality checks and flag exceptions at Rungs 4 and 5. But the foundation is a named person, a clear rung, and an explicit conversation about authority.

---

Start now: Quick self-assessment

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

Score 24 or above: Your delegation structure is working. Move to Decision Rights. Score 15 to 23: The ladder exists but is not moving. Pick one task and schedule the next rung move this week. Score below 15: Delegation is your primary bottleneck. Your team is waiting for you, and you are doing their work. Complete the full exercise before moving on.