Skip to content
GuideEntrepreneurship6 min

Delegating without losing control: a founder's guide

Handing work over without it coming back wrong or everything landing on you again: what to delegate first, how to brief it, levels of authority and how to check.

Share on WhatsApp
Two adults use a practical guide, checklist cards and a recorded workshop to support their learning

Conceptual image · created with AI

Most founders say they delegate. Many redo the work, answer every question themselves or take the decision back at the last minute. Others hand over a task with a single line, then are annoyed when it comes back wrong. Both feel like delegation not working, and both are fixable.

Delegation is a skill, and nobody teaches it. The good news is that it comes down to a few habits: choosing the right task, being clear about the result and the limits of authority, agreeing how you will check and responding well to the first imperfect attempt.

What you should come away with

  • Start with tasks that are repeated, clear and low in risk
  • Brief the outcome, not just the steps, and ask the person to say it back
  • State how much authority comes with the task, from 'tell me first' to 'just do it'
  • Agree the check-in dates before the work begins, so checking is not hovering
  • Separate work that is wrong from work that is merely different from how you would do it
  • Delegate the task and the decision together, or it has not really moved

Begin with an honest list. Write down everything you did last week and the time each thing took. Mark each item: only I can do this, I could teach this, or somebody else would do it better. Most founders find that a surprising share of their week falls into the second and third groups. The list also shows work you repeat every week or month with the same steps, which is the easiest to hand over.

It helps to recognise why you hold on. Common reasons are that it is faster to do it yourself, that nobody will be as careful as you, that people are already busy, that you enjoy the task, or that you were let down once and stopped trying. None of these is silly. But each has a cost. If it is faster for you every time, you will never have time for anything else. And if one bad experience ended your delegating, the real lesson may be that the brief was unclear, not that nobody can be trusted.

Choose the first tasks carefully. Good candidates are work that is repeated, work that follows steps, work where a mistake would be noticed and could be corrected, and work somebody on the team wants to learn. Keep for now the decisions that put the business at risk: pricing, key customer relationships, hiring and firing, and anything involving large sums of money. Delegation is gradual, and the aim is to widen what you hand over as trust is built.

Then brief the task properly. A good brief takes ten minutes and saves days. Say what outcome you want and why it matters, who it is for, and what good looks like, ideally with an example. Give the deadline and say what is flexible about it. Say what the person may decide alone and what they must check with you. Tell them where to find what they need and who can help. Finally, ask them to say the brief back in their own words. That one step catches most misunderstandings before they cost anything.

Be explicit about how much authority comes with the task. A simple scale of four levels works well. At level one, the person looks into the matter and tells you what they found. At level two, they recommend what to do and you decide. At level three, they do it and then tell you what they did. At level four, they do it and tell you only if something is unusual. A new task usually starts at level one or two. As the person proves reliable, you move it up. Saying the level aloud removes a great deal of confusion about who is allowed to decide what.

Agree how you will check before the work starts. The difference between checking and hovering is that checking is planned and shared. Pick a date for an early look at a first draft, well before the deadline, when changes are still cheap. Ask for a short written update at a regular time each week. Keep a simple shared list of who is doing what, by when. When you have agreed this in advance, you do not need to ask 'how is it going?' ten times a day, and the person does not feel watched.

Expect the first result to be different from what you would have done. This is the moment delegation usually fails, because the founder takes the work back. Ask yourself first: is it wrong, or is it just different? If it meets the outcome, let the difference go. If it falls short, say what is good about it, honestly, then explain the gap in terms of the result, not the method. Let the person fix it. Afterwards, ask what in your brief would have made it clearer. Often the answer improves every brief you write after that.

Watch for the habits that quietly undo a handover. Doing the task yourself at the last minute. Answering every question instead of asking 'what would you do?' Changing the deadline or the goal without telling the person. Handing over the task but keeping the decisions. Each teaches the team that the task was never really theirs, and a team that learns this stops taking initiative.

Finally, plan for your own absence. Write short checklists for tasks that repeat, so the knowledge is not only in your head. Make a list of decisions the team may take without you. Name one person who can step in on each key task. Then try one working week in which you answer only what is truly needed, and see what happens. What goes wrong shows what still needs writing down. What goes right shows what you can safely let go of.

Delegation done well does not mean losing control. It means moving your control from doing the work to setting the outcome, the limits and the checks, which is the part only the founder can do.

TopicsHuman ResourcesLeadership

Come to the session it came from

Reading it is useful. Being in the room and asking your own question is better.