10 November 2026 · 14 min read

Micromanagement: why good managers do it, and how to stop

Micromanagement rarely starts with someone who loves control. More often it starts with a manager who was very good at the work, and has not yet worked out how to stop doing it.

The email Hannah rewrote at eleven

Hannah was the best account manager in a company of about sixty. Six weeks ago she was promoted to lead the team she used to sit in, five people, and she has not slept well since.

On Tuesday Joe drafts a reply to a client who is unhappy about a late delivery. He sends it to her "for a quick look", because last week she asked to see anything going to that client. At eleven that night she rewrites it. Hers is better, which is the trouble. It is also nothing like his, and it goes out under his name.

On Wednesday she asks him for an update at nine, again after lunch and once more at five, because she has no idea where things stand and the client is hers on paper. She is copied on every thread. She thinks she is being supportive, and she would be hurt to hear the word micromanagement.

By Friday Joe has stopped finishing things. There is no point polishing a draft that will be rewritten. Everything now reaches Hannah half done, for a quick look, and her evenings fill up with the team's work. She concludes, reasonably from where she sits, that she cannot let go yet.

What is micromanagement?

Micromanagement is managing how someone does their work when you only needed to agree what the work is for. It shows up as checking more often than the work needs, deciding things the person could decide, and redoing work rather than saying what it lacks. It is a pattern, not a single act: one close look at a risky piece of work is management, and the same look at every piece is micromanagement.

Micromanagement or close support?

Close support is sometimes the job. A new starter's first week, work where a mistake is expensive, or someone who has asked for help all call for a manager who looks often. The difference is whether it was agreed and whether it ends. Close support has a reason both people could say out loud, and a point at which it stops. Micromanagement has neither. If you cannot say when you will stop checking, you have stopped choosing to check.

Signs of micromanagement

None of these needs a villain, and most can be seen from either chair.

• Everything arrives "for a quick look". People send work before it is finished, because finished work gets redone anyway.
• The manager is copied on every thread. Nobody asked for it, and nobody dares take them off.
• "Any updates?" comes more than once a day. Not because anything is late, but because nobody agreed when the next update was due.
• Small decisions queue up. A refund, a slide, the order of an agenda all wait for one person's yes.
• Work comes back rewritten, not commented on. The new version is often better, and all the first author learns from it is that their version was not wanted.
• Statements turn into permission. "Is it all right if I..." replaces "I'm going to...", and nobody remembers when.

Why good managers micromanage

This section is my reading rather than a finding, and it starts from a generous premise: Hannah is not enjoying this.

The handover never happened

When Hannah handed Joe the client reply, three things stayed in her head. What a good reply would do: calm the client and promise nothing new. When she would look at it: she never decided. And why it mattered so much: the client is up for renewal next month. Joe got none of the three.

Without the first, he cannot aim, so his draft is a guess. Without the second, Hannah has no moment to wait for, so she checks whenever the worry rises, which is at nine, after lunch, at five and at eleven. Without the third, Joe cannot make the call she would have made, so every call comes back to her. The checking is not a personality. It is what fills the space where the handover should have been.

The job she was good at was the work

A newly promoted lead has spent years being rewarded for doing the work well, and a few weeks being paid to get it done through other people. Rewriting the email is the one part of the new job that still feels like competence. That is what makes it so hard to stop: on a bad week it is the only part that goes well.

Trust that has not had a chance

Some of it is trust, and it runs in a circle. Hannah does not yet know what Joe can do, because she has not let him finish anything. We have written separately about the judgements trust at work rests on, and the one in play here is the plainest of them: can they do it? Micromanagement is a reliable way of never finding out. Each rewrite protects one email and costs the evidence that would have let her stop.

The circle has a second half. Joe, rewritten on Tuesday, sends worse drafts on Thursday, because a draft that will be redone is not worth his best. Hannah reads the worse drafts as proof she was right to check.

What micromanagement costs

Hannah and Joe are invented. What follows is not.

The person loses their say

