To delegate so the work doesn't come back to you, hand off a whole result, not a pile of tasks. Write the process on one page first. Define what winning looks like with one number. Spell out which decisions are theirs. Work side by side long enough to coach. Then let go for at least 30 days, and don't take it back when something goes wrong.
Most delegation fails for one reason. The owner tosses the work over, it goes sideways, and the owner grabs it back. That teaches the team the work was never really theirs.
Why does delegated work keep coming back to you?
Because most delegation is done in a hurry. You are drowning, so you push work at someone and hope it sticks. No context. No coaching. No time together on it. When it goes wrong, you take it back and tell yourself, "It's easier if I just do it myself."
I call that a fumble. In sports, a fumble is when the ball gets dropped in the exchange. It happens when one person lets go before the other has a grip.
A real handoff is the opposite. Think of a handoff in football or a relay race. For a moment, both people have a hand on the ball or the baton. The person giving it doesn't toss it and walk away. The person getting it doesn't have it thrown at them mid-stride. Only when the grip is secure do you let go.
That is what good delegation looks like in a business. In the FOSS Method, we call it the Handoff.
What does "delegating effort instead of ownership" look like?
I learned this in the place I felt strongest. Sales was always my lane. It was the part of the business I loved most, because I could see the work turn into results. As we grew, I handed off the smaller accounts, but I kept the big ones. I told myself I was protecting the team. What I was really protecting was control.
When I finally handed off some of those big relationships, I thought I did it well. I walked the rep through everything I knew. Then something went wrong. The client called me, not the rep. And I fixed it. The second time, the rep brought the problem straight to me. I fixed that one too.
That's when it hit me. I wasn't delegating ownership. I was delegating effort. I was still the safety net, and I was teaching my team that when things got uncomfortable, they came back to me.
So I changed. The next time something came up, I didn't take it back. I walked the rep through how I would think it through, and then the rep handled it. Over time, the questions stopped. The rep owned it, and in most cases the client was better taken care of than when I was holding on.
What should you delegate first?
Not everything at once. Pick one responsibility. A good first pick is the thing that interrupts you most often, or the thing where the only reason it is yours is that nobody does it as fast as you.
Keep the work only you should do: the direction of the company, the culture, and the final big calls. Almost everything else is a candidate.
If you are not sure what is on your plate, start with a list of everything that runs through you. I walk through how to build that list in The Founder Bottleneck: Why Everything Still Runs Through You.
What is a delegation framework that actually sticks?
Here is the five-step framework I teach owners and CEOs.
Step 1: Put the process on one page first
If the process still lives in your head, you aren't handing off ownership. You are handing off confusion.
Write down how the work actually gets done: what starts it, the steps in order, the decisions inside it, who makes each one, and the one number that tells you it is working. Keep it to one page. Think of your grandmother's recipe card, not a cookbook. If it doesn't fit on one page, you went too deep.
Don't write it from memory at your desk. Go watch the work happen, or walk through it yourself from start to finish. Every time someone makes a decision, that is a step. Every time the work moves from one person to another, that is a step. I call this page a Process Play, and the free Process Play sheet gives you the layout.
Step 2: Choose the right person and the right piece
Before you hand it over, ask three questions:
- Does this person actually want it?
- Can the business survive the learning curve while they grow into it?
- Are you holding on because it is truly yours, or because it is comfortable?
If the answer to the first two is no, pick a different piece or a different person. If the honest answer to the third is "comfortable," that is your sign to let it go.
Step 3: Define what winning looks like
Not every step. The outcome. Pick the one number that tells you this is working, and the target that proves it. If you can't name the number and the target, you are not ready to hand it off yet.
Then write down two lists:
- Decisions they can make without you.
- Decisions that still come to you.
If you dictate every move, you aren't handing it off. You are supervising with extra steps.
Last, put two dates on the calendar: the day you start running it together, and the day you let go. Decide how often you will check in between them. Without dates, "together" quietly becomes forever.
Step 4: Run the overlap
This is the step most leaders skip. Walk them through the one-page process. Then let them run it while you watch. When they get stuck, coach with questions, not corrections: "What would you do here?" "What does the page say?"
The hardest part isn't watching them struggle. It is staying quiet long enough for them to figure it out. Your silence is the training. Every time you jump in with the answer, you steal a rep they needed.
Step 5: Let go, and don't take it back
They will make mistakes. Every instinct you have will tell you to step in and fix it. Don't. A mistake made while you coach them builds confidence. A rescue builds dependence. The moment you take it back, you teach them it was never really theirs.
Let them run it for 30 days, their way, mistakes and all. Watch the result, not every move along the way.
Eighty percent done by someone else is more powerful than a hundred percent done by you.
What should you say when you hand something off?
Say out loud what you are doing. Something like this:
"I'm handing this to you because I trust you with it. Here's the process. Here's what winning looks like. I'm going to coach you through it, and then it's yours. When something goes wrong, and it will, bring it to me and we'll work through it together. But I'm not taking it back."
That last sentence changes everything. Most people have been handed work before and had it yanked away the first time something broke. Saying it up front tells them the ownership is real.
What do you do when it goes wrong?
Expect it. When the problem comes to you, don't solve it. Ask a question that puts the thinking back on them. If they are truly stuck, walk them through how you would think about it, then let them make the call and do the work.
Then check in once a week on two things. Did the result hold up to the bar you set? And did you take it back? If you took it back, own it, reset the overlap, and try again.
How do you know your delegation is working?
You will see it in three places:
- Your calendar. More time spent coaching people, less time doing their work.
- Your decisions. Fewer of them route through you each week.
- Your instinct. When someone brings you a problem, your first move is a question, not an answer.
Give it 30 days, not a week. The shift doesn't happen in one conversation. It happens in the pattern.
Get the free delegation worksheet
Everything in this article fits on The Handoff play sheet, a free, printable delegation worksheet. Page one walks through the steps. Page two is your list of everything that runs through you. Page three is the one-page process and a 30-day log for letting go.
Delegation is one piece of a bigger build. For the full path, from fixing your own day to a company that stands on its own, read How to Build a Business That Runs Without You.