Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why Managers Fail At Handing Over Leadership
Transcript
- Lucas: There is a specific kind of panic that sets in about six months after someone gets promoted to their first real management role. It isn't the panic of not knowing what to do. It's the panic of realizing that the skills which made them successful as an individual contributor are now actively hurting their team. Luna: Right. The very thing that got them hired is now the bottleneck. They know how to solve the problem, so they just solve it themselves. Lucas: Exactly. And we call this the hero complex. The new manager looks at a stalled project, a frustrated client, or a buggy codebase, and their instinct is to jump in and save the day. But in doing so, they send a clear message to the team: your judgment doesn't matter, my judgment does. You don't own this outcome; I do. Luna: It creates a dependency loop where the team stops thinking critically because they know the manager will eventually clean up the mess. So the manager ends up working eighty hours a week while their direct reports watch from the sidelines. Lucas: Precisely. And the tragedy is that the manager thinks they are demonstrating value by being indispensable. But leadership isn't about being the smartest person in the room anymore. It's about making the room smarter than you are. When you keep the context, you also keep the accountability. And if you keep the accountability, you can never truly scale. Luna: So how do you break that habit? Because it feels good to fix things. It provides immediate dopamine compared to the slow grind of coaching someone else through the same problem. Lucas: The shift has to be intentional. You have to move from being the player to being the coach. And that means sitting with discomfort. You have to let the team make mistakes that aren't catastrophic. Most new managers intervene too early because they can't tolerate the friction of others learning. But without that friction, there is no growth. Luna: I see this all the time in tech teams. The senior engineer gets promoted and suddenly becomes the sole reviewer for every pull request. The rest of the team just waits for permission to merge. Lucas: That is a classic example. The manager becomes the single point of failure. If they get sick, the whole pipeline stops. That is not a scalable operation. It is a fragile one. And investors, executives, and even the employees themselves can smell that fragility. It signals that the leader hasn't actually built a system; they've just built a crutch. Luna: But isn't there a risk? If you step back, you might lose control over quality. How do you ensure standards don't drop just because you're trying to delegate? Lucas: Good question. The answer lies in pre-work, not post-work. You don't delegate by throwing a task over the fence and hoping for the best. You delegate by defining the constraints, the resources, and the success criteria upfront. Once those are set, you step out of the execution lane. You only check in on the milestones, not the minutiae. Luna: So it's less about watching them work and more about auditing the framework you gave them. If the output is bad, you look at the instructions, not the worker. Lucas: Spot on. And that requires a level of discipline that most people don't practice until they're burnt out. They want to micromanage because it feels safer. But safety is not a strategy. Scalability is a strategy. You have to choose which one you are building right now. Luna: It's funny how often managers confuse busyness with productivity. Being busy fixing fires makes you feel important, but it actually prevents the fires from being extinguished permanently. Lucas: Firefighting is reactive. System-building is proactive. The best managers spend their time designing processes that prevent the fire from starting in the first place. They create checklists, automation, and clear decision-rights matrices. It's boring work. It doesn't look heroic. But it keeps the lights on. Luna: And it takes the pressure off the manager to be the genius. They become the architect instead of the bricklayer. That's a much healthier way to spend a career. Lucas: It is. And it changes the dynamic of performance reviews entirely. Instead of saying, 'You did great on this specific ticket,' you can say, 'You improved the entire workflow for the next ten tickets.' That is the difference between contributing and leading. Luna: I think a lot of people stay stuck in that contributor mindset because it's comfortable. They know exactly what to do. Leading is ambiguous. It involves dealing with other people's insecurities and motivations, which is messy and unpredictable. Lucas: Ambiguity is the price of admission for higher levels of responsibility. If you want more money, more impact, and more influence, you have to accept that ambiguity. You cannot manage a team of ten people by applying the exact same tactics you used when you were managing zero people. The math doesn't work. Luna: So the metric for success shifts from personal output to team output. You measure yourself by what they achieve, not what you achieve. Lucas: Yes. And that requires trust. A lot of new managers lack trust. They assume their team will cut corners or miss details unless they hover. But hovering kills trust. It tells the employee, 'I don't believe you can handle this.' So you have to start small. Delegate low-stakes tasks first. Build confidence on both sides. Luna: Start small, build trust, then expand the scope. It sounds simple, but it's hard to execute when you're under pressure to deliver quarterly results. Lucas: Pressure amplifies old habits. When the deadline is tomorrow, the temptation to take over is overwhelming. That is why you need to establish norms before the crisis hits. You need to tell your team, 'I am stepping back on this. I expect questions, but I do not expect me to write the code.' Set the expectation early. Luna: Communication is key. If you don't explain why you're stepping back, people think you're checking out or abandoning ship. You have to frame it as empowerment, not abdication. Lucas: Absolutely. You are empowering them to own the outcome. And that ownership is what drives engagement. People don't leave jobs; they leave roles where they feel powerless. If you give them power, you retain talent. Luna: That's a huge lever for retention. Empowerment is cheaper than bonuses and it lasts longer. It's intrinsic motivation versus extrinsic rewards. Lucas: Intrinsic motivation scales. Extrinsic rewards hit diminishing returns very quickly. If you pay someone extra to do something they hate, they'll do it for a while. If you give them ownership of a problem they care about, they'll figure it out. That is the secret sauce of high-performing teams. Luna: It really comes down to letting go of the ego. Admitting that you are not the hero, and that your job is to make heroes out of everyone else. Lucas: That is the hardest part. For many high performers, their identity is tied to being the solver. Letting go of that identity is a form of grief. They have to mourn their own indispensability to become effective leaders. Luna: Mourning your own indispensability. That is a profound way to put it. It's basically professional rebirth. You die as the star player and are born as the coach. Lucas: Rebirth. Yes. And once you make that shift, everything changes. Your calendar opens up. Your stress drops. And your team starts moving faster than you ever could alone. You stop being the ceiling and start being the floor. Luna: Becoming the floor that supports the whole structure. That's a much better legacy than being the ceiling that limits their growth. Lucas: Exactly. So if you're in that transition right now, ask yourself: am I solving the problem, or am I solving the process? One keeps you busy. The other builds a company. Luna: If we've helped you think through a career move or decision, and you want to support independent business journalism, honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Just a quick note that listener support is what keeps this show ad-free and allows us to keep digging into these topics deeply. Lucas: Thank you. And it’s interesting to note that this dynamic isn't just limited to corporate offices. Even in creative fields, directors who try to edit every frame end up exhausting their crews. The principle remains the same across industries. Luna: Whether it's software, marketing, or manufacturing, the bottleneck is almost always the person at the top who refuses to share the load. Lucas: Right. And the solution is always the same: define the boundary, grant the authority, and then get out of the way. It’s simple, but it is rarely done well. Luna: Because it requires patience. And patience is a scarce resource in a world that rewards speed. Lucas: Speed without direction is just motion. Direction without delegation is burnout. You need both, and you need to trust your team to help you find that balance. Luna: So the question for this week isn't just what you accomplished. It's what your team accomplished because you stepped back. Lucas: A powerful reframe. Look at your calendar this week. Where did you insert yourself unnecessarily? And where could you have trusted the process instead?