The Delegation
Stack

Most delegation fails because it happens in the wrong order. An owner hires someone, hands them a mess, takes the work back a month later and decides that nobody can do it like they do. The person was rarely the problem. The order was.

In the Optional Owner cohort, the middle phase is called Transfer: knowledge into documents, decisions into rules, work into people. The Delegation Stack is that phase written out in full. It has six layers, and each one rests on the one below, so you build from the bottom and resist the urge to skip. Done in order, it makes you unnecessary one piece at a time, until what’s left is the work you’d choose to keep.

Before you start: the map

Start from a week of notes. Every time the business needs you, write it down: the call, the question, the approval, the job only you can do. The Owner Independence Ladder shows how to keep the log and sort it into four piles: the work, the know-how, the decisions and the relationships. The Stack tells you what to do with each note, and in what order.

A good first handover is often the thing that broke most recently. After a disastrous Halloween in my cleaning company’s first year, I didn’t start with a grand plan to delegate. I started with the two jobs that had failed most visibly, the phones and the schedule, wrote them down, and gave them to someone else. It’s still the best place to begin.

1Clear it first

Before you hand anything over, take away everything that shouldn’t exist. It’s the cheapest delegation there is: work nobody has to do. My four verbs for anything that keeps reaching me are write it down, hand it over, automate it, delete it. In the Stack they run backwards. Delete first, automate second, and only then write down and hand over what’s left, so nobody inherits work that should never have existed.

Take every note from your week’s map through three questions, in order:

1. DeleteWhat would happen if we simply stopped?

   Reports nobody reads, approvals that never change the answer, meetings that could be a message. If the honest answer is “not much”, stop, and tell people you’ve stopped.

2. AutomateCould software do it, start to finish?

   Confirmations, reminders, invoices, review requests, the weekly numbers. The 80/20 guide has a calculator for what one repetitive task really costs you.

3. BatchDoes it need to happen this often?

   Small recurring jobs go into fixed blocks of the day instead of interrupting it. What’s left after all three is the real work, and only that goes up the stack.

2Write it down

Knowledge into documents. The rule is simple: if a question reaches the owner twice, the answer becomes a page. You aren’t writing a manual. You’re writing down what you actually do, in the words you actually use, so that someone else can do it without asking you. The test I use is whether a stranger could run the day from it.

The fastest way to write a page is not to write it. Do the job once while recording your screen or talking it through on your phone, then turn the recording into a checklist, and ask the person who’ll use it to fix whatever’s unclear. The 80/20 guide has the six-part page I use for any recurring task, with a filled-in example.

3Hand over the work

Work into people. Hand over the loudest work first, not the hardest: the work that interrupts everything else. The sequence that has worked across hundreds of companies: booking and scheduling first, then customer follow-up, then daily admin, then the parts of hiring that are process rather than judgement. Each handoff is a document plus a boundary: here is how we do it; here is when you decide alone; here is when you come to me.

The boundary matters as much as the document, so write the whole thing down before the first day. I use a short brief with five parts.

Then hand it over in stages rather than all at once. They read the page and watch you do it. They do it while you watch. They do it and you check the result. Then it’s theirs, and you see the numbers.

Two failures are worth naming, because both are the owner’s. The first is handing off a mess: no page, no example, no definition of done. The second is handing off the task but keeping the worry, checking every message and redoing work at midnight, which is surveillance with extra steps. When something goes wrong, fix the page before you judge the person. At the agency, our rule was to hire for warmth and train with documents, because we could teach anyone our software and our scripts, but not to enjoy people.

4Hand over the decisions

Decisions into rules. This is the layer that gets skipped, and it’s why a business with good pages can still wait for its owner. A task without the decisions inside it is only half handed over: the work gets done, and then it queues behind your approval. Escalation rules replace hovering. They say which decisions are theirs, most of them, and which are yours, few and shrinking.

Two ideas help you set the limits. Some decisions are easy to undo and some aren’t; hand over the easy-to-undo ones first and generously, and keep the hard-to-undo ones longer. And spending limits are cheaper than you think: a mistake within a limit costs less than a team that waits for you all day.

Then write the short list of things worth interrupting you for, and nothing else. A good one is short: anything about safety, anything legal or insurance-related, a major customer about to leave, and spending above the agreed limit. Everything else waits for the weekly check-in, and the team knows it will.

It also helps to say how much initiative each rule expects. William Oncken Jr. and Donald Wass described five degrees of it in their classic Harvard Business Review article on management time. They were writing about managers dealing with their own bosses, but the scale works just as well for anything you hand over.11

