You've walked someone through a task, answered all their questions, felt good about it — and two weeks later you're back doing it yourself. That's not a people problem. It's a handoff problem.

You're handing off tasks, not systems

Most business owners show someone what to do once and assume it'll stick. Or they go the other direction: a perfectly written, 40-page SOP covering every possible scenario from top to bottom. Both fail for the same reason.

What you're actually handing off is your judgment. The part you didn't write down. What "done" looks like. When something is worth escalating. What to do when the process breaks and none of the documentation covers it. Without that, the person you handed to is just guessing until you show up again.

It's a lot like raising a kid. You don't just tell a three-year-old to put their dish in the sink once and move on. You reinforce it, day after day, until it becomes second nature. You're not teaching them to follow steps — you're teaching them to be independent. The same logic applies when you're bringing someone new into your business.

What a real handoff actually needs

A real handoff has three things. A clear definition of done. A decision they can make without you. And a way to know when something went sideways.

That last one matters more than most business owners realize. If someone doesn't know what qualifies as an emergency, they'll either bother you constantly or go quiet until the situation is already bad. Both are worse than just defining it upfront. With my own clients, we work out a clear protocol: what's routine, what gets an email, what actually warrants a text. That kind of structure removes a ton of friction on both sides.

You don't need a 40-page SOP

You need just enough documentation that someone else can get to the same answer you would without texting you first.

The best place to start is the last time something broke. What happened? What did you do? Why did you do it that way? Write that down, put it somewhere people can find it, and move on. It doesn't need to be polished. If it's valuable, you'll come back and refine it. If it's not, you'll forget about it — which is actually fine.

What you don't want is to spend an hour in a meeting with five people deciding how to document a process when you could have just written the thing. Perfectionism upfront is a waste of time.

Consider the classic ops person situation: a business owner spends two hours onboarding them on client follow-up. First week goes fine. Second week, an edge case comes up — a client situation that didn't fit the script. The ops person doesn't know what to do, doesn't want to get it wrong, and either pesters the owner constantly or spins their wheels waiting. By the time the owner finds out, the client's already cold. The ops person wasn't the problem. The handoff just didn't cover what happens when things go sideways.

Teach a man to fish

Give someone a task and they can do that task. Teach them how you solve problems, what your values are when things get messy, and how to make a judgment call in a gray area — and they can handle situations you never anticipated.

This is especially true when you're in the one-to-twenty-employee range. Heavy documentation is more useful at scale — 50, 100 people — where you genuinely need to systematize knowledge transfer. Early on, culture and judgment do most of that work. If anyone in your shop ever faces a choice that isn't covered by a rule, the answer should already be obvious based on how you do things. That's not something you write in a doc. It's something you model and reinforce over time.

If you're a business owner who keeps getting pulled back into work you thought you already handed off, book a free 30-minute call — the link is in the show notes.