Micromanagement: 15 examples and how to deal with a micromanaging boss
What micromanagement looks like, why it happens and what to do about it, from either side of the desk. With scripts and templates you can copy.

If you are trying to work out how to deal with a micromanaging boss, start here: most micromanagers aren’t villains. They are usually anxious, under pressure or unsure what good looks like, and that is something you can work with. This guide covers what micromanagement is, 15 examples you will recognize, a 12-question self-check for managers, eight steps and three scripts for employees, and a delegation system for managers who want to let go.
What is micromanagement?
Micromanagement is managing the how of someone’s work instead of the what: the steps, the wording, the timing, the order. A micromanager agrees an outcome and then can’t leave the route to it alone. The result is slower work, people who stop thinking for themselves and a manager with no time for their own job.
Not all close management is micromanagement. A new hire, a high-stakes launch or someone on a performance plan may need more contact for a while. The difference is whether the closeness is explained, temporary and aimed at helping the person stand on their own.
| Close support | Micromanagement | |
|---|---|---|
| Why | Explained: new role, high stakes, a skill gap | Unexplained, or "that's how I work" |
| How long | Temporary, with an end in sight | Permanent, whatever the track record |
| Focus | Outcomes and the skills to reach them | Steps, wording and activity |
| Goal | The person needs the manager less over time | The manager stays in every decision |
15 micromanagement examples
Each of these micromanaging examples is common on its own now and then. When several are the normal way of working, that's micromanagement.
- Rewriting emails before they go out. Every client email needs the manager's edits first, even routine replies you have sent a hundred times.
- Asking to be copied on everything. The manager wants a cc on every thread, then replies to threads you were handling.
- Approval for decisions inside your job. You need a sign-off to order a cheap tool or move a meeting, though both are clearly your call.
- Daily reports on weekly work. A task due Friday comes with a request for a written status update every evening.
- Redoing finished work without saying why. You hand in a report and it comes back rebuilt, with no note on what was wrong.
- Dictating the how, not just the what. Instead of the goal, you get step-by-step instructions, down to which spreadsheet columns to use.
- Checking in several times a day. "How's it going?" arrives at 9, 11, 2 and 4 on a project that isn't due until next week.
- Watching activity instead of results. The manager notices when your status dot turns yellow and asks where you were.
- Joining every meeting you run. Your boss sits in on your client calls and team meetings, and answers questions that were addressed to you.
- Fixing small preferences on internal documents. Notes meant for three colleagues come back with font changes and reworded headings.
- Being the only path to other people. You aren't allowed to email another team or a senior leader directly; everything goes through your manager.
- Taking over when the work gets visible. You do the project, and the manager steps in to present it or finish it the week it reaches leadership.
- Accounting for every hour. Salaried work comes with a log of what you did in each half hour, reviewed line by line.
- Handing out tasks without the bigger picture. You get small pieces of a project with no context, so only the manager knows how they fit together.
- Expecting instant replies. A message unanswered for ten minutes is followed by a second message, then a call.
Micromanaging is one of several management habits that wear a team down. Our guide to the signs of a bad manager covers the rest, and when the checking comes with fear and threats, it may be part of a toxic work environment.
12 signs you might be a micromanager
For managers. Answer yes or no, honestly. Most managers say yes to a couple; if you say yes to four or more, the rest of this guide is for you.
- Do you feel uneasy when you don't know exactly what each person is working on right now?
- Do you redo work yourself more often than you send it back with notes?
- Does your team ask permission for things they could decide on their own?
- Are you copied on most of your team's emails?
- Do projects slow down or stop when you are on vacation?
- Are you busy all day but rarely get to your own priorities?
- Do you explain how to do a task more than what the result should be?
- Have people stopped suggesting ideas in your meetings?
- Do you review work before it is finished, unasked?
- Do you ask for updates more often than the work actually changes?
- Have your strongest people seemed restless, or left?
- Do you think "it's faster if I do it myself" at least once a week?
Why managers micromanage
Understanding the reason doesn't excuse the behavior, but it tells you which fix will work.
- Fear of failure. The manager is under pressure from their own boss and checks everything so nothing reaches them as a surprise.
- Unclear standards. If "good" was never defined, the only way the manager can get what they picture is to control every step.
- New to managing. People promoted for being great at the work often keep doing it, and doing it through other people's hands feels like the closest thing.
- A past burn. One project that went badly when they let go can make a manager hold on tight for years.
- Not enough visibility. On remote teams, a manager who can't see the work being done may start watching activity instead.
- They were managed that way. Many people copy the only management style they have experienced up close.
How to deal with a micromanaging boss: 8 steps
If you are micromanaged at work, start with the steps that cost nothing and change the most. The direct conversation comes later, once you have shown you can be trusted with more room.
- Work out where it comes from. Is your boss new, under pressure from above, or reacting to a recent mistake? The cause tells you which fix will work.
- Update them before they ask. A short written update on a rhythm you propose answers most check-ins before they happen. A template is below.
- Agree what "done" looks like at the start. Ask about format, level of detail and deadline up front, so there is less to correct at the end.
- Match the preferences that cost you little. If they like bullet points or a certain report layout, give it to them. Save your pushback for the things that matter.
- Build trust with small, visible wins. Deliver a few things on time with no surprises. Each one makes the next request for room easier.
- Propose a check-in rhythm. Offer one short weekly meeting or two written updates in place of ad hoc pings, and keep to it without fail.
- Have the direct conversation. If it continues, name one specific behavior and its effect on your work, and ask for one change. Scripts are below.
- Escalate or plan your exit. If nothing changes after a few months, talk to your manager's manager or HR with specific examples, or start looking quietly for a better fit.
A short update template
Send it on the rhythm you agreed, even when there is little to report. Predictable updates are what make a nervous manager stop checking.
Project update
Update on [project], [date] Done since last update: Next up, with dates: Risks or blockers: What I need from you:
Three conversation scripts
Fill in the brackets and say it in your own words. Each one asks for a change while offering your boss something they want: visibility, or less work.
Propose an update rhythm
I want to make sure you always know where [project] stands. Would it work if I send you a short update every [Tuesday and Thursday] with progress, risks and anything I need from you? That way you won't need to chase me, and I can keep my head down on the work.
Ask for ownership of one task
I'd like to take full ownership of [task]. Here's my plan and the dates I'll hit. Could we agree on two points where you review it, at [milestone] and before it goes out, and leave the rest to me?
Name the pattern
Can I share something that would help me do better work? When [you rewrite my emails before they go out], I'm not sure what I got wrong, and I start second-guessing everything. Could you tell me what you would change instead, so I can get it right the first time and you can spend less time on it?
How to stop micromanaging
Letting go is a skill, not a personality change. These seven habits replace checking with clear agreements.
- Define the outcome, not the method. Say what done looks like and why it matters. If the result is right, the method belongs to the person doing it.
- Agree a decision level for each task. Use the five levels below so both of you know what they can decide alone.
- Set the check-ins up front. New task and high stakes: twice a week. Familiar work: once a week. Proven expert: at milestones only. Then don't add unplanned ones.
- Ask questions instead of fixing. "What would you change if you had another day?" teaches more than your rewrite does, and keeps ownership where it belongs.
- Review results, not drafts. Unless they ask for an early look, wait for the finished piece and give one round of specific feedback.
- Let small mistakes happen. Step in for anything that would hurt a customer or the business. Let the rest become lessons.
- Use the time you get back. Put it into the work only you can do: direction, removing blockers and developing your people.
Five levels of delegation
Say the level out loud when you hand over a task. Most micromanagement is a manager acting at level 1 when the person is ready for level 4.
| Level | What you say | Use it for |
|---|---|---|
| 1 | Look into it and report back. I decide. | Brand-new tasks or people |
| 2 | Bring me options and your recommendation. I decide. | Decisions with real risk |
| 3 | Decide, then tell me before you act. | Growing experience |
| 4 | Decide and act, then tell me what you did. | Familiar work |
| 5 | Decide and act. No need to report back. | Proven people, routine calls |

