How to Delegate When You Can Do It Better Yourself

You probably can do it better. That's not arrogance. It's often true, especially when you've been promoted from a specialist role into leadership. You've spent years developing skills that your team is still building. And every time you hand off work that comes back at 70% of what you'd have produced, a small voice says: "I should have just done this myself."

The voice is wrong. Not because quality doesn't matter, but because your job has fundamentally changed. The question is no longer "what's the best output I can produce?" It's "what's the best outcome my team can produce without me?" Those are different questions, and they lead to very different behaviours.

The Control Trap

Sam ran a design team of six. Every brief that went to a client passed through his hands first, and he revised most of them. His work was excellent. His team's growth was stagnant. "I kept telling myself I was maintaining quality standards," he said. "But really, I was maintaining my relevance."

This is the control trap. It disguises itself as quality assurance, but it's actually a refusal to tolerate the discomfort of imperfect output. And the cost compounds. Your team stops taking ownership because they know you'll redo it. They stop growing because they never face the consequences of their own decisions. And you end up overworked, under-leveraged, and wondering why nobody steps up.

The first step out is recognising what the trap actually costs you. If you spend 15 hours a week polishing your team's work, that's 15 hours you're not spending on strategy, stakeholder relationships, or developing the very people who could eventually take that work off your plate for good.

A Framework for Letting Go Without Losing Quality

Not everything should be delegated the same way. The mistake most managers make is treating delegation as binary, either "I do it" or "they do it." But there's a spectrum, and matching the right level to the right task is where the skill lives.

Full delegation: The outcome matters, the method doesn't. "Get this done by Thursday. You decide how." Use this for tasks where your team has existing competence and where the learning opportunity outweighs the risk of a suboptimal result.

Guided delegation: Share the outcome and the approach, but let them execute. "Here's how I'd structure this proposal. Take it from here and show me a draft before it goes out." This works when someone is stretching into new territory and needs a framework, not a script.

Collaborative delegation: Work on it together, with them leading. "Walk me through your thinking on this, and I'll share where I'd push it further." This is for high-stakes work where the quality bar is non-negotiable but the developmental opportunity is too valuable to skip.

The key is movement. If you're still doing guided delegation for the same task after three months, something's off. Either the person needs a different kind of support, or you're holding on tighter than you need to.

What "Good Enough" Actually Means

Here's a question that changes the game: "Is this good enough for its purpose?"

Not "is this as good as I'd make it?" Not "is this perfect?" Just: good enough for its purpose. A client-facing pitch deck needs higher polish than an internal status update. A first draft needs to be structurally sound, not flawless. When you judge everything against your personal best, you create a standard that prevents your team from ever succeeding.

Try this: the next time someone gives you work that's not quite what you'd have produced, before you edit it, ask yourself two questions. First, will this achieve its objective? Second, if I fix it, will this person learn anything? If the answer to the first is yes and the second is no, send it as is.

The discomfort you feel when mediocre-but-acceptable work goes out with your team's name on it? That discomfort is the feeling of your team getting stronger. Learn to sit with it.