No-one sets out to be a micromanager

There are some familiar patterns that emerge during our conversations:

• they're across every detail - every email gets read twice, every report gets a line-by-line check before it goes anywhere
• they hand someone a task, then redo half of it before it goes out the door
• some things they never delegate at all, because ‘no one else really gets it’ or ‘it's easier if I just do it’
• priorities shift daily; they want to be responsive, so their team is constantly changing direction to keep up with them
• they’re the last one to leave because their own work gets pushed back to the end of the day, or into the evening, or the weekend.

Nobody thinks they’re micromanaging their team. The leaders I work with talk about ‘maintaining standards’, doing it because they ‘care’, ‘shouldering the responsibility’ that comes with leading, or being ‘too busy’ to find a different way of doing things. 

Often, their teams describe them as ‘brilliant’, ‘knowledgeable’, ‘caring’, ‘diligent’, but underneath that recognition, there are consequences.

• The program coordinator who used to flag risks early stops raising them, because last time it turned into a 40-minute deep-dive where you ended up fixing the problem yourself.
• When drafts are returned rewritten in your voice, so people stop putting real effort into a first attempt. Why bother, when it's getting redone anyway?
• Your comms officer runs every caption past you before it goes live, even though that's technically their job, because a few months ago one post got publicly picked apart.
• People start doing the safe thing rather than the right thing; they stick to exactly what you asked for, because guessing and being wrong is more costly than asking and waiting.
• Your strongest performer, the one who used to run their own caseload with confidence, starts looking for other roles, because they’re tired of being second-guessed on things they're good at.
• Monday's priority is scrapped by Wednesday because something else became ‘urgent’, so people learn not to fully commit to anything until it's survived a few days – and progress slows down as a result.
• New starters take months longer than they should to become useful, because nothing substantial ever really gets handed over - just fragments, closely supervised.

A team that's technically busy and functionally stuck, waiting to be told, protecting themselves, or heading for the door.

What’s behind this?

For many leaders, what sits behind this behaviour isn’t a lack of strategies or skills, but rather the beliefs that have powered them through their careers, and often, have been the foundation of their earlier success.

"If I'm not across it, it will go wrong." This often comes from the real experience of seeing what happens when things go off track, and being the one who caught it and fixed it. There’s a good chance you’ve enjoyed a strong reputation as a safe pair of hands. The problem begins when we generalise from "I need to check this particular high-stakes thing" to "I need to check everything, always."

"I get rewarded for getting things done, so it has to happen now." Many people step into leadership from roles where output was the measure of their worth - let’s say a focus on ‘doing’. That reward system doesn't disappear just because your title changed, but with a team doing the ‘doing’, it’s they who start to experience ‘now’ as the default speed for every request.

"I'm the only one who can get this right." This is often strongest in people who are genuinely excellent at the technical work, and who haven't yet separated ‘I do this well’ from ‘I'm the only one who could ever do this well’.

"If I could learn to do this, so should they." A belief that ignores how long it actually took you to get good at it, how much context you're carrying that they aren't, and how much support (or lack of it) shaped your own learning curve.

Each of these beliefs made sense at some point. They probably served you well as an individual contributor. They just weren't designed for leadership; they were designed for someone whose job was to produce the work rather than build the capability of a team.

Shifting the belief, not just the behaviour

Telling yourself to ‘delegate more’ without addressing the belief underneath isn’t going to result in long term change. You'll do it once, feel uneasy, and take it back. 

The real task to bring about change is in acknowledging the value of the belief that’s got you where you are today, and then expanding beyond it so that you have more choice in how you approach work, and leadership.

• From “I need to be across it or it'll go wrong" to "my job is to build a team I trust enough not to need to be across everything." We’re removing the bottleneck and creating activity that can scale.
• From "I'm rewarded for getting things done" to "I'm now rewarded for what my team gets done." The metric remains, but it's moved.
• From "I'm the only one who can get it right" to "there's more than one way to get this right, and it's my job to define what 'right' means, not to produce it myself." This one usually involves some real grief: letting go of being the expert in the room is a real loss, even when it's the right thing to do.
• From "if I could learn it, they should too" to "everyone's starting point, timeline and support needs are different, and that's something to plan around and respond to."

It’s hard work to challenge strongly held, and often unconscious, beliefs. Particularly when the changes you’re making might be happening before you really feel confident in your identity as a leader. You're being asked to let go of the identity that got you here - the person who's excellent at the work, who solves things, who's relied on to be right - before you've had a chance to build any real confidence in the new one. No wonder it feels safer to keep doing what's always worked. But a team led by someone who's still trying to be across everything will always be capped by that one person's capacity. A team led by someone who's built trust and capability keeps performing, and developing, even when that leader isn't around.

