Delegate outcomes, not tasks

Part 7 of 9. "You own this outcome" is a different instruction than "do this thing" — and only one of them comes back finished.

Office Clones
October 20, 2026

The most common delegation failure is not the wrong person. It is the wrong instruction.

"Can you send the invoice to the Hendersons?" is a task. It comes back when it is done, or when it is forgotten, and either way you will be the one who notices.

"Own invoicing. Everything billed by Friday, chased until paid, escalated to me if an invoice is more than 14 days late." That is an outcome. It comes with a goal, a deadline, decision rules, and a review rhythm attached.

Only one of those scales past the second week.

Delegate the whole picture

Whoever takes something on should be able to answer five questions without asking you:

1. What does success look like?
2. What am I allowed to decide alone?
3. When should I ask?
4. What tools do I use?
5. When does it get reviewed?

Skip number two and you have created a queue with extra steps — the person will come back for every small decision, and you will conclude they were not ready. What actually happened is that you never said where the edges were.

The handoff should be written down where both of you can see it. Not a hallway conversation, not a voice note. A sentence and a list is enough.

Define roles before you hire

Before adding anyone — employee, contractor, or vendor — write four things: what they own, what they explicitly do not own, what they decide, and how success is measured.

The second one is the one people skip. "What they do not own" prevents the slow erosion that happens when a helpful person absorbs adjacent work and the org chart quietly stops being true.

If you cannot fill those four lines in, the role is not defined yet, and hiring will not define it — it will just make the ambiguity more expensive.

Bring in outside support

Admin, bookkeeping, marketing, customer service, content, and technical implementation are the common places to add outside help.

Whoever you use — an agency, a contractor, a service — the rule does not change: organise and document the work before handing it off, or the owner becomes the bottleneck again on the other side.

This is the part of delegation that surprises owners. Handing off an undocumented process does not remove the dependency. It moves it, adds a communication delay, and creates a second person who now needs you to explain things.

It is also, in fairness, why outside help sometimes gets blamed for not working out. The work was never defined; the vendor was asked to guess. Guessing is not a service anyone can deliver reliably.

The three-question handoff test

Before you hand something off, ask:

• If I were unreachable for a week, would this keep running?
• Would the result be what I wanted, or what I would have done?
• Do I know how I will check in three weeks?

A no to any of these is not a reason to delay the handoff. It is the list of what to write down first.

What delegation is actually for

Delegation is not a productivity trick for getting more done. It is how a business stops depending on one person's memory and calendar.

That has a slightly uncomfortable implication: the goal is not that the work gets done the way you would have done it. It is that the work gets done, to a standard you wrote down, by someone who did not have to ask. The standard is the deliverable. Your preferences matter only where they affect the outcome.

Do this today

Take the thing you most want off your plate. Write the five lines. Then notice how many of them you had to invent — that count is how much of it lived only in your head.

What this is part of

Part seven of nine in How to Be a Real CEO in 30 Days or Less. The CEO Goals worksheet in the full guide carries an owner and a first step for each goal, which is the same discipline applied upward.

[Get the full guide and the four worksheets →]

Next Thursday: the business that never reviews itself repeats its own mistakes — and a monthly review that takes twenty minutes.