Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Manager Trap Of Fixing Everything
Transcript
- Lucas: There is a specific kind of panic that sets in when a high performer gets promoted to management. It usually happens around month three. They realize they are no longer judged on their own output, but on their team's. And because they are good at their job, they assume the best way to ensure quality is to just do it themselves or closely supervise every detail. Luna: It feels like the only safe bet in the moment, right? Like if I don't check this code or edit this deck, it'll look bad and reflect on me. Lucas: Exactly. But what we see repeatedly is that this creates a bottleneck. The manager becomes the single point of failure for every minor decision. I want to look at a case from a mid-sized software company where a new director realized he was actually slowing down his team's velocity by being too involved in the weeds. Luna: So he was the bottleneck? That must have been frustrating for everyone else who wanted to move faster. Lucas: It was. His engineers were waiting on him to approve design choices that should have been theirs. He wasn't trying to be controlling; he was trying to be helpful. But the data showed that his direct involvement correlated with a twenty percent drop in sprint completion rates over two quarters. Luna: That is a massive hit to productivity. Did he realize how much time he was actually spending reviewing things versus leading? Lucas: He didn't until someone did a simple audit of his calendar. He was spending forty percent of his week in review cycles. The irony was that he had hired six people to handle that workload, yet he was doing half the work himself. So the question is, how do you step back without letting standards slip? Luna: I guess the fear is always that the quality will drop the moment you aren't there to catch every mistake. Lucas: Right. And that fear is rational. Quality matters. But there is a difference between checking for errors and preventing mistakes. The shift happens when you move from inspecting the final product to coaching the process. Let's talk about one technique called 'decision framing' that helped this director regain control without doing the work. Luna: What does decision framing look like in practice? Is it just setting rules? Lucas: It is more structured than rules. It involves defining the boundaries of authority before the task starts. For example, instead of saying 'send me the email draft,' the manager says 'you can send any email under five hundred words as long as it includes these three data points.' You are setting the guardrails, not driving the car. Luna: So you are giving them enough rope to hang themselves if they mess up, but enough structure to stay on track. Lucas: Precisely. And it forces the employee to think through the constraints. When they operate within those guardrails, you stop micromanaging. You only intervene when they cross the line. It sounds simple, but it requires the manager to resist the urge to correct small deviations immediately. Luna: That takes a lot of patience. Most managers would jump in to fix a typo or a slightly off metric right away. Lucas: They do. And that is the trap. Every time you jump in to fix a small error, you teach the employee that their judgment isn't trusted. You reinforce the idea that the manager is the expert and they are just the hands. Over time, the employees stop thinking and start waiting for instructions. Luna: So the cost of fixing that typo is actually lower engagement and slower learning for the team. Lucas: Exactly. You are trading short-term accuracy for long-term capability. In the software case we mentioned, once the director started using decision framing, his engineers began proposing solutions he hadn't considered. They felt ownership because they had made the call within the boundaries. Luna: It is interesting how ownership changes behavior. People work harder when they feel like it is their project. Lucas: It absolutely does. But there is a second layer to this. Even if you set the guardrails, some managers still struggle to let go because they equate visibility with value. If nobody sees them working, do they matter? Luna: That is a really honest admission. I think a lot of us feel that pressure. Especially when we come from individual contributor roles where output was so visible. Lucas: It is a hard transition. The metrics change. You can no longer count lines of code or closed tickets. You have to measure influence. And influence is quieter. It shows up in fewer fires, smoother processes, and better decisions made by others. Luna: How do you make that quiet work visible to upper management? If your boss only looks at immediate output, you might get penalized for stepping back. Lucas: You have to translate your leadership activities into business outcomes. Instead of reporting hours worked, you report risk mitigated or time saved. In our case study, the director tracked how many decisions were made without his input. That number went up, and his team's delivery speed increased. Luna: So he was able to show that his absence from the daily grind actually improved the bottom line. Lucas: He did. He framed it as scaling his impact. One person managing ten people is worth ten times more than one person doing ten jobs. But you have to prove that scaling is happening. Luna: That makes sense. It shifts the narrative from 'I am less busy' to 'we are more efficient.' Lucas: Yes. And efficiency is a language executives understand. Now, I want to pause here for a quick word about how this show operates. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that is literally what funds making this many of these episodes. No ads, just support from people who find value in the conversation. Luna: It is great to have that direct link to the community. It keeps the content focused on what actually helps rather than chasing clicks. Lucas: It really does. Back to the manager's dilemma. Once you have established guardrails and proven your value through efficiency, there is one final hurdle. What happens when the employee makes a mistake that crosses the boundary? Luna: This is the scary part. Because if you punish them heavily, they might go back to waiting for your approval to avoid risk. Lucas: Spot on. You have to distinguish between a stupid mistake and a brave mistake. A stupid mistake is negligence or ignoring clear guidelines. A brave mistake is trying something new within the guardrails and failing. You treat those completely differently. Luna: So for the brave mistake, you analyze it and learn from it. For the stupid one, you correct the behavior. Lucas: Exactly. If you punish the brave mistake, you kill innovation. The employee learns that the safest path is to do exactly what you say, nothing more. You want them to take calculated risks. So you ask questions like 'what did you learn?' rather than 'why did you fail?' Luna: That reframes the failure as data collection. It reduces the emotional sting and keeps the focus on improvement. Lucas: It does. And it builds psychological safety. When people know they won't be punished for experimenting within bounds, they solve problems faster. They don't waste weeks escalating a minor issue to you because they are afraid of being wrong. Luna: That escalation delay is another hidden cost of over-management. Everyone waits for permission while the clock ticks. Lucas: And in fast-moving markets, that delay can be fatal. Your competitors are moving because their teams are empowered to act. You are waiting for your manager to nod. Luna: So the goal is to create a team that can operate independently, but still aligns with the broader strategy. Lucas: Alignment is key. The guardrails ensure alignment. The autonomy ensures speed. You are balancing control with freedom. It is not easy, but it is the only way to scale leadership effectively. Luna: It feels like a lot of trust upfront, but the payoff is a self-sustaining team. Lucas: It is. And eventually, you become the architect of the system, not the builder. You design the guardrails, coach the players, and then watch the game unfold. It is a different kind of satisfaction, but often more lasting. Luna: I like that image. Architect vs. Builder. It gives a clearer picture of the role shift. Lucas: Try visualizing it. Next time you pick up a task your team could do, ask yourself if you are acting as an architect or a builder. If you are building, you might be holding back their growth. Luna: That is a useful mental check. It stops the impulse to jump in and forces a moment of reflection. Lucas: Exactly. One moment of reflection can save hours of rework later. It also signals to your team that you trust their judgment. That signal is powerful. Luna: Trust is the currency of leadership. If you spend it wisely, you get returns in loyalty and performance. Lucas: Well said. So, as you head into your week, consider where you are currently building versus where you should be designing. Where can you hand over the reins without losing sight of the destination? Luna: It is a challenging balance, but one worth striving for. Thanks for breaking it down, Lucas. Lucas: Anytime. Let us know which area you plan to delegate first.