APEX Business Growth · Insights
The delegation trap
Why handing things off keeps failing, and what to fix before you try again
You handed client reporting to your account manager three months ago. Last week a report went out with the wrong figures, a client emailed you directly, and by Friday you were rewriting it yourself at eleven at night. Now the task is back on your plate, and you have quietly decided it is easier to keep it there. You have made this decision before.
Why owners take things back
Almost every agency owner has tried to delegate and watched it unravel. The usual conclusion is about people: the hire was not senior enough, the team does not care as much, nobody does it quite the way you would. Sometimes that is true. Far more often, the problem sits underneath the person.
Delegation, as most owners practise it, means passing a task across with a short brief and a hope. The knowledge of how the task should be done, what good looks like and what to do when something unexpected happens stays in the owner’s head. The team member receives the work without the structure that makes the work possible.
When the first problem appears, there is nowhere for it to go except back to you. You fix it, because you can and because the client matters. The team member learns that the real decisions still belong to the owner. You learn that delegation does not work. Both conclusions are reasonable, and both are wrong.
Delegation is the last step, not the first
In the APEX build sequence, team management and delegation come sixth, after financial reporting, vision and identity, annual planning, operational systems and organisational structure. That order is deliberate. Delegation is what becomes possible once the foundation exists. Attempted earlier, it simply moves the bottleneck from one desk to another and then back again.
Each earlier layer removes a reason the work returns. Clear financial reporting lets a team member see whether a decision is affordable without asking. A defined vision and identity tell them which clients and which standards the business stands for. An annual plan tells them what matters this quarter. Documented systems tell them how the work is done. A clear structure tells them who owns what, and who they answer to when something goes wrong.
Without those layers, you are not delegating a task. You are delegating a guess about what you would have done, and asking someone else to carry the risk of guessing wrong.
What to build before you let go again
The good news is that the structure required is not mysterious. For any responsibility you intend to hand off, a few things need to exist in writing, outside your head:
- a clear outcome, described as a result rather than a list of activities
- a documented process for the routine parts of the work
- the decision boundaries: what the person can decide alone, and what needs a conversation
- a simple measure that shows whether the work is on track, visible to both of you
The third item is where most hand-offs break. When nobody has said where the person’s authority ends, they either escalate everything or overreach on something important. Both send the work back to you.
The fourth item replaces checking in. When progress is visible, you no longer need to hover, and the team member no longer needs to wonder whether you are quietly unhappy.
Letting go without losing control
Owners often fear that real delegation means losing sight of quality. In practice, structured delegation gives you more visibility, not less. You stop relying on memory and impression, and start relying on agreed outcomes and shared measures.
It also changes the first mistake. When a report goes out wrong under a clear system, the question is no longer who to blame or whether to take the task back. The question becomes which part of the structure was missing, and that part can be fixed once, for everyone. Each correction strengthens the foundation instead of pulling the work back to the top.
This is the shift from operator to leader. Your value moves from doing the work well to building the conditions in which others do it well. That shift is uncomfortable at first, because the results are less immediate and less visible than finishing the task yourself. It is also the only path that leads out of the seventy-hour week.
The delegation trap is not a failure of trust or talent. It is what happens when work is handed over without the structure that makes ownership possible. Build the outcome, the process, the boundaries and the measure first, and the hand-off stops looping back. The work stays where you placed it, and your time returns to the decisions only you should be making.