Delegation Dies at the First Mistake

Most handovers die at the first mistake. Usually the person was doing fine; the problem was that nobody had agreed in advance how much was allowed to go wrong.

I watched a founder hand his weekly production plan to a plant manager on a Monday morning. In the second week there was one stockout: a single product, on one day, for one unhappy client. By the third week the founder was back to signing every plan himself. When people talk about founder burnout while scaling a business, they picture overwork, but what I saw that month was quieter and more structural, a handover that lasted eleven days.

The Moment Delegation Dies

Almost every delegation in a founder-led company has a precise moment of death, and it's rarely the handover itself. It's the first mistake. The task leaves the founder's desk, runs for a week or two, hits one error and comes straight back. Everyone in the room calls it a lesson, and the founder says the person wasn't ready.

In most cases I've seen, the person was ready. What wasn't ready was the founder's tolerance for an imperfect first attempt.

What Actually Broke

It took me years to see this part clearly. The founder handed over the task but kept the right to be wrong for himself. He gave away the doing while keeping a standard that only he was ever allowed to miss, which was to be correct on the first try.

A plant manager who makes one scheduling error in week two is doing exactly what anyone does in a new job. If the unspoken rule is zero defects from day one, though, that first mistake gets treated as a verdict on the person instead of feedback on the work. Someone working with no margin for error is being supervised on a longer leash rather than trusted with the decision. The leash felt like freedom for eleven days, then the first test snapped it back, and the founder mistook the snap-back for wisdom.

The Second Version of the Same Story

I saw the same pattern at a Rs. 35 Cr services firm, in a completely different function. The founder handed client scoping to a senior account lead. One proposal went out underscoped, the margin on that project shrank, and within a fortnight the founder was reviewing every scope again.

The account lead hadn't become incompetent overnight. She had made one mistake the firm could undo, and the founder reacted as if she'd made one it couldn't. That confusion, between a mistake that can be reversed and one that can't, sits at the centre of the whole problem.

The Misdiagnosis

When this happens, founders nearly always reach for one of two explanations, and both are wrong. The first is "I hired the wrong person", which sends them into another hiring round for a problem no hire can solve. The second is "I'll delegate again when they're ready", which in practice means never, because readiness gets defined as never making a mistake and nobody clears that bar. Both explanations protect the founder from the harder fact that the terms of the delegation were never set.

The Real Cause

The structural cause is missing tolerances. In a working system, every delegated decision carries a defined margin: how much can go wrong, how the error gets caught and at what point someone steps back in.

In a founder-led business that runs on the founder's instinct, none of that is written down, because the founder never needed it. He absorbed his own errors silently and corrected them before anyone noticed. So when he hands the task over, he hands over the visible work and keeps the invisible shock absorber, and the delegate inherits the job without the buffer. The first bump is enough to knock them off the road.

What the Fix Actually Looks Like

The fix is a small piece of structure the founder installs before the handover, instead of a pep talk after the failure. It has three parts.

  • An error budget. Before the handover, the founder names how many mistakes, or what size of mistake, the role is allowed to make.
  • A correction loop. There's a set moment, weekly or after each decision, where founder and delegate look at the mistake together and adjust the pattern.
  • A re-engagement threshold. This is the specific point at which the founder steps back in on purpose, rather than by reflex.

With those three in place, the first mistake becomes information the firm can use instead of a verdict on the person.

How to Size the First Error Budget

When founders ask me how to set the number, I give them four questions to answer before the handover. Is this decision reversible within a week? If it is, allow at least three mistakes before any review, because a wrong call that can be undone costs the firm a day rather than a year. What's the worst realistic cost of one wrong decision here? Put a rupee ceiling on it and delegate freely below that ceiling.

Who catches the error, and how fast? Naming the person and the point where errors show up means a mistake surfaces in days instead of quarters. And at what point does the founder step back in? Deciding that in advance turns re-engagement into a rule the delegate knows about, instead of a reflex set off by the first bad week.

The Objection Founders Always Raise

"But some mistakes are fatal," founders tell me, and they're right. That's why decisions get sorted by reversibility before any budget is set. A mistake that can be undone, like a wrong reorder, an underscoped proposal or a mistimed campaign, deserves a generous error budget because fixing it is cheap. One that can't be undone, like a compliance breach, a safety call or a contract the firm can't exit, deserves a tight budget or none at all.

The founder's error lies in collapsing both kinds into a single zero-defect standard. Then the reversible mistakes get punished as harshly as the fatal ones, and nothing ever leaves the founder's desk.

The Principle

The founders who eventually scale past themselves rarely have unusually gifted teams. They decide in advance how many first mistakes they'll pay for, instead of punishing those mistakes afterwards. The kind of founder burnout that comes from taking back every task after every stumble won't be fixed by a holiday, because it comes from missing tolerances, and a tolerance is fixed by writing down a number.

Handing over work with no margin for error is really supervision with extra steps. If your last three handovers all came back to you after one error, look at the standard you never wrote down before you look at your team.

If you want to find where this is sitting in your own company, that's what a structured diagnostic is built to do.

Pick a time that suits you.

Book a call