The Delegation Ladder

The reality

A founder runs a 38 person property management business in JLT. The founder delegated tenant onboarding to the operations lead three months ago. Last week a tenant complained that nobody had answered her email for ten days. The operations lead said she was waiting for the founder's input. The founder said he was waiting for her decision. Both were honest. Neither was wrong. The delegation never happened cleanly because the rung of the ladder was never named. Telling someone to "handle it" is shared confusion with a deadline. Not delegation.

Read this if

• A handed-off workflow comes back to the founder for a final decision the founder thought the team would make
• The team and the founder hold different mental models of who owns what
• A new hire spends their first three months asking permission for decisions they were hired to make
• A delegated task collapses when the team member is on leave because the rung was never written down
• The founder catches themselves saying "I told them to handle it" when the work failed
• The senior team would describe the same workflow's ownership in different ways if asked separately

What dysfunction costs

Bottleneck cost. Work the team should be running comes back to the founder's desk because the rung was never set. The founder becomes the escalation path on every workflow, and the calendar fills with decisions a team member could have made.

What success looks like

When delegation is a discipline:

• Every recurring decision in the business sits at one of five named rungs of authority
• The team knows the rung for every decision they touch and can name it without checking
• A decision misrouted to the founder is corrected by pointing at the rung, with no need to relitigate the decision itself
• New hires receive their rung map in week one, before three months of mistakes have to teach it
• The founder spends time on rung 5 (founder-only) decisions and approves rung 4 (recommend-then-act) work without re-doing it
• A team member's leave does not collapse a workflow because the rung was the artifact, not the person

The framework

The delegation ladder has five rungs. Every decision sits on exactly one of them. The discipline is naming the rung in writing for every recurring decision before the work begins.

Rung 1: Wait until I tell you

The team waits for the founder's instruction. Used for novel work the team has not seen before, or for decisions where the founder genuinely needs to make the call (a key client conversation, a sensitive personnel issue). Most founders run too much work at this rung by default.

The behaviour to adopt this week: list every recurring decision currently at Rung 1. Pick one to move up the ladder.

Rung 2: Research and bring me options

The team researches and brings two or three options with a recommendation. The founder decides. Used for decisions where the founder needs the analysis but not the legwork. A vendor selection, a hire shortlist, a pricing change.

The behaviour to adopt this week: pick one Rung 1 decision and move it to Rung 2. The team does the research, you decide.

Rung 3: Recommend and wait for approval

The team makes a recommendation and waits for explicit approval before acting. The founder approves or pushes back, and the action follows. Used for irreversible decisions above a defined threshold (e.g., AED 10,000, USD 2,720) or any decision where the cost of being wrong outweighs the cost of waiting for approval.

The behaviour to adopt this week: define the threshold for Rung 3 decisions in writing. Approvals above the threshold go to the founder. Below the threshold goes to Rung 4.

Rung 4: Recommend and proceed unless you hear back

The team makes the recommendation, waits 24 to 48 hours for the founder to object, and proceeds if no objection arrives. The founder reviews the queue once a day. This rung is the workhorse of effective delegation. It moves work without losing the founder's veto on anything important.

The behaviour to adopt this week: pick three Rung 3 decisions where the founder has approved every recent recommendation without changes. Move them to Rung 4. Watch the founder's calendar reclaim the time.

Rung 5: Decide and inform me at the next checkpoint

The team owns the decision fully. The founder is informed at a regular checkpoint (weekly summary, monthly review) but does not approve in advance. Used for operational decisions inside the team's defined scope. Approve expenses below the threshold. Hire below a level. Reschedule a non-key client meeting.

The behaviour to adopt this week: define the scope for Rung 5 decisions in writing. Anything inside scope is the team's call.

A founder you might recognise

A founder runs a 28 person fitout business in Al Quoz. AED 8M (USD 2.2M) last year. Until April 2026, every variation order above AED 5,000 (USD 1,360) routed through the founder for approval. The senior PM made the recommendation. The founder reviewed. The founder approved. Across 60 projects a year and roughly 300 variations, that was 300 decisions the founder either rubber-stamped or sent back with a small change.

The founder mapped the variations against the ladder over a single afternoon. Variations under AED 15,000 (USD 4,085) where the senior PM had been recommending the same thing the founder approved 95 percent of the time moved to Rung 4: recommend and proceed unless objected to within 24 hours. Variations between AED 15,000 and AED 50,000 (USD 4,085 to USD 13,615) sat at Rung 3: recommend and wait for approval. Anything above AED 50,000 (USD 13,615) stayed at Rung 1: founder owns the decision.

The next quarter the founder spent four hours total on variations, down from twelve the prior quarter. The senior PM ran 220 of the 280 variations on Rung 4. The other 60 came up to the founder, and 5 of them produced changes the founder considered worth making. The team had been ready a year earlier. The ladder had not.

Working through it

1. List every recurring decision the team currently asks the founder about. Vendor selections, hires, contract approvals, scope changes, expense approvals, scheduling conflicts. Aim for at least 20 entries across one week.

2. Sort each decision into one of the five rungs. The default rung most founders use is too low. Push each decision up by one rung if the data supports it.

3. Define thresholds in writing. Dirhams for financial decisions. Categories for non-financial. The thresholds get reviewed quarterly, and they only move up.

4. Communicate the ladder to the team in a 15 minute meeting. The team knows what the founder owns, what they own, and what the boundary is between rungs. Confusion at the boundary is worse than slow delegation.

5. Hold the line for 30 days. When a Rung 4 decision arrives in the founder's inbox, redirect it back to the team. The team needs the data point that the rung is real.

Common mistakes

• Telling someone to "handle it" without naming the rung. Both parties walk away with different mental models. The work either stalls or comes back broken. The fix is the explicit rung name in writing.
• Skipping the threshold definition. A Rung 3 decision needs a threshold in dirhams or categories. Without it, the team escalates everything just to be safe.
• Approving Rung 4 decisions one by one. Rung 4 means the team acts unless the founder objects. Reviewing every recommendation defeats the rung and trains the team to wait. Set a daily 10 minute review window for the queue.
• Demoting rungs after one bad outcome. A team that has run Rung 4 successfully for a quarter does not need to be moved back to Rung 3 because of one mistake. Diagnose the mistake first. The rung usually stays.
• Forgetting the new-hire ladder briefing. A new hire who learns the ladder by trial and error spends three months making the wrong escalation calls. Hand them the ladder in week one as part of the onboarding map.

Self-assessment

Y or N for each.

1. Does every recurring decision in the business sit on a named rung?
2. Are the thresholds for each rung written down in dirhams or categories?
3. Has the team had a 15 minute briefing on the ladder in the last quarter?
4. Does the founder's calendar reflect the time saved by the ladder (less Rung 1 and 2 work)?
5. When a Rung 4 decision arrives in the founder's inbox, does the founder redirect it back to the team?
6. Do new hires receive the ladder map in week one?
7. Has the founder moved at least one decision up a rung in the last 90 days?

Five or more "yes" answers means delegation is doing the work it is supposed to do. Three or four is the band where the founder has named the ladder but has not held the line on it. Two or fewer means the founder is the escalation path on most workflows, and the next 90 days belong to building the ladder out and teaching the team to use it.