Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Handle a Micromanaging Boss
Transcript
- Lucas: So you've just become a manager — maybe you're three months in, maybe six — and you're finally getting the hang of leading your team. But there's one person who isn't getting the hang of you: your boss. Luna: The micromanaging boss. The one who wants to be cc'd on every email, who checks in twice a day, who rewrites your team's project plan. Lucas: Exactly. And it's a brutal spot because you're supposed to be building trust with your direct reports, but you feel like you have zero trust from above. Today I want to talk about a specific case — a friend of mine named Priya who became a regional manager at a midsize logistics company last year. She oversees five warehouse teams, roughly 60 people. And her boss, the VP of operations, was a classic micromanager. Luna: What was he doing specifically? Lucas: She'd send him a weekly ops summary, and he'd reply within an hour asking for more detail — why this metric moved, who approved that overtime, what the plan was for next Tuesday. He wanted to see her schedule for the next day, every morning. He'd call at 6 PM to ask about something she'd already covered in an email. It was wearing her down, and she felt like her team noticed she was on edge. Luna: That's the double bind. You can't project confidence to your team if you're being treated like you don't have any. Lucas: Right. And the natural instinct is to push back — 'trust me, I've got this.' But that almost never works with a micromanager, because the problem isn't your competence. It's their anxiety. Luna: So what did Priya do? Lucas: She tried something counterintuitive. Instead of resisting the oversight, she invited more of it — but on her terms. She proposed a weekly 30-minute check-in, same time every Wednesday, where she'd walk him through her three biggest decisions from the past week and her three biggest decisions for the week ahead. She called it the 'first-draft' meeting. Luna: First-draft meaning she was presenting her thinking before it was final? Lucas: Exactly. She'd say, 'Here's my first draft on the shift schedule change. Here's why I'm leaning this way. What am I missing?' That gave him a structured, low-stakes way to contribute without her feeling like he was second-guessing everything. And it worked because it addressed his anxiety directly — he got a preview, he got to feel involved, and she got to keep control of the execution. Luna: So she was basically preempting his urge to micromanage by giving him a controlled channel for his input. Lucas: Yes. And here's what surprised her: after about six weeks, the daily calls stopped. The emails got shorter. The VP started saying things like, 'I trust your judgment.' Because the Wednesday meeting had built a track record — she consistently showed good judgment, and he could see that she was proactively managing risk. Luna: I think there's a deeper lesson there. A lot of new managers assume that trust is something you have to earn by being perfect. But sometimes it's more about managing the relationship and the rhythm. Lucas: Absolutely. And I want to get into the psychology of why micromanagement happens, because it's rarely malicious. In Priya's case, her VP had been promoted from a similar role years ago, and he had his own scars. He'd made a costly mistake early in his tenure — a warehouse mix-up that cost the company about $300,000. So his micromanaging was really about managing his own fear of that happening again. Luna: That reframes it. It's not about you. It's about their history. Lucas: Right. And when you understand that, you can stop taking it personally and start being strategic. So the first step is diagnosis: is this micromanager anxious, or are they controlling by nature? If it's anxiety, the solution is predictability — give them a reliable structure for input. If it's a control personality, the approach is different. Luna: What's the difference with a control personality? Lucas: Control personalities micromanage because they genuinely believe they can do it better. They don't delegate because they don't trust anyone else's standards. In that case, you need to build a case with data — show that your decisions produce results equal to or better than theirs. And you need to be very explicit about scope: 'I'm responsible for X, Y, and Z. If you want to be involved in X, let's define what that looks like. But Y and Z need to be mine.' Luna: That's a hard conversation. Do you have a script for that? Lucas: I've seen it work like this: 'I want to make sure I'm fully owning my role. Can we agree on which decisions I can run with independently and which ones you want visibility into before I move forward?' That puts the ball in their court to define the boundaries, but you've framed it as you wanting to be accountable — not as you trying to push them away. Luna: That's smart. It's basically asking permission to be trusted. Lucas: Exactly. Now, there's another move that's underrated: over-communicate early, then taper off. When you're new, your boss has no data about your judgment. So for the first 30 days, over-share. Send brief daily updates. Explain your reasoning. After a month, you can say, 'You've seen my process for 30 days. I'm going to scale back to weekly summaries unless something urgent comes up.' If they've seen you make good calls, they usually agree. Luna: That's like an onboarding period for the boss. You're training them to trust you. Lucas: Training is exactly the right word. Because the boss's behavior is a pattern, and patterns can be reshaped. The key is to be consistent and predictable. Once they learn that your updates are reliable, they don't need to chase you for them. Luna: I want to go back to Priya. Did her team notice the change? Lucas: They did. She told me that after a couple months, her warehouse leads started commenting that she seemed calmer. And that's the hidden cost of a micromanaging boss — it trickles down. If you're anxious, your team picks up on it. By fixing the relationship upward, she actually became a better manager downward. Luna: That's a great point. Your ability to lead your team is directly tied to how much autonomy you feel yourself. Lucas: And if you're stuck with a micromanager who won't budge, there's a longer game. You can document your wins — specific decisions you made that turned out well, with measurable outcomes. After six months of that, you have a case for a conversation about expanding your scope. And if that fails, you have a case for a lateral move or a new role. Luna: So the goal isn't to fix the person, it's to fix the situation enough that you can do your job well. Lucas: Exactly. And if today's episode was useful to you — if you're a new manager dealing with a hovering boss — the way we keep these conversations ad-free is listener support. You can buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. It helps us keep doing episodes like this without any sponsors. Luna: And we really appreciate it. It's what lets us keep the focus purely on what's helpful for you. Lucas: Alright, back to it. So we've talked about managing anxiety-driven micromanagers and control-driven ones. But there's a third type that's worth mentioning: the micromanager who's actually a poor delegator. They don't know how to let go because they've never learned. Luna: That's a training gap on their part, but you still have to live with it. Lucas: Right. And in that case, you can actually help them delegate to you. You can say, 'I'd like to take this off your plate entirely. Here's my plan. Can I report back to you once it's done, rather than checking in along the way?' That gives them a clear off-ramp — they don't have to think about it anymore because you've given them a framework for closure. Luna: That's almost like managing upward by offering solutions. Lucas: Yes. And there's research on this. A study from the Harvard Business Review a few years ago looked at 400 new managers and found that the ones who successfully managed a micromanaging boss used one of three strategies: structured communication, like Priya's weekly check-in; boundary negotiation, where they explicitly discussed scope; or performance proof, where they let results speak. The least effective strategy was complaining to HR or trying to avoid the boss. Luna: Avoiding makes it worse, because then the boss feels like they have to check in more. Lucas: Exactly. So the takeaway from Priya's story and from the research is: take the initiative. Don't wait for your boss to change. Design a system that gives them what they need — information, involvement, reassurance — while preserving the autonomy you need to lead your team. Luna: I think the confidence to do that comes from realizing that your boss is probably nervous too. They've got a new manager reporting to them, and they're being judged on your performance. Lucas: That's a great reframe. Your boss's micromanagement is often just their way of trying to protect you — or themselves. Once you see it that way, it's a lot easier to have a constructive conversation. So if you're in that seat right now, try the first-draft meeting. Give it three weeks. See if the temperature comes down. Luna: And if it doesn't, you've still built documentation and a relationship that will serve you well wherever you go next. Lucas: Exactly. That's it for this episode of New Manager Conversations. We'll be back next week with another practical challenge. Until then, good luck managing up.