How to Delegate Without Micromanaging

Why founders end up micromanaging

Most micromanagement in small businesses does not come from a controlling personality. It comes from handing over a task without handing over enough information to do it well, then feeling compelled to fill the gap by checking in constantly. The founder knows what 'good' looks like because it lives in their head, but they have not written it down, so the person doing the work is guessing — and the founder can tell they are guessing.

The second common cause is unclear authority. If nobody has told an employee whether they can approve a £40 refund or reply to a difficult customer without checking first, they will either freeze and ask about everything, or act and get it wrong once, after which the founder trusts them less and starts double-checking everything. Both patterns look like micromanagement from the outside, but they start with a gap in the brief, not a lack of trust.

The fix is not a personality change or a resolution to 'let go more'. It is building three things into how you hand over work every time: a written outcome, a stated authority level, and an agreed check-in point. Once those three things exist, most of the anxious checking-in stops on its own, because you already know when you'll next see the work.

Write the brief before you hand anything over

A delegation brief does not need to be long, but it needs to answer four questions before the person starts: what does 'done' look like, what constraints apply, what can they decide without asking, and when will you next look at it. Skipping any one of these is what forces you back into hovering, because you will find yourself wanting to check the thing you didn't specify.

Write the outcome as a result, not a list of steps. 'Customers who email support get a reply within four working hours, in our tone of voice, with the issue actually resolved' is an outcome. 'Reply to emails' is not — it tells the person nothing about the standard you're holding them to, so they cannot self-check their own work, and you will end up doing it for them.

• Outcome: what result are you actually paying for, stated as an end state, not a task
• Definition of done: what a reviewer (you, or eventually them) would check to confirm it's finished properly
• Constraints: budget limits, brand or tone rules, legal or safety boundaries that can't be crossed
• Authority: what they can decide alone, what needs a quick check, what needs your sign-off
• Deadline: a specific date, not 'soon' or 'when you get a chance'
• Review point: exactly when you will look at progress — a date and a format, not 'I'll check in'

If you can't write the definition of done in one sentence, you're not ready to delegate the task yet — you need to define it first.

The delegation ladder: matching authority to task

Not every task deserves the same level of independence, and treating them all the same is a common source of friction. A useful way to think about this is a ladder of five authority levels, moving from tightly controlled to fully independent. Naming the level explicitly, out loud or in writing, removes the guesswork that otherwise gets filled with either excessive checking-in or unwelcome surprises.

Most founders start everyone at level one or two for a new task, then move up a rung once the person has demonstrated they understand the standard. The mistake is leaving someone at level one indefinitely out of habit, which reads as a lack of trust even when that isn't intended, and it caps how much you can actually take off your plate.

1. Level 1 — Do exactly this: follow the steps precisely, no judgement calls, report back when done
2. Level 2 — Do this, ask before deciding: attempt the task but check with you before any judgement call
3. Level 3 — Do this, tell me what you decided: act on their judgement, then report what they did and why
4. Level 4 — Do this, tell me if something goes wrong: full autonomy, only flag exceptions or problems
5. Level 5 — Decide and act, tell me periodically: complete ownership, reviewed on a set schedule, not per task

What to say in the handover conversation

The words you use when you hand something over set the tone for how much you'll need to intervene later. Avoid vague phrases like 'just have a go and let me know how it goes' — they sound relaxed but actually create anxiety, because the person has no way to judge whether they're on track. Instead, be specific and say the review point out loud so it's on both your minds.

A workable script: 'I want you to own replying to customer emails from Monday. Done well means every email gets a reply within four hours in our tone, and the issue is actually fixed, not just acknowledged. You can offer refunds up to £30 without checking with me — anything above that, flag it to me first. I'll read through a sample of your replies on Friday afternoon and we'll talk through anything that needs adjusting. If anything urgent comes up before then, message me.'

Notice what that script does: it states the outcome, the definition of done, the authority limit, and the exact review point, all in under 90 seconds. It also gives an escape valve for genuine urgency, which prevents the person from either sitting on a real problem or interrupting you constantly for small ones.

Holding the line during the review point, not before it

The hardest part of delegating without micromanaging is not the handover — it's the days in between, when you notice something you'd have done differently and feel the pull to step in immediately. Unless it breaches a stated constraint (budget, safety, legal, brand), the discipline is to note it and raise it at the agreed review point, not interrupt the moment you spot it.

This matters because interrupting mid-task teaches the person that the review point is meaningless and that you'll intervene whenever you feel like it, which pushes them back towards asking permission for everything — the opposite of what you're trying to build. Keep a short private note of things to raise at the review point rather than acting on each one as it occurs to you.

If something does breach a hard constraint — money, safety, a legal requirement, a promise to a client — step in immediately and say clearly why this one is different from the small stuff you're deliberately leaving alone. That distinction, made explicit, actually builds trust rather than eroding it.

Running the review point well

A review point is not a test with a pass or fail mark; it is a working conversation about what to keep doing, what to adjust, and what authority level to move to next. Start by asking them how they think it went before you give your own view — this surfaces their judgement, which is exactly what you're trying to develop, and it tells you a great deal about where the gaps in understanding actually are.

Keep a simple three-part structure: what worked and should continue unchanged, what needs adjusting and why, and what the plan is until the next review point. Write down anything you agree to change in the brief itself, so the next handover starts from an improved version rather than repeating the same gaps.

• Ask their own assessment first, before giving yours
• Name specifically what met the standard, not just 'good job'
• Name specifically what needs to change and what 'better' looks like
• Agree whether the authority level moves up, stays, or (rarely) moves back down
• Set the next review point before the conversation ends

Diagnosing why a handover isn't working

When delegation goes wrong, it's tempting to conclude the person isn't capable, but in a small team that's rarely the whole story. Work back through the brief first: was the outcome actually clear, was the authority level realistic for their experience, and was the review point close enough together for someone new to the task? Most failed delegations trace back to one of these three, not to the person's ability.

A genuinely useful diagnostic is to ask what decision they got stuck on. If they say they didn't know whether they were allowed to do something, that's an authority gap, and the fix is a clearer brief next time. If they say they didn't understand what 'good' looked like, that's a definition-of-done gap. Only if neither of those applies, and the standard is still not being met after a fair run, are you looking at a genuine skills or fit problem.

Common mistakes that keep founders stuck micromanaging

A handful of habits reliably drag founders back into hovering even after they've read all the advice about letting go. Recognising them in yourself is more useful than resolving in the abstract to 'trust more'.

• Redoing the work yourself after the review instead of coaching the person to redo it
• Changing the brief halfway through without telling the person, then judging them against the new version
• Delegating the task but not the authority that goes with it, so every decision still routes back to you
• Reviewing more often than agreed 'just to check', which trains the person to expect interruption
• Delegating everything at once rather than one task at a time while the ladder approach is new to both of you
• Never revisiting the authority level, so someone who's proven themselves for months is still on level one

Week one: what to actually delegate first

Start with a task that is frequent, well-understood by you, and low-to-moderate risk if it's done imperfectly — this gives you and the other person several repetitions to calibrate quickly, rather than one high-stakes attempt with no room to adjust. Customer email replies, routine supplier ordering, or a recurring report are typical starting points in a small business.

Avoid starting with the task that is highest-stakes or most emotionally attached to you, even if it's the one taking the most of your time. You will find it hardest to resist intervening on exactly that task, which undermines the whole approach before it's had a chance to work. Build the habit on something smaller first, then move up.