Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / When Top Performers Become Bad Managers
Transcript
- Lucas: We've all seen it happen. The company's best software engineer, the one who could debug anything in half the time, gets promoted to engineering manager. Six months later, the team is slower, morale is down, and the engineer is miserable. Why does this keep happening? Luna: It's the classic Peter Principle — people rise to their level of incompetence. But I think there's more to it than that. It's not that they become incompetent; it's that the job fundamentally changes. Lucas: Exactly. The skills that made you a star individual contributor — deep technical expertise, personal productivity, the ability to dive into code — are almost entirely different from the skills you need as a manager: coaching, delegation, conflict resolution, strategic thinking. Luna: And yet most companies promote based on past performance, not management potential. I read a study that said less than 30% of first-time managers receive any formal training before stepping into the role. Lucas: That stat tracks with what I've seen. I want to use a specific example today. A mid-sized fintech company — we'll call it PayBridge — had a star engineer named Priya. She'd been at the company for four years, shipped three major features, and was the go-to person for architectural decisions. Lucas: Leadership decided to promote her to engineering manager of a team of six. No training, no transition plan, just a new title and a bigger paycheck. Within three months, her team's velocity dropped by 40%. Luna: Forty percent — that's huge. Was it because she was trying to do everything herself? Lucas: Partly. She couldn't stop coding. She'd still jump into pull requests, rewrite chunks of code, and make architectural decisions without consulting the team. Her team felt disempowered and micromanaged. But also, she was overwhelmed by the people side — performance reviews, one-on-ones, conflict between team members. Luna: So she doubled down on what she knew — the technical work — and neglected everything else. That's a common trap. Lucas: Right. The thing is, Priya's story is not unique. Google's Project Oxygen study — which analyzed thousands of manager reviews — found that the number one trait of effective managers wasn't technical expertise. It was being a good coach. Luna: A good coach. That means asking questions, not giving answers. Helping the team solve problems rather than solving them yourself. Lucas: Exactly. And that's a skill that has to be learned. It doesn't come naturally to someone who's spent years being rewarded for having the right answer quickly. Luna: So what did Priya do? Did she turn it around? Lucas: She did, but it took a wake-up call. Her manager sat her down after the third month and showed her the data — the velocity drop, the team satisfaction survey scores. That was the moment she realized she couldn't keep doing the same thing. Lucas: She started with three things. First, she stopped writing code altogether for two weeks. She literally blocked her own access to the production repository. That forced her to delegate. Luna: Wow, extreme measure. But I bet it worked. Lucas: It did. She started holding proper one-on-ones — not status updates, but coaching conversations. She asked her team members what they wanted to learn, where they were stuck. And she began assigning ownership of entire features to individuals instead of keeping the critical path for herself. Luna: That's the shift from individual contributor mindset to multiplier mindset. Your success is no longer measured by your own output, but by the output of your team. Lucas: Exactly. And it took about six months, but her team's velocity not only recovered — it exceeded where it had been before the promotion. The team became more autonomous, and Priya actually started enjoying her job again. Luna: So what's the lesson for first-time managers listening right now? What's the concrete takeaway? Lucas: I'd say three things. One: in your first 90 days as a manager, your primary job is to stop doing the work yourself. Resist the urge. If you're still the top coder, you're not managing. Luna: That's hard because you're good at it, and it feels productive. Lucas: It feels productive, but it's actually destructive. Two: invest in coaching skills. Read up on the SBI model — situation, behavior, impact — for giving feedback. Practice active listening. Your team will forgive you for not knowing every technical detail if you genuinely help them grow. Luna: And three? Lucas: Three: get a mentor who has been through the transition. Priya's turnaround accelerated when she started meeting weekly with a senior manager in another division. Someone who could tell her, 'Yes, it's normal to feel like you're failing. Here's what I did.' Luna: I think that's key. The isolation of that first management role is real. You can't vent to your team, and your old peers now report to you. Having that external sounding board is huge. Lucas: Absolutely. Now, I want to push back on something. Some people argue that the Peter Principle is inevitable — that eventually everyone gets promoted one level beyond their competence. But I don't think that's true. Luna: Because with the right support and mindset, people can grow into the role. Lucas: Right. The problem isn't the promotion itself. It's the lack of a transition plan. Companies that invest in a proper ramp — a first 90 days curriculum, a peer cohort of new managers, regular coaching from a senior leader — see much higher success rates. Luna: I've also seen companies use a 'trial period' where the promoted person manages a small project first, to test the waters. That can work. Lucas: That's a smart approach. But the reality is, most companies don't do that. So as an individual, you have to take ownership of your own transition. If you're about to become a manager, or if you've just been promoted, start building your support system now. Luna: And if you're already in the role and feeling like Priya did — drowning and tempted to go back to what you know — it's never too late to course-correct. She did. Lucas: Exactly. So here's my closing thought: the best managers I've seen are the ones who treat management as a craft to be learned, not a reward for past performance. If you approach it with humility and curiosity, you won't just avoid the Peter Principle — you'll build a team that makes you look good. Luna: And that's the real goal, isn't it? To make the team better than you ever were alone. Lucas: That's it. Thanks for listening. We'll be back next week with another episode of Manager Mondays.