Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why Managers Stop Developing People
Transcript
- Lucas: The most common failure mode I see in new managers isn't bad judgment or even harshness. It is actually an inability to step back. They are promoted because they were excellent individual contributors, and they carry that identity into the role with such force that they accidentally suffocate the very team they were hired to lead. Luna: Right, the executor trap. You get promoted to fix problems, but by fixing them yourself, you stop creating space for others to grow. Lucas: Exactly. And it is subtle because on the surface, everything looks fine. The metrics are hitting, the deadlines are being met, and the manager is technically available. But if you look at the trajectory of the team, nobody is getting better at anything harder than what they did last month. They are just repeating known patterns under pressure. Luna: It feels productive in the short term, doesn't it? Like you are pulling your weight, even though you are hoarding the learning opportunities. Lucas: That is the dangerous part. A recent study from Harvard Business Review looked at high-potential individual contributors who were moved into management. About thirty percent of them struggled significantly within the first eighteen months. The primary reason was not a lack of technical skill, but a reluctance to delegate core tasks because they feared the output would be imperfect. Luna: So they are trading long-term team capability for short-term personal comfort and control. Lucas: Precisely. Let me give you a concrete example from a mid-sized software firm we analyzed last quarter. There was a senior engineer named David who got promoted to team lead after shipping three major features ahead of schedule. His instinct was to jump into the code reviews immediately. He felt that if he didn't catch every edge case himself, the product quality would drop. Luna: And did his team respond by taking more ownership, or did they wait for him to sign off? Lucas: They waited. Two junior developers stopped pushing complex tickets entirely because they knew David would just rewrite the logic anyway. Within six months, David was working eighty-hour weeks, and the two juniors were stagnant. They weren't learning architecture because David wasn't letting them make architectural mistakes. Luna: That is a classic bottleneck. David became the single point of failure for quality, which means he became the single point of failure for speed too. Lucas: Right. And here is the kicker: when the executive team asked why the team wasn't scaling, David said he was carrying the load. He didn't realize that his definition of carrying the load was preventing the team from developing its own muscles. He was managing the work, not the people. Luna: But how do you break that habit? It is hard to let go when you know exactly how to do it faster. Lucas: You have to change your success metric. If your goal is to ship feature X by Friday, you will do it yourself. If your goal is to ensure that Jane can ship feature Y independently next month, you have to let her stumble a bit this week. It requires a shift from outcome-based management to capability-based management. Luna: So you are measuring your performance by how redundant you make yourself, not by how essential you remain. Lucas: Yes. Redundancy in management is actually the gold standard. If you can take a week off and the team operates exactly as well, you have built a system. If the team collapses without you, you have built a dependency. And dependencies are fragile. Luna: That is a terrifying thought for someone who just spent years proving they were indispensable. Lucas: It is. And it gets worse because many companies reinforce this behavior. We reward the hero who stays late and fixes the bug, not the manager who documented the process so no one else has to stay late. The incentive structure is misaligned with good leadership. Luna: So new managers are punished for trying to scale their impact through others. Lucas: Punished or ignored. Usually ignored until it is too late. By the time the executive team realizes the team is capped at the manager's bandwidth, key talent has already left. In our software firm example, both juniors quit within a year. One went to a competitor where they were trusted to lead a small module. The other left the industry entirely because they felt stuck. Luna: That is a massive loss for the company. They paid for David's promotion but lost two future leaders because he couldn't let go. Lucas: And David probably felt like the victim. He was working harder than anyone else. He didn't see that his willingness to do the work was actually disempowering everyone around him. It is a blind spot that only becomes visible when you look at retention data and career progression charts. Luna: So what is the practical fix? How does a manager like David start delegating without micromanaging the delegation? Lucas: Start with the eighty-twenty rule. Identify the twenty percent of tasks that are most valuable for your direct reports to learn. These are usually the tasks that scare them slightly or require judgment calls. Then assign those exclusively to them. For the rest, you can still help, but you must frame it as coaching, not doing. Luna: Coaching instead of fixing. That means asking questions rather than providing answers. Lucas: Exactly. When a junior developer comes to you with a problem, don't give them the solution. Ask them what they think the options are. Ask them what risks they see. Guide them to the answer, but let them walk the path. It takes longer initially, but the velocity compounds over time. Luna: It feels inefficient in the moment, but it is the only way to build real institutional knowledge. Lucas: It is. And it frees you up to do the actual managerial work: removing blockers, aligning strategy, and advocating for the team. Those are things no one else can do. If you are buried in code reviews, you cannot do those higher-level functions. Luna: So the manager becomes useless to the organization because they are too busy being useful to the task. Lucas: Spot on. You become a resource consumer instead of a capacity creator. And organizations need creators. They can always hire more executors. They struggle to find people who can multiply the output of others. Luna: That multiplier effect is what separates good managers from great ones. Lucas: Absolutely. And it starts with the mindset shift. You have to accept that your team's early mistakes are investments in their future competence. Your job is not to prevent every error. Your job is to ensure the errors are low-cost and high-lesson. Luna: Low-cost errors. That is a really helpful framing. It changes how you view the inevitable hiccups. Lucas: It does. Because if you treat every hiccup as a failure, you will intervene every time. If you treat it as tuition, you can stand back and watch them pay it. Just make sure the bill doesn't bankrupt the project. Luna: So there is a balance between放手 and oversight. You need guardrails, not a cage. Lucas: Guardrails are perfect. Set clear boundaries on budget, timeline, and customer impact. Inside those lines, let them drive however they want. Outside those lines, then you step in. But most new managers set the boundaries too tight, effectively building a cage. Luna: I wonder if this is why some teams feel stifled even when the manager is nice. The niceness masks the control. Lucas: It absolutely does. A nice manager who does all the work is still a bottleneck. The team knows they are not trusted, even if the manager thinks they are helping. Trust is demonstrated through autonomy, not assistance. Luna: Autonomy is the currency of professional growth. Without it, people just exist in the role. Lucas: They exist, yes. But they don't grow. And in a competitive market, stagnation is the fastest way to lose top talent. People leave when they feel they are not becoming better versions of themselves. Luna: So the manager's legacy isn't the projects they shipped, but the leaders they created. Lucas: That is the true test. Can you point to three people on your team who are now capable of doing your job better than you could? If not, you haven't managed yet. You've just been busy. Luna: Busy is easy. Multiplying is hard. But it is the only thing that scales. Lucas: Exactly. So the challenge for every first-time manager listening today is to ask yourself: what am I holding onto that I should be handing over? What lesson is someone else ready to learn, and am I blocking it because I am afraid of looking slower? Luna: It is a tough question to sit with, especially when the quarterly goals are pressing. Lucas: They are. But remember, short-term speed achieved through burnout is expensive. Long-term capability achieved through delegation is compounding. Choose the compound interest. Luna: Compounding trust and capability. That is a much better investment portfolio. Lucas: It really is. And it requires patience. Real patience. Not the kind where you wait for the person to finish so you can correct them, but the kind where you wait for them to figure it out, even if it takes three times as long. Luna: Three times as long once, versus zero times as long forever if they never learn. Lucas: Precisely. The math works out in your favor eventually. You just have to survive the initial dip in efficiency. Luna: And that dip is the price of admission for building a real team. Lucas: It is. And once you cross that threshold, you stop being the engine and start being the chassis. The team carries itself, and you steer. Luna: A steering wheel is lighter than an engine, but it directs where the whole vehicle goes. Lucas: That is the shift. From power to direction. And that is where real leadership lives. Luna: Thanks for the perspective, Lucas. It makes me rethink my own recent project assignments. Lucas: Do that. Look for the tasks you are doing that could teach someone else something valuable. Hand them over. Watch them stumble. Watch them rise. It is the best part of the job. Luna: We deliberately don't run ads on these shows because we want to keep the conversation focused on the substance, not the interruptions. If that resonates with you, and you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: Your support helps us keep digging into these specific dynamics without needing to chase clicks or sponsors. It keeps the signal clear. Luna: Yeah, it lets us focus on the craft rather than the commerce. Thanks for keeping this ad-free. Lucas: Back to the topic though, because there is one more layer to this delegation issue. It isn't just about assigning tasks. It is about assigning context. Luna: Context. That is the piece people often skip. They give the 'what' but not the 'why'. Lucas: Right. If you hand off a task without explaining the strategic intent behind it, the employee is just following instructions. If you explain the intent, they are solving a problem. The difference between those two mindsets is huge for retention and innovation. Luna: So delegation without context is just outsourcing. Delegation with context is development. Lucas: Exactly. You have to share the business rationale. Why does this matter? Who does it help? What happens if we get it wrong? That context empowers them to make decisions when you aren't in the room. Luna: It turns them from order-takers into owners. Lucas: Owners. Yes. And owners protect the asset. Order-takers just check the box. Which one do you want on your team? Luna: Owners. Definitely. Even if they are messy owners at first. Lucas: Especially if they are messy at first. Because messy owners can be coached. Clean order-takers are dead ends. Luna: So the goal is to create enough messiness that they have to think, but enough structure that they don't crash. Lucas: That is the sweet spot. Controlled chaos. Where the stakes are real, but the safety net is visible. That is where growth happens. Luna: It sounds like a lot of work upfront, but it saves so much time downstream. Lucas: It does. And it builds a team that doesn't need you. Which, ironically, is the only way you get the freedom you actually want as a leader. Luna: Freedom through redundancy. It is counterintuitive, but it makes total sense. Lucas: It does. And that is the paradox of management. You have to work yourself out of a job to truly succeed in it. Luna: A job you never really leave, just evolve into. Lucas: Exactly. You evolve from the player to the coach to the architect. And each stage requires letting go of the previous one completely. Luna: Letting go of the ego, mostly. Lucas: Mostly. The ego wants to be the smartest person in the room. The manager wants to make the room smarter. Big difference. Luna: One creates followers. The other creates leaders. Lucas: And in the end, that is what matters. Not who is leading, but who is leading whom forward.