David Marquet, who commanded a US Navy submarine, found a three-word way to move people up that scale. He had his officers say “I intend to…” instead of asking permission, and if all was well he answered, “Very well.”12 Ask your team to bring you intentions rather than questions, and most of the time all you’ll need to say is yes.

For the few big decisions that involve several people, Paul Rogers and Marcia Blenko of Bain suggest naming who recommends, who must agree, who does the work, who gives input and, above all, the one person who decides.13 One name per decision, written down, ends most arguments before they start.

5Hand over the outcomes

Tasks get done; results get owned. At the agency, the best placements grew from an assistant who answered the phone into a role with judgement in it, rather than a queue of chores. That’s this layer: each seat owns a handful of numbers, and the decisions that move them.

Then protect the ownership. When someone brings you a problem, the next move stays with them. Ask what they recommend, and let them do it. Every problem you take back teaches them to bring you the next one, and you’re climbing back down the ladder.

6Hand over the managing

The last layer is the one that frees you: someone else runs the people. You stop managing the team and start coaching one person, who runs everything else. At Inova Local, Kelli managed our assistants for most of the eight years, and she deserves as much of the credit as I do. One of our clients got their own involvement down to thirty minutes a week, and said, simply, that a lot of it came down to delegation.

What makes this layer hold is a steady rhythm, so your manager knows exactly when you’ll look and you know you don’t need to look in between.

Mike Michalowicz describes the same shift in Clockwork. He sorts all the time in a business into doing, deciding, delegating and designing, and suggests a business as a whole aims for about 80% doing, 2% deciding, 8% delegating and 10% designing.14 Once someone else manages, the designing is what’s left for you, and it’s the part only an owner can do.

Give your manager the layers beneath them too: their own pages, their own decision limits, and in time their own hires. A manager who has to come to you to hire is a manager in name only.

What stays yours

At the top of the stack is the work you choose. Some of it belongs to any owner: the direction, the money, the culture, and the few decisions too big to delegate. The rest is up to you. If you love selling, keep a little selling. If you love training new people, keep that. The difference is that you’re doing it because you want to, and the business would be fine if you stopped tomorrow.

Not hours so much as absence that doesn’t cost anything.

That’s how I once described what an office manager who isn’t in the office gave the owners we worked with at Inova. It’s also what the whole stack gives you.

What to hand over first

When you look at recurring work, judge it by how often it happens and how much judgement it needs. Those two together tell you which layer it belongs to.

Ninety minutes a week and six hours of setup pays back in four weeks and gives you more than seventy hours in the first year. If the payback is under a quarter, do it this month. If it never pays back, go back to layer one and ask whether the job should exist.

Why delegation fails, and the fix for each

The stack in ninety days

One quarter, one area of the business, taken all the way up. Run it alongside the work rather than instead of it.

1. Week 1Keep the map

   A week of notes on everything that needed you, sorted into the four piles.

2. Weeks 2–3Clear it and write it down

   Layer one on every note, then pages for what survives. Record first, write second.

3. Weeks 4–6Hand over the work

   A brief for each job, then the stages: they watch, you watch, you check, it’s theirs.

4. Weeks 7–9Hand over the decisions

   Rules with limits for the situations that came up, and a short emergency list.

5. Weeks 10–12Hand over the outcomes

   A scorecard for the seat, reported every week without being chased.

6. Week 13Test it

   A week away. What breaks gets fixed; what holds becomes permanent. Then the next area, or layer six.

Questions people ask

How much should I check their work?

A lot at first, then less, on a schedule you agreed in the brief. Check results rather than activity: the schedule that went out, not every message that made it. Once the numbers are steady, look at the numbers and nothing else.

I can’t afford a manager. Can I still do this?

Yes. Layers one to five need no manager at all, just pages, rules and people who own their work. Layer six often arrives by promotion rather than recruitment, when a coordinator or senior assistant grows into running the day.

How do I hand over customers who want me?

Introduce the person who’ll look after them while you’re still involved, and let them solve the next problem with you in copy. Step out of the thread a little more each time. Customers mostly want things fixed quickly and kindly, and that rarely needs you personally.

What if I hand something over and it goes badly?

Fix the page first, then talk to the person. If the same mistake happens twice with a clear page and a clear limit, it’s a conversation about the person. Most of the time it’s the page, or a decision nobody wrote down.

What do I do with the time?

Spend the first of it on the next handover, because the stack compounds. After that, it’s the whole point. Decide, deliberately, where you want to be useful, and protect that time as carefully as you once protected the business.

Clear it, write it down, hand over the work, then the decisions, then the results, then the managing. One handover at a time, until what’s left is yours by choice.