A field guide for founders who keep getting pulled back into the work they hired someone to take off their plate.

Every founder I work with has tried to delegate. Most have tried more than once. They hire the right person. They block out time to onboard. They even repeat themselves patiently for the first week or two.

And then, somewhere around week four, the work starts creeping back onto their calendar. A question in Slack. A small fire they need to put out. A decision that "only you can make." Before long, they are doing the thing they hired someone else to do. Their team is waiting. Their inbox is full. And they are quietly convinced the issue is them.

It is not.

The issue is that delegation is almost never taught as a system. It is taught as a personality trait. Trust more. Let go. Stop being a control freak. None of that advice survives contact with a real business where the work is messy, the team is small, and the founder is still the person who understands why every decision matters.

If you have been around my work for any length of time, you already know where I land on this. Delegation is a design problem, not a mindset problem. And the reason it keeps failing is not because founders care too much. It is because the handover itself was built to break.

Why founders resist delegation (even when they want to)

Let's start with the part nobody says out loud. Most founders resist delegation not because they are controlling, but because they are responsible. They built the business. They hold the client relationships. They know which details, if missed, would blow up a launch. And the honest truth is that handing that off to someone who does not carry the same weight feels reckless.

That resistance is not a flaw. It is context your team does not have yet.

The problem is that most founders try to solve it by doing the work themselves "just this one time." One time becomes the default. The team stops offering to help because the founder has already absorbed it. And the founder becomes the bottleneck in a business they designed to scale.

On the other side, the cognitive cost is quieter but just as real. Every open loop in your business, every decision only you can make, every context only you hold, takes up working memory. You feel it as the low hum of tiredness that does not go away even after a short week. You feel it as Sunday dread. You feel it as the inability to focus on strategy because you are still holding the operational details in your head.

Delegation, done well, does not just free up time. It frees up thinking space. And thinking space is the single most undervalued asset in a solo or small-team business.

The three reasons delegation breaks down

Before we get to what works, it helps to name what does not. In the businesses I work with, delegation fails for one of three reasons, and usually a combination of all three.

1. The process lives in the founder's head.

If the only documentation is a twenty-minute Loom and a Slack thread from three weeks ago, your team is not being delegated to. They are being quizzed. Every small variation requires them to come back to you, which reinforces the pattern you are trying to break.

2. The founder delegates the task but not the outcome.

"Can you put together the client report?" is a task. It is not clear what a good report looks like, what decision it needs to support, or what success means. The founder ends up reviewing, rewriting, and eventually redoing the work, because the brief was never actually complete.

3. There is no feedback loop.

Work gets handed off and then vanishes into a black box until something goes wrong. No checkpoints. No shared definition of "done." No small course corrections along the way. By the time the founder sees it, fixing it costs more than doing it from scratch would have.

Notice what all three have in common. None of them are about trust. They are about the absence of structure. And structure is something you can build.

The system that actually works

When I teach founders how to delegate inside the Focus Vault Experience, the shift is always the same. We stop treating delegation as a moment (the handover) and start treating it as a system with three deliberate steps. This is the exact framework I walked through in the masterclass on Friday, and if you missed it live, the replay is below.

Step one: Capture the process before you hand it off.

Not a full SOP. Not a 40-page manual. A working capture. Record yourself doing the task once, narrate the decisions you make as you go, and list the three to five inputs that need to be true for someone else to run it. The goal is not perfection. The goal is to externalize the context you have been holding in your head so someone else can actually hold it too.

This is the single highest-leverage hour you can spend this quarter. One hour of capture saves you fifty hours of re-explaining over the next year.

Step two: Define the outcome, not the method.

Once the process is captured, your brief to your team changes. Instead of telling them how to do it step by step, you tell them what good looks like. What does the finished output need to enable? Who is it for? What decision does it support? What constraints matter and which ones do not?

This is the part most founders skip because it feels slower. It is not. A clear outcome gives your team the one thing they need to work without pinging you: judgement criteria. When they know what good looks like, they can make the small calls themselves. When they do not, every small call becomes your problem.

Step three: Build a feedback loop into the handover.

The final piece, and the one that keeps the first two from unraveling, is a predictable rhythm for review. A weekly fifteen-minute check-in. A shared doc where progress lives. A standing question at the end of every handover: what would make this easier next time?

The feedback loop is what turns a one-time delegation into a repeatable system. It is how you move from "I did it for you this time" to "you own this now, and here is how we keep it tuned."

Together, these three steps form the framework I teach inside the Focus Vault: capture, define, and loop. It is deliberately simple because the point is not to add more to your plate. The point is to make sure the work you hand off actually stays off your plate.

What changes when the system holds

The founders I have watched implement this do not become different people. They do not suddenly become hands-off or stop caring about the details. What changes is where their attention goes.

Strategy stops being something they squeeze in between client work and becomes the work. Their team stops asking for decisions that live inside their own scope. Client outcomes improve because the work has structure behind it. And the quiet cognitive drag that made Sunday evenings feel heavier than they should, that lifts too.

That is the real prize here. Not the hours back, although those come. The thinking space. The ability to lead your business instead of running alongside it.

Where to go from here

If this resonates, the full framework is what I walk through in the free Monthly Focus Framework Masterclass. This is where I go deeper into each of the three steps, with the exact steps and templates I use with my clients. Feel free to explore more!

You do not need to become a different kind of founder to delegate well. You just need a system that does the heavy lifting the moment your attention has to go somewhere else.

That is what I want for you this quarter.