Delegation is one of those pieces of advice that sounds obvious until you try to do it properly.
“Stop doing everything yourself” is easy to say. The difficult part is deciding what someone else should genuinely own, what context they need, how much authority moves with the work, and when the founder should still be involved.
A lot of businesses get only halfway there. The task moves. The judgement does not.
Someone else prepares the report, speaks to the supplier or runs the project, but the meaningful choices still come back to the same person. The founder becomes the approval queue for a business that is supposedly becoming less dependent on them.
That is usually where delegation starts to feel disappointing.
The task is rarely the real thing being delegated
There is a big difference between giving somebody an activity and giving them an outcome.
“Send the weekly report” is an activity. It can be completed perfectly without improving anything.
“Make sure leadership has a reliable view of delivery risk every Monday” is different. Now the person has room to ask whether the report is useful at all. They can change the format, automate part of the data collection, remove noise or surface a risk that the old version missed.
The second version requires judgement. It also creates ownership.
That is the point.
When the outcome is clear, the person doing the work can improve the way the work is done instead of simply reproducing the founder’s habits.
Context is part of the job
Founders carry an enormous amount of unwritten context.
They know which customer matters for reasons that do not appear in the CRM. They remember why a seemingly sensible option was rejected six months ago. They know which risk is acceptable and which one is not. They understand the history behind a pricing decision that looks strange when viewed in isolation.
None of that automatically transfers with the task.
This is why “I delegated it and they got it wrong” can be a misleading diagnosis. Sometimes the person made a poor decision. Sometimes they were asked to make a good decision using only half of the information.
Good delegation therefore includes the awkward, messy context as well as the clean brief.
It does not mean writing a book before every handover. It means sharing the information that changes the decision.
Authority has to move with responsibility
This is where many delegation attempts quietly collapse.
A manager is told they own an outcome, then discovers they cannot approve a modest spend, adjust the process, reject a bad request or make an exception without asking permission.
The role looks autonomous on the organisation chart. In practice, it is not.
If somebody owns the result, they need enough authority to influence the result.
That does not mean unlimited freedom. It means agreed boundaries.
Perhaps spending above a certain amount needs escalation. Perhaps a customer concession beyond a defined threshold needs approval. Perhaps a hiring decision requires another pair of eyes.
Those limits are useful because they tell people where their judgement begins and where it ends.
Without them, people either escalate everything or guess.
Neither scales particularly well.
Different does not mean wrong
One of the harder parts of delegation is accepting that another capable person may not make the same decision you would.
They may structure the meeting differently. They may choose a different supplier. They may solve the problem in a way that feels unfamiliar.
That can be uncomfortable, especially when the founder has spent years building the instincts that shaped the business.
But if the outcome is good, the principles have been respected and the risk is acceptable, difference is not failure.
If every delegated decision must still look exactly like the founder’s decision, then the business has created imitation rather than ownership.
The standard should be clear enough to protect the organisation, but not so narrow that nobody else can exercise judgement.
Visibility is not the same as control
Founders still need to know what is happening.
That is reasonable.
The mistake is assuming that visibility requires involvement in every decision.
A better system makes the important things visible without pulling the founder back into the workflow. A short operating rhythm, a small number of useful measures and clear exception reporting can do far more than endless approvals.
The founder should be able to see where something is going wrong without becoming the mechanism that makes everything go right.
That distinction matters.
Once information can travel upward without authority travelling back down every time, the organisation begins to behave differently.
Delegation is a test of the management system
If delegation repeatedly fails, the individual is not always the problem.
The business may have unclear roles. Information may be difficult to find. Decision rights may never have been defined. Managers may have responsibility without the systems needed to exercise it.
Delegation exposes those weaknesses because it removes the founder as the universal workaround.
That can feel uncomfortable, but it is useful.
It shows whether the organisation has actually built management capability or whether it has simply built more activity around one central decision maker.
The goal is not to make the founder less busy
Reduced workload can be a welcome consequence, but it is not the most important outcome.
The real gain is that more people become capable of making sound decisions without waiting for the founder.
That creates speed, but more importantly it creates depth.
A business with one good decision maker is fragile. A business with several people who understand the context, know their authority and can own outcomes has much more room to grow.
That is what delegation is for.
Not getting tasks off a desk.
Building an organisation that can carry responsibility beyond the person who started it.