Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Micromanages Every Decision
Transcript
- Lucas: So we've talked about the boss who takes credit, the boss who gaslights, the boss who avoids conflict—but there's one type that almost everyone has encountered at some point, and it might be the most exhausting of all: the micromanager. Luna: The boss who wants to approve every email, sit in on every call, review every line of code. Yeah, I think most of us have been there. Lucas: And before we dig into the tactics, I want to just acknowledge something quick. If we've helped you think through a career move or a tough conversation, a couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: Yeah, it really does make a difference. And we keep the show ad-free because of it. So anyway—micromanagers. Why is it so draining? Lucas: Because it's not just about the extra work of reporting—it's the signal it sends: 'I don't trust you to do your job.' And that erodes confidence over time. But here's the thing—micromanagement is almost never about you. It's usually about the boss's own anxiety, or pressure they're getting from above. Luna: So the first step is reframing it in your head—this isn't a personal indictment of your competence. Lucas: Exactly. Let me give you a concrete example from a listener I'll call Priya. She's a project manager at a mid-sized logistics firm. Her boss, the director of operations, required a fifteen-minute check-in every morning and final sign-off on every single vendor email—even routine ones like 'can you confirm the delivery window.' Luna: That sounds exhausting. And probably a huge time sink for the boss too. Lucas: Right. So the first thing Priya did was preempt the check-in. Instead of waiting for the daily call, she started sending a brief written status update every morning—bullet points: what she did yesterday, what she's doing today, one thing she needs input on. She kept it to three lines max. Luna: So she's replacing the live check-in with something the boss can read in thirty seconds. That gives the boss a sense of control without the synchronous drain. Lucas: Exactly. And it worked—the boss started skipping the call some days because he already had the update. That's step one: preempt the impulse to check. Luna: Step two? Lucas: Build a 'trust dossier.' Over-communicate early on a few high-visibility tasks. Priya picked three vendor relationships that were straightforward—no history of issues—and for the first two weeks, she copied the boss on every email, flagged the ones that needed action, and sent a short summary at the end of the week. She made her work transparent in a way that required zero effort from the boss to follow. Luna: That's smart—you're giving them visibility without them having to demand it. And after a few weeks of no surprises, the boss might start to relax. Lucas: That's the idea. After about a month, Priya asked her boss if she could send routine vendor emails without prior approval, as long as she CC'd him. He said yes—because she'd proven she wouldn't mess up. And then she slowly expanded the scope. Luna: I love the gradual approach. It's not a big confrontation—it's a series of small proofs. Lucas: And that brings us to step three: the decision threshold document. Priya created a simple one-pager that listed common decisions and proposed who should make them—her, the boss, or both. For example: 'Schedule a vendor call' — Priya decides. 'Change contract terms' — boss decides. 'Escalate a service issue' — Priya decides, boss informed. She presented it as a way to save the boss time. Luna: Wow—that's really proactive. It gives the boss a clear framework, and it's hard to argue with because it's framed as efficiency. Lucas: Right. And the boss signed off on it with minor tweaks. Within two months, Priya's morning check-ins were gone, and she was handling ninety percent of vendor communications without review. Luna: But I imagine that doesn't work with every micromanager. Some are just wired that way—or their boss is breathing down their neck. Lucas: True. Let me share a different story. I worked with a guy named Tom—he was a senior analyst at a bank, and his boss, the VP, wanted to review every slide before it went to the managing director. Even formatting changes. Tom tried the preemptive update approach—didn't work. The VP just kept asking for more detail. Luna: So what did Tom do? Lucas: He tried a counterintuitive move: he started asking his boss for advice on small strategic questions. Like, 'Hey, I'm thinking about how to structure the competitive analysis section—would you recommend a table or a chart?' The boss loved giving input on those micro-decisions. And once he felt his expertise was being valued, he stopped scrutinizing every detail. Luna: That's fascinating—it's like giving them a little bit of the control they crave, but in a way that actually reduces their overall interference. Lucas: Exactly. It's a quid pro quo: you get my advice on the interesting stuff, I get autonomy on the execution. And for a boss who micromanages because they feel insecure or undervalued, that can be a game-changer. Luna: But I think there's a line, right? At some point, if the micromanager is truly incapable of letting go, you have to decide whether it's worth staying. Lucas: Absolutely. And I want to be honest about that. Priya's boss was anxious but reasonable—he responded to data and structure. Tom's boss needed to feel smart. But there are bosses who micromanage out of a deep need for control that no amount of trust-building will satisfy. You can try all these tactics, and if after three months nothing changes, it might be time to start looking. Luna: How do you know when you've hit that wall? Lucas: A couple of signals. One: your boss rejects every proposal for more autonomy, even small ones. Two: they actively undermine your decisions after you've been given the green light. Three: you find yourself spending more time managing the boss's anxiety than doing actual work. If that's the case, the problem isn't your approach—it's the boss. Luna: And then you have to weigh the cost of staying versus the risk of leaving. Because chronic micromanagement can really damage your confidence and your career growth. Lucas: Yeah. I've seen people stay for years under a micromanager and then struggle when they move to a healthy environment because they've forgotten how to make decisions independently. So there's a real long-term cost. Luna: Let's circle back to the practical steps for people who want to try the gradual approach. What's the first thing they should do tomorrow? Lucas: Identify one low-stakes task that your boss currently reviews. Then, send them a brief email before they ask: 'Here's what I'm planning for this task. I'll proceed unless I hear otherwise.' That simple shift—from reactive to proactive—starts to reset the dynamic. Luna: And if they push back, you haven't lost anything—you've just learned something about how much rope you have. Lucas: Exactly. And pay attention to their response. If they say 'great, go ahead,' that's a win. If they say 'let's discuss it in our next check-in,' you can use that as an opening to talk about the check-in itself. 'Hey, I notice we spend a lot of time on these routine decisions—what if I send a quick summary instead?' Luna: So it's about turning every interaction into a small experiment for more autonomy. Lucas: Right. And the key is to be patient. It took Priya two months to get to a good place. It might take you three or four. But if you see no progress after that, you have your answer. Luna: One last thing—what about the boss who micromanages because they're under pressure from their own boss? How do you handle that? Lucas: That's actually a slightly different case. If the pressure is coming from above, your boss might be micromanaging as a coping mechanism. In that situation, you can help by making your work 'audit-ready'—documenting your process and decisions so that if the big boss asks, your boss can point to the paper trail. That reduces their fear of being blindsided. Luna: So you're essentially giving them ammunition to defend you and themselves. Lucas: Exactly. And that can turn a micromanager into an ally—because now you're helping them manage their own boss. Luna: I think that's a great note to end on. Micromanagement is draining, but it's not always hopeless. Lucas: It's not. And if you've tried everything and it's still not working, remember: a good boss is out there. Sometimes the best career move is finding one.