HSE's Management Standards cover six key areas of work design that, if not properly managed, are associated with poor health, lower productivity and increased accident and sickness absence rates: demands, control, support, relationships, role and change (HSE, What are the Management Standards?). HSE describes control as "how much say the person has in the way they do their work". Its standard is that "employees indicate that they are able to have a say about the way they do their work", and its list includes that "where possible, employees have control over their pace of work" (HSE, Control).

HSE does not use the word micromanagement. But a manager who decides the wording, the order and the timing of every task is taking that say back, one rewrite at a time. Our guide to HSE's six areas has the early sign for control: the "how" questions stop.

How much say do people report? In the CIPD's 2026 survey, 41% of employees reported a lot of autonomy over how they do their work, 35% some, 16% a little and 7% none; over the tasks they do in their job, 21% reported a lot, 36% some, 26% a little and 17% none (CIPD, Good Work Index 2026: Survey report, July 2026, Figure 26). That measures autonomy, not who limits it: a job can be tightly specified with no micromanager near it, and the CIPD notes that autonomy is closely linked to occupation. It does show that most people report some room over how they work, which is the room a micromanager fills.

Motivation goes with it, as far as the research can say

A meta-analysis of 754 correlations across 72 studies (83 unique samples, N = 32,870) found that leader autonomy support, as employees perceived it, correlated strongly and positively with autonomous work motivation and was unrelated to controlled work motivation; it was positively associated with basic needs, well-being and positive work behaviours, and negatively associated with distress (Slemp, Kern, Patrick and Ryan, Motivation and Emotion, 2018).

The authors define leader autonomy support as "a cluster of supervisory behaviors that are theorized to facilitate self-determined motivation in employees". In plain words, and the gloss is mine: people who feel their manager backs their own way of working tend to be the people doing the work because they see the point of it, rather than because somebody is watching. The studies are correlations of what people perceived, so they do not show that loosening the reins causes any of it.

The manager pays too

Hannah pays in evenings, which she can see. She also pays in information, which she cannot. A team that sends everything for a quick look stops sending its judgement: she sees drafts, never opinions, and the person closest to the client has stopped telling her what the client is like. The team moves at the speed of her inbox.

None of this is a private matter of style. Line management, leadership, skills development and meaningful work have the biggest effect on all five business-related outcomes the CIPD measures (CIPD, Good Work Index 2026, July 2026). Two of those four are what Hannah was promoted to do.

How to stop micromanaging

None of this needs a product. Take the next piece of work you hand over, and do all four.

Agree what done looks like before the work starts

Ask yourself, then say it: "What will be true when this is done well?" For Joe's email, the client knows the new date, nothing new is promised, and the tone is one the client could forward to their own boss without wincing. If you cannot say what done looks like, you were always going to rewrite whatever came back.

Agree when you will look, then look only then

Name a time: "Show me before it goes, by three." Until three, do not ask. The anxious check at eleven was really the absence of a three o'clock. If the stakes are high, make the time earlier, not more frequent, and say why.

Give the reason, not the route

"This client renews next month, so tone matters more than speed." A reason lets someone make the call you would have made when you are not there to ask. A route ("say this, then this, then sign off like this") works only until the first thing it did not foresee, and then the question comes back to you.

Ask before you correct

When something comes back not as you would have done it, ask "what were you going for here?" before you touch it. Sometimes the answer is better than your version. When it is not, say what the draft lacks against the done you agreed, and hand it back. If it needs saying, say it about the work, once, in private. Rewrite it yourself and you both lose the lesson: you learn nothing about what Joe can do, and Joe learns only that his draft was not wanted.

The trouble with all four is the third week, when the diary fills and rewriting is quicker than explaining.

How to deal with a micromanager

If you are Joe, the most useful thing to know is that Hannah is probably anxious rather than hostile, and that the three things missing from the handover can be asked for from below.