A delegation template
Fill it in together when you hand over anything bigger than a day’s work. If you can’t fill in “what done looks like”, the task isn’t ready to delegate yet.
Delegation brief
Task: Why it matters: What done looks like: Deadline: Decision level (1 to 5): Budget or limits: Check-ins (when, and in what form): Who else to involve: Where to get help if stuck:
Trust grows in both directions once people deliver on their own. Our guide to building trust in the workplace has more habits for that, and how to give constructive feedback helps you give one useful round of notes instead of a rewrite. For the bigger picture of what to do instead, see the qualities of a good leader.
Remote micromanagement
Distance makes it worse: a manager who can't see the work starts watching activity instead. Each habit has a better replacement.
| Instead of | Try |
|---|---|
| Monitoring software that tracks clicks or screenshots | Weekly outcomes agreed in advance and checked on Friday |
| Watching status dots | Core hours for overlap, and freedom outside them |
| Pings every hour | One written update at an agreed time |
| Cameras on for every call, all day | Cameras for team meetings, optional for focus work |
| Instant-reply expectations | Agreed reply times by channel, with a phone call for real emergencies |
The test is simple: would you be happy if your team judged you by your status dot? Judge them by their results, and make sure everyone knows what those results are.
Leadership workshops for your managers
For managers who want to lead without doing everything themselves, see our leadership team building. Book about 2 weeks ahead, or get a free quote.
Two live workshops on Zoom by default: one on setting goals and getting past self-doubt, one on moving from doing it all yourself to building a team that has your back.
