Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Micromanages Others
Transcript
- Lucas: Luna, you ever had someone on your team who isn't your boss, isn't a formal lead, but they basically start managing their peers? Like, they review everyone's work, give unsolicited feedback, and quietly take over decisions that aren't theirs to make. Luna: Oh, absolutely. I've seen it firsthand. It's almost always a senior person who's very good at their job, but they can't stop themselves from 'helping' in a way that actually undermines everyone else. Lucas: Right. And it's a really tricky thing to manage because on one hand, you want that person's high standards and initiative. On the other hand, they're slowly eroding the autonomy and confidence of the rest of the team. So today I want to talk about how to handle the team member who micromanages their peers. Luna: Good. Because I think a lot of managers see it and they hesitate. They think, 'Well, they're just being thorough,' or 'Maybe I should let the peers sort it out themselves.' But that usually backfires. Lucas: It really does. And I want to ground this in a specific case. I was talking to an engineering director at a mid-sized SaaS company — about 40 engineers — and she had a senior engineer named Priya. Priya was excellent technically, but she had started rewriting her teammates' pull requests without being asked. She'd leave comments like, 'Actually, this approach is cleaner,' and she'd just push her own code. Luna: Oh, that's the worst. It's not feedback at that point, it's a takeover. How did the director handle it? Lucas: She came to me because she was stuck. She'd already told Priya to 'be more collaborative,' but that was too vague. So we worked through a three-step intervention. Step one: a private conversation that reframes the behavior not as a character flaw but as a symptom of anxiety about shared outcomes. Luna: I like that reframe. Because usually the micromanaging peer isn't trying to be a jerk. They genuinely believe they're helping. They're just scared the project will fail if they don't control it. Lucas: Exactly. So the director said to Priya, 'I see how much you care about the quality of our work. That's valuable. But when you rewrite someone else's code without discussing it first, you're sending a message that you don't trust them. And that damages the team's ownership.' Then she asked, 'What's the fear underneath?' And Priya admitted she was worried the team would ship something buggy and she'd be the one who has to fix it later. Luna: That's so honest. And that's the key — once you name the fear, you can address it directly. So what was step two? Lucas: Step two was a structured delegation tool. We called it the 'decision grid.' For any project, Priya and her teammates would agree upfront: who decides on the architecture, who decides on the implementation details, who decides on the testing approach, and who has final sign-off. They literally wrote it down in a shared doc. That way Priya knew exactly where she could influence and where she needed to step back. Luna: So it's a boundary-setting tool. I love that. And I bet it also helped the other team members feel safer because they knew the rules were explicit. Lucas: Exactly. And step three was a feedback loop. The director started recognizing Priya publicly when she coached someone rather than corrected them. So she'd say in a team meeting, 'Priya spent 20 minutes helping Alex think through the database query design. That's the kind of mentorship I want to see more of.' That reinforced the new behavior. Luna: That's smart. You're shaping the culture by what you reward. And I think a lot of managers miss that step — they only focus on stopping the bad behavior, not on redirecting the energy. Lucas: Right. And the results were good. Within about six weeks, Priya's unsolicited rewrites dropped to nearly zero. She started asking, 'Would you like me to look at that?' instead of just doing it. And the team reported feeling more ownership. Luna: But I want to push back on something. Is it always the manager's job to intervene? Couldn't the peers just stand up for themselves? I mean, in a mature team, maybe someone should just tell Priya, 'Hey, back off.' Lucas: In theory, sure. But in practice, it's really hard for a peer to give that feedback, especially if Priya is more senior. There's a power imbalance even if it's not formal. And if the team tries and fails, the dynamic gets worse. The manager has to set the container. Luna: That's fair. So the manager's role is to create the conditions where peers can eventually have those conversations themselves. But you start by modeling it. Lucas: Exactly. And that brings me to another point — how do you distinguish micromanagement from healthy mentorship? Because some managers overcorrect and tell their senior people never to give feedback, which is just as bad. Luna: Yeah, you don't want to kill the helpful impulse entirely. So what's the line? Lucas: The line is: does the feedback build the other person's capability, or does it replace their work? A mentor asks questions: 'What made you choose this approach? Have you considered X?' A micromanager says: 'Do it this way instead.' One expands thinking, the other contracts it. Luna: That's a great litmus test. And it's easy for the manager to observe in stand-ups or code reviews. So if you see your senior engineer asking a lot of 'what if' questions, you're probably fine. If you see them closing down options, that's the red flag. Lucas: Right. And the tricky part is that the micromanager often doesn't see themselves that way. They think they're being helpful. So in that first conversation, you want to get them to see the impact, not just label the behavior. Use specific examples: 'Last Tuesday, you rewrote Sarah's function without talking to her. How do you think that made her feel?' Luna: And if they get defensive? What if Priya had said, 'But her code was wrong. I was just fixing it before it caused problems.' Lucas: Then you validate the intent but hold the boundary. You say, 'I know you had good intentions, and I'm glad you care about quality. But the impact is that Sarah loses confidence. So going forward, if you see something that needs fixing, I need you to talk to the person first. If they disagree, you bring it to me. You don't just rewrite it.' Luna: That's firm but fair. And it also gives the micromanager a clear escalation path so they don't feel like they're letting quality slide. Lucas: Exactly. And speaking of quality — if you've been enjoying these episodes and they're helping you think through real management situations, honestly, if today was worth a coffee to you, that's the link. Buy me a coffee dot com slash fexingo. It's how we keep the show ad-free and focused on practical advice. Luna: Yeah, listener support makes a huge difference. And it really does help us keep doing deep dives like this one. Lucas: So back to the practical side. One thing I want to emphasize is that this approach works beyond engineering. I've seen it work in marketing teams, in sales ops, even in finance. The pattern is universal: someone with high standards and low trust starts taking over. Luna: Give us an example outside of engineering. Lucas: Sure. I worked with a marketing team where the senior copywriter, let's call her Maria, would rewrite her junior colleague's email drafts before they were ever sent. The junior person felt like they couldn't improve because they never got feedback — they just got a finished product. Same dynamic. Luna: So the manager used the same three-step approach? The private conversation, the decision grid, and the recognition for coaching? Lucas: Almost exactly. The decision grid was a little different — they agreed that for first drafts, the junior writer would have final say on tone and voice. Maria could suggest edits, but only in a document with comments, not direct changes. And the junior writer could accept or reject each comment. That gave the junior ownership while letting Maria still contribute. Luna: So it's about creating a safe container for disagreement. The junior person isn't forced to accept every suggestion, but they're also not ignoring the senior's expertise. Lucas: Exactly. And Maria actually became a better mentor because she had to articulate her reasoning in the comments instead of just fixing it. Her junior colleague said later that she learned more from those comment threads than from any training session. Luna: That's the best outcome. The micromanager becomes a teacher, and the team gets stronger. So what's the one thing you'd tell a manager who calls you tomorrow and says, 'I've got a Priya on my team and I don't know where to start?' Lucas: I'd say: start with curiosity, not judgment. Have the private conversation and ask, 'What are you afraid will happen if you don't step in?' Nine times out of ten, the answer will reveal a legitimate concern that you can address structurally. Then build the guardrails — the decision grid — so they can let go safely. And then consistently reinforce the behavior you want to see. It takes four to six weeks, but it works. Luna: And don't wait too long. The longer you let it go, the more the team's trust erodes. By the time you act, you might have already lost a good employee who felt overshadowed. Lucas: Exactly. The cost of inaction is higher than the cost of an awkward conversation. Priya's director told me later that if she'd waited another month, she would have lost Sarah — the junior engineer Priya kept overriding. And Sarah was a star performer. Luna: That's the real risk. So act early, act with structure, and redirect that energy into coaching. That's the takeaway. Lucas: Yeah, I think that's a solid place to leave it. Luna, as always, good to talk this through. Luna: You too, Lucas. See you next time.