How to work with a micromanager

Your manager wants to see the deck before you send it, asks how it's going the same afternoon you started, and rewrites your email to a customer you've been talking to for a year. You've started routing around them, which they can tell, so now they check more.

This article covers what's usually driving the behavior, and how to tell an anxious manager from one who has a real concern about your work. It also covers the updates that pre-empt the check-ins, and how to agree on what needs approval and what doesn't. Read the section on diagnosing it first, because the fix for a nervous manager and the fix for one who has been told to watch you are completely different.

The advice here comes from Molly Graham, who led teams at Google, Facebook, and Quip and now coaches leaders through fast growth; Wes Kao, co-founder of Maven and the altMBA, whose most-shared writing is about managing up; Claire Hughes Johnson, chief operating officer at Stripe from about 160 people to several thousand; Kim Scott, author of Radical Candor; Ravi Mehta, former chief product officer at Tinder; Ethan Evans, who spent over fifteen years at Amazon and retired as a vice president; and the Mochary Method, the coaching curriculum Matt Mochary uses with startup CEOs. We've also written the manager's side of this, in our guide to delegating without micromanaging, and a lot of what follows comes from knowing what your manager is being told to do.

Why your manager keeps checking on you

Almost nobody sets out to micromanage. What happens is that a manager hands over work they used to do themselves, and handing it over feels like a loss.

Molly Graham has the phrase most managers now use for this. She describes joining a fast-growing company as being handed a giant pile of Legos and told to build something. You build a house, you get good at building houses, and then someone tells you it's actually a neighborhood, hands your half-built house to a new hire, and asks you to go build dog parks.

Graham has been doing this for close to twenty years and says the feelings still hit her. When your manager is standing over your work, you're the new hire who just got handed the half-built house. Most of the time the hovering is about what they gave up rather than about what they think of you.

The second driver is that they're accountable for something they can no longer see. Your manager has a number they have to answer for, and once you own the work that moves it, their only view of it is whatever you tell them. If you tell them very little, they'll go looking. Most of what people call micromanagement is a manager filling an information gap in the most annoying way available.

None of this makes it fine. It just means the lever you have is bigger than it looks, because a lot of the behavior responds to information rather than to argument.

Work out which kind you're dealing with

There are roughly three reasons a manager checks on you constantly, and they need different responses. Guessing wrong wastes months.

The third one is the one people miss. A manager's own boss tells them to watch a team more closely after a customer complains, after an audit, or once HR starts documenting a performance concern. Your manager may not be allowed to tell you which of those it is, but they can usually tell you that something changed if you ask them directly.

There's a fourth possibility worth knowing about, because your manager may have been taught it deliberately. Ravi Mehta, who was chief product officer at Tinder and a product director at Facebook, coaches leaders to get temporarily hands-on when they don't like the direction a team is heading.

Mehta's test for whether it's working is that the close supervision gets replaced by a shared way of making the decision, so the manager can back off. That gives you a question to ask: what would you need to see before you stop reviewing these? Someone doing this deliberately will have an answer ready, and someone who's just anxious usually won't, which tells you something either way.

Before you go and ask, do a pass on your own part in it. Claire Hughes Johnson puts self-knowledge at the front of everything else in management, and it applies just as much from below.

The honest questions are: how often do they hear from me without asking, do they find out about problems from me or from someone else, and have I missed a date recently without flagging it early. If any of those is bad, some of the checking is a response to how you've been communicating, and that part is yours to fix.

Ask your manager what they're worried about

The conversation most people have goes badly because it's an accusation with a question mark on the end. "Do you not trust me?" gives your manager exactly one safe answer, and it isn't a useful one.

Ask about the risk instead. Managers can talk about risk all day, and the answer tells you which of the three situations you're in.

The Mochary Method has a format for raising something like this in a 1:1 that keeps it from turning into a complaint. You write down the issue, then what you did to help create the situation, then a proposed solution with specific actions and dates. The middle section is the one that does the work. If you can name your own contribution, you usually find a fix that doesn't depend on your manager changing first. Send it a day ahead so they can think about it rather than react in the meeting.

Then be ready for the answer to be about expectations rather than about trust. Molly Graham's rule for diagnosing anything on a team is to check the boring structural stuff before you conclude anything about the people.

Graham says she's taken over a lot of teams, and almost every time she arrives, nobody knows what their job is and nobody knows what success looks like. She runs the conversation from both sides: here's what I'm seeing, now tell me what you think your job is and what number you were hired to move. Run it from your side too. Say what you believe you own and what you think success looks like, and watch whether your manager's version matches. A lot of hovering turns out to be two people with different pictures of the same job.

Send the update before they ask for it

This changes more than anything else on the list, and people skip it because it feels like extra work for a problem someone else created.

Wes Kao's argument is that the people who are best at this are the senior ones, which is part of how they got senior.

Kao also says most people assume their boss is supposed to manage them, and resent having to manage in the other direction. You can keep thinking that and your career will probably be fine. But if you manage up, you get more trust and more opportunities, and in this specific case you get left alone.

In the same conversation, Lenny Rachitsky describes what he sent his own manager every week: an email titled "the state of Lenny", with three sections. His current priorities, the blockers he needed help with, and whatever was on his mind that week. He put the blockers near the top so they'd actually get read.

Propose the cadence yourself rather than waiting to be handed one. A schedule you suggested is much harder for your manager to add to, and much easier for you to point back to when they ask for something outside it.

Two rules make this work. Send it on the same day every week without fail, because a cadence that's sometimes there is worse than no cadence. And put the bad news in it. An update that's only good news trains your manager to go looking for the rest, which is the exact behavior you're trying to stop. Our guide to writing a concise status update covers the format in more depth.