• Ask what done looks like. "Before I start, what should a good reply do?" A manager who has said it out loud has something to judge your draft against other than their own version.
• Offer the update before it is asked for. "I'll tell you where this is at twelve and at four." A manager with a time to wait for has less reason to check. Most "any updates?" are the sound of nobody having said when.
• Ask for the reason. "What's driving the tone on this one?" Then make the next call yourself and say so: "Given the renewal, I've kept it short and promised nothing new."
• Ask for one piece of room, about the work. "Could I send the next one without a review, and we talk about how it went afterwards?" One piece of work, not a debate about trust.

None of this is managing up against anybody. It is the handover, finished from the other end, and it also tells you something: a manager who answers all three and still checks every hour has a problem the handover did not cause.

If what you are dealing with is worse than checking, hostile or personal or aimed at you alone, it is not something better updates will fix. Take it to whoever your company has named for concerns.

How MeaningFuel helps with micromanagement

The daily insight: Trust, Leadership & Coaching and Communication

A company chooses the values and skills it wants to work on, and each working day everyone gets one short insight on one of them, drawn from something a real person said. Micromanagement is a problem, and a problem cannot be chosen for the daily culture: that is what a module is for. What a company can choose is what micromanagement wears away: Trust as a value, and Leadership & Coaching and Communication as skills. In an ordinary week that might put a line on letting people finish in front of Hannah on a Tuesday. It will not stop the eleven o'clock rewrite; it keeps the idea in the week where the rewrite happens.

The module: Clear Direction

MeaningFuel has no module called micromanagement. The nearest is Clear Direction, because most micromanagement, as this piece describes it, is direction that never landed. A module is a short course of ten daily lessons across two working weeks. Booked for a team, it invites the people on it, and those who join get one lesson each working day.

It practises both ends of the handover. The team learns to ask for the target, "what does done look like?", and to say direction back in its own words. The lead practises the five questions of Mike Rother's Coaching Kata, a routine widely used in continuous-improvement work. One lesson starts where Hannah's Wednesday did: many check-ins open with "any updates?", and nobody leaves clearer on whether the work is nearer to done. The five questions take its place: the target, where things actually are, the obstacles, the next step, and when to look again. That last one is the three o'clock. Another lesson is a short note each week with the priority and the reason for it, so people can decide well when the plan stops fitting and the lead is not there to ask. It draws on research by Amy Edmondson on psychological safety, the shared belief that it is safe to speak up: people ask for clarity more readily when asking feels safe.

What leaders read, and what they cannot

Insights shows how much of a team takes part and how the insights land, pooled, with nobody named. It is not a reading of micromanagement, and nothing in it shows whose email was rewritten at eleven. During a module the lead sees whether the team is doing it, and never anyone's answers or what they write. If Hannah wants to know how her checking lands, she still has to ask Joe.

What it does not do

Neither the insight nor the module hands a piece of work over for a manager. The module turns the done-question, the agreed time to look and the stated reason into habits a team keeps on a schedule, so they do not depend on one good Monday. It promises no result, and it will not take the pen out of Hannah's hand at eleven. Putting it down is still hers to do.

Questions managers ask about micromanagement

How do I know if I am micromanaging?

Count what reaches you unfinished. If most of your team's work arrives "for a quick look", or your evenings hold work you asked someone else to do, you are probably micromanaging. A second test takes five minutes: ask two people what done looks like for their main task this week. If they cannot say, the checking is filling a gap you left.

What do I say to a micromanager?

Ask for what the handover left out, rather than for less attention. "What should a good version of this do?", "When would you like to see it?" and "What's driving the deadline?" each give a manager something to rely on other than checking. Then offer the update before it is asked for, at a time you both agreed, and keep to it.

How long does it take to stop micromanaging?

Nobody has a reliable figure for that, and a number quoted for it is a guess. What you can change is smaller: the next handover. Agree what done looks like, a time to look and the reason on the next piece of work, keep to the time, and do it again on the one after. The habit is built from handovers, not from deciding to trust more.

Back to eleven o'clock

Hannah's rewrite made a better email and a worse week. The fix is three sentences on Tuesday morning: what a good reply does, when she will see it, and why this client matters. Then comes the hardest part of the job she was promoted into: at eleven, closing the laptop.

• Micromanagement
• Delegation
• Managing Teams
• Trust
• Workplace Culture