Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Always Micromanages Others
Transcript
- Lucas: So you've got a team member who's technically brilliant, delivers on time, knows the codebase inside out — but they're driving everyone else crazy because they can't stop micromanaging their peers. Luna: Oh, I've seen this. The person who just can't let go, even when they're not the lead on a project. Lucas: Exactly. And it's a tricky one because on the surface, this employee looks like a high performer. They're detail-oriented, they care deeply. But the cost is real — you lose junior talent, collaboration stalls, and you end up with a bottleneck instead of a multiplier. Luna: So how do you actually address it? Because just telling them 'stop micromanaging' usually backfires. Lucas: Right, it's like telling someone 'relax' — it never works. I want to talk about a case I came across from a mid-sized software company, about 200 engineers. There was a senior developer named Priya — she was incredible technically, but her junior colleagues were quitting because she would rewrite their code without asking, she'd sit in on their calls uninvited, she'd email their stakeholders directly. Luna: Classic. And I bet she thought she was being helpful. Lucas: Absolutely. When her manager finally sat down with her, Priya said, 'I'm just trying to protect the team from making mistakes.' And that's the key insight — micromanagement of others is almost never about control for its own sake. It's usually rooted in anxiety — past trauma from a project that failed, or a lack of trust in the system. Luna: So the underlying emotion is fear, not ego. That changes how you approach it. Lucas: Totally. Priya's manager used what I call the 'Trust Triangle' framework. Three points: clarify boundaries, build competence, and reward delegation. Let's walk through each one. Luna: Let's start with boundaries. How do you set them without sounding like you're punishing her for caring? Lucas: You have to be specific. Priya's manager said something like: 'I see how much you want this team to succeed. Here's the thing — when you rewrite someone's code before they've had a chance to respond to feedback, you rob them of the learning moment. So let's agree: you can review, you can comment, but you don't touch the code unless they ask. Let's try that for two weeks.' Luna: That's good — it's a behavior, not a character attack. And it's time-boxed. Lucas: Exactly. The second point is build competence. Priya was micromanaging because she genuinely believed her colleagues couldn't handle things. So her manager worked with her to create a skill map — what did the juniors need to learn for Priya to feel comfortable? And then they made a plan for Priya to teach those things deliberately, rather than just taking over. Luna: That reframes her role from 'doer' to 'teacher'. Much more sustainable. Lucas: Right. And the third point — reward delegation — is the one most managers forget. Priya had been rewarded her whole career for being hands-on. So her manager started celebrating when Priya let someone else own a piece of work and it went well. Even small wins — like 'I noticed you didn't jump in on that call, and Sarah handled the client question perfectly. That's because of your coaching.' Luna: That's a really concrete way to retrain the instinct. And it probably made Priya feel seen in a new way. Lucas: Exactly. Over about eight weeks, Priya started to pull back. Her juniors reported feeling more trusted, and the quality actually stayed the same. The bottleneck disappeared. Luna: So the manager here didn't just slap a rule on it — they addressed the root cause. I think that's a great blueprint. Lucas: Let me add one more layer. Sometimes, the micromanagement is a mirror — it reflects a lack of clarity from the manager themselves. If you haven't clearly defined what 'done' looks like, or what decisions the team can make independently, your anxious high-performer will fill that vacuum. Luna: That's a good point. So before you coach the employee, check your own systems. Are the expectations clear enough that trust can actually exist? Lucas: Exactly. Priya's manager realized that the team's decision-making framework was vague. So they documented it together — what constitutes a 'tier one' decision that needs Priya's input, versus a 'tier two' that the junior can own. That gave Priya a concrete off-ramp. Luna: I love that. It's basically a delegation cheat sheet. And it works both ways — the juniors know when to escalate, and Priya knows when to stay out. Lucas: Right. And here's a little script: if you're in this situation, you can say, 'I need you to trust the process I'm building. If something fails, I own it. But I need you to give people room to grow.' That's usually enough for a well-intentioned micromanager to pause. Luna: You know, this episode feels really practical. If today was actually useful to you, the way these stay ad-free is listener support. Lucas: Yeah, it's a small thing that makes a big difference. You can find us at buy me a coffee dot com slash fexingo. Luna: And we really appreciate it. Okay, back to the management tactics — because I think there's one more nuance I want to explore. Lucas: What's that? Luna: What if the person micromanaging is actually a peer, not a direct report? Like a senior engineer who nags the project manager about every detail? Lucas: That's a different dynamic. You don't have positional authority, so you have to appeal to shared goals. You might say, 'I know we both want this project to succeed. When you check in on every task, it actually slows me down because I have to stop and respond. Can we agree on a weekly sync instead?' Luna: So you're naming the impact on you, not accusing them. That's smart. Lucas: And you can offer an alternative structure. The key is to channel their vigilance into a cadence that works for you both. Set a standing 15-minute check-in every Monday — that gives them the control they need without the constant drip. Luna: I think a lot of micromanagers would actually welcome that structure because it reduces their own anxiety too. Lucas: Absolutely. It's a win-win. And if they still won't let go after you've tried the Trust Triangle and clear boundaries, then you have a deeper issue — maybe they're in the wrong role, or they need to move to an individual contributor track where they don't have to manage others. Luna: So sometimes the kindest thing is to help them find a role that fits their wiring. Not everyone is meant to be a multiplier on a team. Lucas: Right. And that's not a failure — it's actually good leadership to recognize that and have that conversation honestly. Luna: Lucas, I think the biggest takeaway for me is that micromanagement of others is almost always a symptom. You have to treat the cause, not the behavior. Lucas: Exactly. Look for the fear, build the trust, define the boundaries. And remember — the goal isn't to stop them from caring. It's to channel that care into something that builds the team instead of draining it. Luna: Great way to put it. Thanks for the insights. Lucas: Always a pleasure. See you next time.