The Handoff That Never Actually Happened
You explained it clearly. Twice, actually.
The task was supposed to move to Sarah three weeks ago. Reconciling the weekly supplier invoices against purchase orders. Not complicated. You walked her through it on a Tuesday, answered her questions on Thursday, and considered it done.
Except last Friday, when the numbers didn't match, Sarah pinged you. And you ended up doing it yourself because it was faster than explaining the edge case. This Friday, same thing. Different edge case, same outcome.
The task never actually left your plate. It just pretends to leave, then comes back.
This is the handoff that never happened. It looks like delegation. It feels like progress. But the work still routes through you, just with extra steps.
The pattern shows up everywhere:
- You "handed off" social posting, but you still write the captions because the drafts never sound right.
- You "delegated" customer enquiries, but you review every response before it goes out.
- You "trained someone" on the monthly reporting, but they message you with questions every time.
None of these are delegation failures in the traditional sense. The person is willing. They're capable. They understood the explanation.
The failure is in what you handed over: a verbal explanation, maybe a quick screen-share, and an assumption that understanding equals ownership.
A real handoff has four parts. Skip any of them and the task bounces back.
1. The documented process.
Not a training session. A document. Something they can check at 9pm on a Sunday when you're not available and the supplier's invoice has a line item that doesn't match anything.
This doesn't need to be elaborate. A Notion page with six bullet points and two screenshots often does more than a thirty-minute walkthrough. The test: can they do the task without asking you a single question? If not, the document isn't finished.
2. The decision rules.
Explaining the process covers the 80% case. The other 20% is what pulls you back in.
When the invoice amount is wrong, do they email the supplier or flag it for you? When the PO number is missing, do they search for it or reject the invoice? When it's a new supplier not in the system, what's the first step?
These micro-decisions feel obvious to you because you've made them five hundred times. They're not obvious to anyone else. Write them down.
3. The explicit boundary.
There's always a line where the task genuinely does need you — a judgement call that requires context they don't have, or a decision with consequences above their pay grade.
Name that line explicitly. "If the discrepancy is under £200, resolve it yourself. Over £200, flag it to me." Now they know. No more pinging you for a £40 variance. No more making a call on a £2,000 error they shouldn't be making.
4. The feedback window.
Handoffs fail silently. The person hits a snag, works around it, doesn't mention it. The workaround becomes habit. Six months later you discover they've been doing step three completely wrong the entire time.
Build in a checkpoint. First two weeks: review every output together. Next month: spot-check twice a week. After that: monthly audit. The feedback window is how the documented process gets better. It's also how you actually let go.
The real cost here isn't the time you spend on the task itself. It's the mental weight of tasks that are supposedly someone else's but still live in your head.
You're not running one business. You're running yours, plus the shadow version where you're still the backup for every role you've tried to delegate.
That's the bottleneck that doesn't show up in any time audit. You can't measure "waiting for something to go wrong so I can step in." But it takes up space. It stops you from thinking about the things that actually need a founder's attention.
Pick one task this week. Something you've "handed off" but still touch regularly.
Write down the process in enough detail that someone could do it without you. Add the decision rules for the edge cases. Draw the explicit line for when it comes back to you. Set the feedback checkpoints.
Then actually step back. Don't peek. Don't preemptively check. Let the system catch the mistakes instead of your vigilance.
That's what a real handoff looks like. Everything else is just delegation theatre.
If you're looking at a list of tasks that never quite left your plate, and wondering how to make any of them actually stick elsewhere — that's the kind of thing we dig into.