How to Delegate a Task You're Better At Than Anyone on Your Team

The task nobody wants to delegate is the one they're best at. It feels faster to just do it yourself, and there's a real cost to handing it off — a junior teammate will take three times as long the first few tries, and the output won't match yours for a while. But holding onto it is a slower kind of expensive: it caps your team's growth, and it caps how much you can actually take on next.

Separate "I'm best at it" from "only I can do it"

These get treated as the same thing and they're not. Being the fastest person at writing the quarterly report doesn't mean you're the only one who could learn to write it well. Before you decide something's non-delegable, ask: is this actually specialized, or is it just familiar to me because I've done it fifty times and no one else has done it once? Most "only I can do this" tasks are really "only I have done this" tasks — which is a different, much more fixable problem.

Delegate the version, not the whole thing, at first

Handing over your best skill in one shot — "here, you own the client presentations now" — sets both of you up to be disappointed. Instead, break it into a version they can actually own this round. If you're the one who always writes the sharpest client-facing summary, don't hand off the whole document. Have them draft it, you edit it visibly with comments explaining the "why" behind each change, and next time they draft with fewer edits needed. Three or four rounds of this is usually faster than you'd expect, and it beats either extreme — doing it yourself forever, or dumping it on someone unprepared and hoping for the best.

What this looks like in practice

Weak handoff: "Can you take the client update this week? Let me know if you have questions."
Better handoff: "Draft the client update using last week's as a template. I'll mark up anything I'd change and explain why — the goal is that by round three you don't need my pass at all."

The second version tells them what "done well" looks like and sets an explicit endpoint for your involvement, so it doesn't quietly become a task you're still doing every week under a different name.

Protect the standard, not the task

What you actually don't want to give up is usually the bar, not the task itself. If you're worried a report will get sloppy once someone else writes it, that's a signal to be specific about the standard — "every number needs a source, and the summary goes above the fold" — rather than a reason to keep doing it yourself indefinitely. Write the standard down once, and it becomes something you can hand off along with the task, instead of something only you carry in your head.

Expect the dip, and say so out loud

The first two or three times someone else does your best task, it will be visibly worse than when you did it, and that's normal, not a sign delegation isn't working. Tell them this upfront: "This will probably be rougher than what I'd produce for the first few tries — that's expected, not a problem." Naming the dip in advance takes the pressure off both of you and makes it much less likely they quietly avoid the task out of fear of getting it wrong.

Track it, so you actually notice the shift

Delegation that works is easy to forget happened, because the moment it succeeds, the task just quietly stops being yours. That's useful to have on record — both as proof you're building your team's capability, not just offloading work, and as a concrete example for your own next review or promotion case: "I trained someone else to own X, and it freed me up for Y." Log it when it happens rather than trying to reconstruct the timeline later. A quick voice note in Strivo — what you handed off, who took it on, how it went — gets tagged as a leadership memory automatically, so it's on hand the next time someone asks for an example of you building up your team rather than just managing it.

A test for whether you're actually ready to let go

If you catch yourself redoing someone's work rather than coaching it forward, you haven't delegated yet — you've just added a review step. The real handoff happens when you can look at a rougher version of your best work and let it ship, with feedback for next time instead of a rewrite this time.