So, you’re ready to let go…

There’s a real skill to delegating effectively – it takes time, thought, and yes, leadership. Here’s how:

1. Get clear on the result before you hand it over. Not "write the funding report" but "we need a report the board can use to decide whether to keep or cut the youth program, by August 12." That's the difference between giving someone a task and telling them the outcome you’re looking for.
2. Agree how much autonomy they have, out loud. For this piece of work should they just handle it and tell you after, or check with you before acting? Don't leave that unspoken and then get frustrated when they guess wrong.
3. Set check-in points, not open access. Agree on one or two moments to look at progress, a draft at the halfway mark, a quick call before it goes external, rather than being available, or looming, the whole way through.
4. Let the first attempt be theirs, even if it's rougher than yours would be. The gap between their first draft and your best draft is where the learning happens. Rewriting it closes that gap for you, not for them.
5. Debrief after, don't rescue during. If something's heading off track, resist stepping in mid-task. Let them finish, then talk about what you'd both do differently next time. Slower, but far more durable.

A simple structure - CPQQRT, developed by organisational psychologist Elliot Jaques – can help you  hand work over properly the first time, so you're not fielding constant clarifying questions or redoing it later: Context (what's driving this), Purpose (why it matters), Quality (what ‘good’ looks like in this instance), Quantity (scope), Resources (time, budget, people they can draw on), and Time (deadline and check-in points).

Traps to watch for:

• Reverse delegation. You hand something over, they hit a snag, it boomerangs straight back to your desk because it's easier for both of you in the moment. Every time this happens, you've taught them (and yourself) that handing things back to you works.
• Delegating the task, not the authority. You give someone a project but still need to approve every decision inside it. That’s not delegation, it’s task management.
• Keeping the interesting 20%. Handing over the admin and reporting while holding onto the stakeholder meetings and the strategic calls. People notice which parts you trust them with.
• Fixing instead of coaching. "Here, let me just tweak this," said often enough, means you've done the work again, just with extra steps and someone else's name on it.
• Disappearing instead of delegating. Handing something over with no context, no access to the right people, and no idea when you're contactable is abandonment with a task attached.

Accountability without rescue

The question I hear most when leaders start to loosen their grip is some version of: “if I stop doing or checking everything, how do I make sure it still gets done properly?”.

It's a fair question, and the key is to separate two things that get tangled together: being hands-off about how the work happens, and staying completely direct about whether it met the standard. Kim Scott's Radical Candor framework calls this caring personally while challenging directly – providing feedback that's kind and specific, not vague or avoided. Leaders who default to redoing someone's work often think they're being kind. They're actually avoiding the harder, more useful act of telling the person directly what fell short and what "good" looks like instead. 

Real accountability means the natural consequence of the work stays with the person who did it, and your job is the follow-up conversation, not the rescue.

In practice, that looks like:

• agreeing the standard up front, not critiquing it after the fact (this is what CPQQRT does for you)
• letting the work land as submitted, even when it's rougher than you'd have produced yourself
• having a specific, direct conversation about what didn't meet the mark - not "this needs work" but exactly what, and what it should look like instead
• asking what they'll do differently next time, rather than telling them. A simple structure like the GROW model — Goal, Reality, Options, Will — is a useful shape for that conversation: what were they aiming for, what actually happened, what options do they see now, and what will they commit to. 

How coaching can help you

Most leaders I work with can describe their own patterns accurately within the first conversation - knowing "I should delegate more" is rarely the hard part.

The hard part is that the beliefs that underpin how we behave formed under real pressure, over years, and they don't loosen just because an article makes sense of them. Left alone, the default is to keep them, especially in your busiest, highest-stakes weeks. You try to hand something over, feel the discomfort of not being across it, and take it back. Your belief is reinforced, and nothing changes.

Here's what coaching does that reading or self-reflection doesn't:

• It gives you an outside read on your own blind spots. Most of these behaviours are invisible from the inside - they feel like diligence, not control. Someone who can name the pattern back to you, with evidence from how you're actually operating, cuts months off working it out alone.
• It builds accountability for the follow-through, not just the insight. You can have the "aha" about your reward-for-doing belief in a single conversation. Building a new habit under real deadline pressure takes structured practice, and someone checking whether you actually did it.
• It's a place to rehearse the harder conversations before you have them for real. Handing someone genuine authority, explaining to your team why you're changing how you operate, telling your board you're stepping back from the detail - these are conversations better rehearsed than improvised.

If you've read this and recognised more of yourself than you'd like to admit, that's usually the moment worth acting on — not filing away for the next quiet week that never comes.