Agree on what needs approval and what doesn't

Updates close the information gap, but they leave the permission problem alone, so you're still waiting on your manager to sign off on things you could decide yourself. That needs an explicit agreement, and the useful way to sort decisions is by how expensive they are to undo.

Write the three buckets down and take them to your manager. Most managers have never articulated this and will agree to more than you expect once they see it on paper.

Keep the third list short and be honest about it. If everything is on it, you haven't agreed to anything.

The structural version of this is what the Mochary Method calls Areas of Responsibility: every function in the company written down with exactly one name next to it. If your company has one, find out what it says about your area, because it's a lot easier to point at a document than to explain why you feel overmanaged. If it doesn't, Molly Graham's rule is worth quoting to your manager directly. She says two people owning a goal is nobody owning a goal, and that the work of putting one name next to each number is painful but it's the job. Our guide for managers walks through the same handoff from their side, and it's a reasonable thing to send your manager if the relationship can take it.

Pick one small thing and build a record on it

Conversations rarely rebuild trust on their own. What does it is a handful of things going well without your manager's involvement, and you can set those up on purpose rather than waiting for one to come along.

Pick something with three properties: it's genuinely yours, it's small enough that a mistake wouldn't be expensive, and it produces a visible result within a few weeks. Then negotiate a clean run at it.

Six weeks of something working, reported by you before anyone asked, is worth more than any amount of explaining that you're capable. Then ask for the next thing while the evidence is fresh. Managers loosen up in increments, and the increment is easiest to get right after a win.

Mochary's format for reviewing actions is a useful shape for these check-ins. For each thing you said you'd do, you write whether it's done. If it is, the learnings or next steps. If it isn't, three things: what blocked you, whether you still want to do it and by when, and what you'll change so you don't get blocked the same way again. Running your own review that way, before your manager runs it for you, changes what the meeting is about.

When the problem is actually your work

Sometimes the honest answer is that the checking is a reasonable response to something real. Work has come back rough, a date got missed, or a customer heard something they shouldn't have. Managers rarely say this clearly, partly because it's uncomfortable and partly because in some companies they're not supposed to until it's documented.

So go and find out. Kim Scott's approach is to have one question you always ask, refine it until it works, and use it often enough that people believe you want the answer.

Scott's advice is to save five minutes at the end of your 1:1 for it, ask your manager and your closest cross-functional colleagues, and vary the wording so it doesn't sound rehearsed. She also says to expect the first answer to be "no, everything's fine", and to keep going. If someone clearly hates being put on the spot, tell them you'll ask again next time and you want them to have noticed something.

Two follow-ups are worth having ready. Ask "is there a version of my work you'd stop reviewing if it looked different?", which turns a vague concern into a specific standard. And ask "are we in a place where this needs to be written down?", which is a direct way to find out whether a performance process has started without you being told. If the answer to that is yes, our guide to the questions to ask when you didn't get what you expected covers how to get a specific bar out of a manager who's being careful.

If it turns out the concern is real, that's actually the most fixable version of this problem. Once you have a named gap with a date on it, you can go and close it, which is more than you can do with a manager who's uneasy about you for reasons nobody will say out loud.

When none of this is working

Give it a quarter. That's long enough for a cadence to hold, one small thing to go well, and a decision agreement to get tested. If you've done all of that and you're still being asked for status every day, more patience isn't going to fix it.

On raising it directly, our guide to disagreeing with your boss covers how to say a hard thing without your manager hearing it as an attack, and our guide to running a useful 1:1 covers where in the meeting to put it.

And it is sometimes right to leave. Ethan Evans spent over fifteen years at Amazon, most of it as a vice president, and someone whose new leader had taken away their independence asked him this exact question.

Note the order he puts it in. Earning trust, raising it privately, and asking what would change their mind all come before changing teams, and most people skip straight past them to being frustrated. But he doesn't pretend the last step isn't real.

The cost of staying isn't only the annoyance. It's that you stop making decisions, and a couple of years of not making decisions shows up in your next interview, where you'll be asked what you owned. If you're at that point, start looking while you're still employed and treat the job you have as practice for the conversations. There's no prize for outlasting it.

Frequently asked questions

What are the signs of a micromanager?

They want to approve work you were hired to do, they ask for status more often than the work changes, they rewrite rather than give feedback, they want to be copied on everything, and decisions stall while they're busy. The strongest signal is that your peers at the same level make calls you have to ask permission for.

How do I get my manager to trust me?

Pick something small that's genuinely yours, agree in advance what a good result looks like, run it without a review step for a set period, and report the outcome yourself before anyone asks. Do that two or three times. Trust is built from a record of specific things going well without them, and you can arrange those on purpose.

Should I tell my boss they're micromanaging me?

Not in those words. The label puts them on the defensive and gives you nothing to do next. Describe the specific behavior, the cost, and what you'd like instead: "I'm asked for status on this most days, it's about half a day a week, and I'd like to try a Friday written update instead."

Is it micromanagement if I'm new?

Usually not. Close supervision in your first few months is a manager doing their job, and it should get lighter as they see your work. Ask at the start what would need to be true for the check-ins to reduce, and by when. If nothing has changed by month four, that's worth raising.

What if my manager was told to watch me?

Ask directly whether something changed and whether anything needs to be written down. Managers can often confirm that a concern exists even when they can't say where it came from. If a performance process has started, get the specific bar and the date in writing, because that's the version of this you can actually close out.

Can I go over my manager's head?

Use a skip-level to ask what normal looks like at your level rather than to report your manager. Going over their head to complain almost always gets back to them and makes the next six months worse. Save the escalation for behavior that's genuinely out of bounds, and bring dates and examples when you do.

The whole thing on one page