Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How Managers Lose Control Through Micromanagement
Transcript
- Lucas: There is a specific moment in almost every new manager's career when they realize they are doing all the heavy lifting themselves. It usually happens around month three or four, when the initial excitement wears off and the reality of delegated tasks starts to fray at the edges. You start checking emails before your direct reports do, you start rewriting code or copy because you can see the flaws faster than they can explain them. Luna: And the worst part is, you tell yourself you are just being thorough, but everyone else knows you are just afraid the project will fail if you aren't holding the wheel. It creates this invisible wall between you and your team that no amount of positive feedback can really repair. Lucas: Exactly. And what is fascinating about the current market environment here in late September of twenty twenty six is that remote and hybrid work has amplified this instinct. When you cannot see people working, the urge to monitor their activity metrics spikes. We are seeing a rise in digital micromanagement tools that track keystrokes or screen time, which is frankly a disaster for retention. Luna: It feels like we have swung too far from the wild west of early remote work into this hyper-surveillance phase. I had a friend who left her job last week because her manager started requiring daily video status updates that lasted an hour each. Lucas: That is a classic example of confusing visibility with productivity. The core issue isn't really about trust in the abstract; it is about the manager's inability to tolerate ambiguity. They want to control the process because they are scared of the outcome. But research consistently shows that when you remove autonomy, you remove ownership. Luna: So the team stops caring about the result because they know they didn't get to make the choices. They become executors rather than owners. That is a dangerous place for a company to be long term. Lucas: It is. And it creates a bottleneck. If the manager is the decision node for everything, the whole organization moves at the speed of that one person's bandwidth. We saw this clearly during the supply chain disruptions earlier this year. Companies that empowered local teams to make sourcing decisions recovered faster than those that required headquarters approval for every small change. Luna: Right, so the very thing the manager thinks is protecting the project is actually slowing it down. It is the control paradox. Lucas: The control paradox is exactly the right term. The more you try to control the inputs, the less predictable the outputs become because you are demotivating the people doing the work. Now, I want to take a quick moment to talk about how we keep this show running. Luna: If you are finding these conversations useful for your own leadership journey, supporting us directly helps keep the content free and ad-free. You can find us at buy me a coffee dot com slash fexingo. Lucas: Thank you to everyone who has already contributed. It genuinely allows us to spend more time digging into these case studies rather than worrying about overhead. Now, back to the mechanics of breaking the cycle. Luna: Yeah, so once a manager realizes they are hovering, how do they actually stop? It is hard to unlearn that habit overnight. Lucas: You have to shift from monitoring activities to defining outcomes. Most new managers default to checking whether someone did the task. The better approach is to agree on what success looks like before the task begins. You set the guardrails, not the steering wheel. Luna: So instead of asking how many hours they spent on the report, you ask if the report answered the client's core question. It changes the metric from effort to impact. Lucas: Precisely. And this requires a higher level of upfront communication. You have to be clearer about constraints and expectations early on. It feels like more work initially, but it saves time later because you are not constantly correcting course. Luna: But doesn't that require the manager to be really confident in their ability to judge the final output? What if they don't know enough to set good guardrails? Lucas: That is a valid concern. This is where the manager needs to lean on their peers or mentors. Admitting you need help setting the framework is a sign of strength, not weakness. It also models humility for the team. Luna: I like that. It turns the manager from a supervisor into a coach. A coach doesn't play the game for the athlete, but they make sure the athlete knows the rules of the stadium. Lucas: That analogy works well. Another practical step is to institute structured check-ins that are focused on blockers, not progress. Instead of a daily update, have a weekly fifteen-minute sync where the employee lists what is stopping them from hitting their goal. Luna: That takes the pressure off the manager to nag and gives the employee agency to identify their own risks. It feels much more collaborative. Lucas: It does. And it builds psychological safety. If an employee knows they can say they are stuck without being micromanaged, they will raise issues earlier. Early intervention is always cheaper than late-stage crisis management. Luna: So the micromanager is actually creating more work for themselves by waiting until the end to check everything. They are betting against their own efficiency. Lucas: They are. There is also a talent retention angle here. High performers hate being micromanaged because it signals that you don't value their expertise. If you treat a senior engineer like a junior intern, they will leave for a company that trusts their judgment. Luna: It is a huge signal. It tells them that their growth is stalled. You can't grow if you aren't allowed to make mistakes and learn from them. Lucas: Exactly. Mistakes are tuition fees for experience. If the manager prevents the mistake, they prevent the learning. The team stays at the same skill level forever. You end up with a department of juniors led by a exhausted senior manager. Luna: Which brings us back to burnout. The manager burns out from doing the work, and the team burns out from lack of autonomy. Everyone loses. Lucas: Everyone loses except maybe the competitor who is building a high-trust culture. It is a strategic disadvantage. Companies that master delegation scale better because they are not bottlenecked by their leadership layer. Luna: So the advice for listeners today is to audit your own behavior. Are you checking in because it adds value, or because it makes you feel safe? Lucas: That is a tough question to answer honestly. But if you catch yourself rewriting something your team submitted, pause and ask why. Was it truly broken, or was it just different from how you would have done it? Luna: Different is often better. Diversity of thought leads to better solutions. Your way is just the only way you know. Lucas: Right. So let go of the need for it to look like your work. Let it look like their work. That is how you build a real team. Luna: Agreed. It is scary to let go, but it is the only way to scale your impact beyond your own two hands. Lucas: Next week we will tackle the topic of giving difficult feedback without damaging the relationship. For now, try to delegate one task this week and resist the urge to touch it. Luna: Good luck with that. It is easier said than done, but worth the effort. See you next Monday.