If work you delegated keeps landing back on your desk, the problem usually isn't your team. You handed over the steps and kept the decision. Real delegation means handing off an outcome, saying out loud how much authority comes with it, and then not taking it back when it gets uncomfortable. Here's how to do all three.
You handed over the steps and kept the decision
The typical handoff sounds like this: "Can you put together a comparison of the three vendors?" Your team member does exactly that. Then they come back with questions, because they don't know what you're optimizing for. Then they bring a draft, because they don't know whether they're allowed to pick. You don't love the draft, so you rewrite it.
Two weeks later you're doing the original work plus managing the handoff. Founders take that as proof that "nobody does it like me," and they stop delegating.
The reality is the handoff was built to come back. A task with no outcome and no authority has only one place to go when it gets hard: up.
Decide what to keep before you hand anything off
Most founders delegate randomly, whatever feels heaviest this week. Start with a clearer filter. Rate everything on your plate on two questions: do you love doing it, and are you great at it?
- Love it and great at it. This is your highest-value work. Keep it.
- Love it, not great at it. Enjoyable, but someone else could do it better. Hand it off soon.
- Don't love it, great at it. The hardest one to let go, because you're good at it. Hand it off now anyway.
- Don't love it, not great at it. It's costing you twice. It should never have been on a founder's desk.
The target is to spend at least 80% of your time in the first two. Most founders I work with are nowhere close when they start.
Hand off the outcome, not the method
Compare two handoffs.
The task: "Put together a vendor comparison."
The outcome: "Get us a vendor contract that cuts cost 10% without slowing turnaround. You pick the vendor. Bring me the signed agreement."
The second one tells your team member what winning looks like, lets them choose the route, and gives them something they can own. It also takes you out of the middle. You're no longer the approver of every step. You're the person who defined the result.
If you're nervous about handing over the method, say what the guardrails are instead: budget, timeline, non-negotiables. Then let them solve it inside those lines.
Name the decision right out loud
This is the step almost everyone skips, and it's why decisions keep bouncing back. Every delegated outcome needs a level of authority attached. I use four:
- Act independently. No need to report back.
- Act, then report. Make the call and tell me afterward.
- Propose and proceed. Tell me what you're going to do, and go unless I stop you.
- Ask first. Get approval before acting. Save this for the truly high-stakes calls.
Here's the pattern I see: most delegated work sits on level 4 by default. Nobody ever said otherwise, so your team assumes they need your sign-off, and every decision waits for a slot on your calendar. Move one decision type down a level this week and watch how much faster it moves.
Don't take it back
The final failure is the quietest. The work gets done differently than you'd have done it, and you step back in. Maybe you fix a slide. Maybe you answer a customer email directly. Every time you do, you teach the team that the handoff was temporary.
If the result is acceptable, let it stand, even if it isn't how you'd have done it. If it isn't acceptable, coach the owner. Don't redo the work. Say: "This is yours. Here's what I'd push on. Bring it back when it's done."
The Feldman Delegation Map
The Feldman Delegation Map walks you through both halves of this. The Delegate and Elevate matrix sorts your work by what you love and what you're great at, so you know what to keep. The Decision Rights Ladder sets how much authority goes with each handoff. The tool also covers handing off outcomes instead of methods and resisting the pull to take work back.
Hand off outcomes, name the authority, and hold the line. That's how you stop being the place every decision goes to wait.
Open the Feldman Delegation Map →Get the next lesson in your inbox
Short, practical lessons like this one for founders running $1M–$20M companies, plus every new free tool before anyone else.
If this is the call in front of you, let's talk it through.
A focused 30-minute conversation. No pitch. Just a direct discussion about the decision and whether I can help.
Book a call with Danny →
Danny Feldman is a 3× founder and the advisor behind Feldman Advisory. He founded and scaled Stellar to $100M in annual revenue across 15 states, raised $55M+ as a founder, and used AI to double revenue before exiting to private equity. Earlier, he recruited and trained 55,000+ sales reps at Cutco and grew a division from 1 to 58 locations. Operator to operator, he now helps founders of $1M–$20M companies get out of the middle of the business, build the leadership team, and raise capital. Book a 30-minute call →