For founders, owners, and operators

How do I delegate when it feels faster to do it myself?

By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.

It is faster to do it yourself this week, and that is exactly why you will still be doing it next year. Delegating is not a time trade, it is a capacity trade: you pay a one-time cost to hand off the outcome and the standard, so the work stops routing back through you. "Faster to do it myself" is usually true and still the wrong optimisation, because you are optimising the week instead of the year.

Key takeaways

  • Doing it yourself wins the next two hours and loses every future week.
  • Delegate the outcome and the standard, not the keystrokes, and accept the first attempts land near eighty percent.
  • "Faster to do it myself" is often a hiding spot dressed up as efficiency.
  • The fix is structural: pay the handoff cost once and let one messy delivery stand instead of rescuing it.

The math that makes "faster myself" a trap

The instinct is not wrong about the next two hours. You can almost always do the task faster and better than the person you would hand it to, so in the moment, doing it yourself is the rational call. The problem is the horizon you are measuring. Doing it yourself is faster this week and it is the precise reason the same work lands on your desk again next week, and the week after, because nobody else ever built the capacity to hold it. Delegating is not a trade of your time for theirs, it is a trade of a one-time cost now for a recurring cost forever. Teaching someone costs more today and far less every day after. Doing it yourself costs less today and never stops costing. Founders get stuck because they keep winning the two-hour argument and quietly losing the year. You have always been the fastest person to do it, and that is exactly the reflex that built the company and now caps it.

Two ways to score a delegation decision. The instinct optimises the week: do it yourself, faster right now. The stronger move optimises the year: hand off once so capacity compounds. Doing it yourself is faster this week and the reason you are still doing it next year. Handing off the outcome and standard once is what compounds into a team that delivers. TWO WAYS TO SCORE THE DECISION The instinct Optimise the Week do it yourself · faster right now vs The move Optimise the Year hand off once · capacity compounds Doing it yourself is faster this week and the reason you are still doing it next year. Handing off the outcome and the standard once is what compounds into a team that delivers.

Delegate the outcome and the standard, not the task

The reason handoffs come back wrong, and then get pulled back permanently, is almost never that the person was incapable. It is that they were handed a task without the standard around it. "Write the report" invites a guess. "Write the report so a board member could act on it without a follow-up call" hands over the actual target. Say what good looks like, name the two or three things that must be true for it to be right, and make the ownership explicit so it is theirs to deliver, not yours to hover over. Then accept that the first version lands at maybe eighty percent of what you would have produced. Your job stopped being to produce the best single piece of work and became to raise the floor of the whole team, and you cannot do that while every real task still routes through your hands. Their eighty percent, improved one percent a week, beats your hundred percent that only ever scales to the hours you personally have. (If the pattern is specifically that delegated work returns broken, there is a fuller structural fix in everything I delegate comes back broken.)

Why "faster myself" is often a hiding spot

There is an uncomfortable second reason the phrase is so sticky. Doing the work yourself is comfortable, provable, and finite. You know exactly how to do it, you can see it get done, and it lets you feel productive at the end of the day. The real job of running the business is none of those things: it is the hard conversation you are avoiding, the underperformer you have not confronted, the direction you have not set. "Faster to do it myself" can be an honest efficiency judgment, and it can also be an efficiency costume over avoidance, a way to stay busy in the work you are good at so you never have to sit in the work that scares you. The blunt test is the one worth asking yourself: are you running the business, or are you the highest-paid individual contributor in it? If the honest answer is the second, the delegation problem is not about speed at all.

How to actually break the pattern

Willpower loses this fight, because every individual instance genuinely is faster to do yourself, so telling yourself to delegate more fails by Wednesday. Treat it as structure instead. Pick one recurring thing that keeps boomeranging back to you and hand off the outcome and the standard for it, once, properly. Make the handoff visible, so quietly taking it back would be a public reversal rather than a private convenience. Block the time you would have spent doing it, so the hours do not silently refill with more of the same. Then expect one messy delivery, and let it stand, coaching the specific gap instead of rescuing the result. That first uncorrected handoff, the one where the world does not end and the work still gets done, is the moment the reflex breaks. It is also the Delivery pillar of the Momentum Engine (Direction, Decisions, Delivery): ownership that lives with the team by design, not by your permission each time.

Not sure which work is genuinely yours and which is a hiding spot? The free Operating Diagnostic maps where your week goes and names the first thing to hand off.

Take the free diagnostic

Common questions

Is it actually faster to do it myself?

This week, yes. Over any longer horizon, no, and that is the whole trap. Doing it yourself wins the next two hours and loses every future week, because the work comes back to you again and again while your team never builds the capacity to take it. The honest way to see it is as a choice between a one-time cost and a recurring one: teaching someone costs you more now and far less forever, doing it yourself costs you less now and never stops costing. "Faster to do it myself" is true and still the wrong optimisation, because you are optimising the week instead of the year.

How do I delegate something I can genuinely do better than my team?

Hand off the outcome and the standard, not the keystrokes, and accept that the first few attempts land at maybe eighty percent of yours. Your job is not to be the best individual contributor any more, it is to raise the floor of the whole team, and you cannot do that while every piece of real work routes through your hands. Define what "good" looks like, let them deliver it imperfectly, then coach the specific gap. Their eighty percent that you improve by one percent a week beats your hundred percent that only ever scales to the hours you personally have.

What if I delegate and it comes back wrong?

That usually means you handed off the task without the standard around it, not that the person was incapable. Delegating "write the report" invites a guess. Delegating "write the report so a board member could act on it without a follow-up call" hands over the target. Say what good looks like, name the two or three things that must be true, and make the ownership explicit. If it still comes back broken after that, the problem is a specific skill gap you can coach, not a reason to take the work back permanently.

Is delegating just dumping my work on an already busy team?

No, and that fear is often the polite cover story for keeping the work yourself. Building capacity is not the same as offloading load: you hand off an outcome, you make the standard clear, and you stay close enough to coach without doing it for them. The alternative, holding everything because the team is busy, guarantees the team stays exactly as capable as it is today and you stay the permanent bottleneck. A team only grows into work it is actually given.

How do I stop reflexively taking the work back?

Treat it as a structural problem, not a willpower one, because willpower loses this fight every time. "Faster to do it myself" is usually a hiding spot, a way to stay busy in comfortable, provable work and avoid the harder, more exposed parts of the job. Remove the hiding spot on purpose: make the handoff visible so taking it back is a public reversal, block the time you would have spent doing it, and expect one messy delivery you let stand instead of rescuing. That first uncorrected handoff is the moment the pattern breaks. The Operating Audit builds this into the Delivery pillar as a standing structure.

Related: everything I delegate comes back broken · every decision routes back to me · what is my real mandate as a new VP · managing former peers after a promotion · The Momentum Engine · The Operating Audit · the free Operating Diagnostic · more insights.