Blog | News, Tips & Advice

Stop Telling Founders to Delegate More

Here is an unpopular opinion. "Delegate more" is close to useless advice, and every time it gets repeated to a founder who is already drowning, it does a small amount of damage rather than none. It implies the problem is the founder's willingness to let go. In most of the businesses we see, that is not the problem at all.

The usual story goes like this. The founder holds on to too much, the team stops growing into bigger roles, and the answer is for the founder to simply trust people more and step back. It is a tidy story, and it is tidy because it is wrong. Most founders we meet are not white-knuckling control out of ego. They have tried to step back, more than once, and watched it go wrong, because there was nothing solid underneath the delegation. No documented decision rights. No written context for why things are done a certain way. No record of the judgement calls that made the business work. Stepping back into that vacuum does not feel like trust. It feels like abandoning the one system that was actually holding things together, which is the founder's own memory.

So the founder pulls it back in, the team reads that as a lack of confidence in them, and everyone quietly concludes the founder is "just like that." Nobody is wrong exactly, but nobody has identified the actual fault, which is structural, not personal.

This is the part that tends to get skipped in the standard advice. Delegation does not remove risk from a decision. It moves the risk to whoever the decision was handed to. If that person has no documented context, no clear boundary on their authority and no record of how similar calls were made before, the founder has not delegated a task. They have quietly transferred exposure to someone less equipped to carry it, and then hoped it goes well. Occasionally it does. Often it does not, and the founder's reasonable response is to take the decision back, which then gets read as an unwillingness to let go.

The signs of this are familiar even where nobody has named it:

  • a manager who technically has authority but still checks everything anyway,
  • decisions that get made twice, once by the person delegated to and once, quietly, by the founder afterwards,
  • a founder who has read every book on delegation and still cannot switch off on holiday.

None of that will be fixed by trying harder to delegate. It will be fixed by building the thing that makes delegation safe in the first place: decisions written down clearly enough that someone else can make the same call the founder would have made, without needing to ask.

That is a smaller job than most founders assume, and it is not about hiring a COO before the business is ready for one. It is about making enough of the founder's judgement visible and portable that letting go stops being a leap of faith.

There is an obvious objection here, which is that trust does matter, and building it takes time regardless of what is documented. That is true, and it is not really in tension with the point. Trust grows fastest when the person being trusted has something solid to work from, rather than being asked to guess the founder's reasoning from scratch under pressure. A manager who can see how similar decisions were handled before will make better calls sooner, and will need to be corrected less often, which is exactly what builds a founder's confidence in them in the first place. Documentation is not a substitute for trust. It is usually the fastest route to it.

If "delegate more" has never actually worked for you, that is worth paying attention to. It usually means the advice was wrong, not you.

Information icon

We need your consent to load the translations

We use a third-party service to translate the website content that may collect data about your activity. Please review the details in the privacy policy and accept the service to view the translations.