Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Is Better Than You
Transcript
- Lucas: So here's a situation that I think every manager eventually hits — and it's one of the most quietly uncomfortable things you can face on the job. Luna: I'm already nervous. What is it? Lucas: You're managing someone who is genuinely better at the work than you are. Like, they code faster, they close more deals, they have deeper client relationships, they think more strategically. And you're supposed to lead them. Luna: Oh, that's a gut punch. And I think it's more common than people admit. Especially for first-time managers who got promoted because they were the best individual contributor. Lucas: Exactly. You were the top performer, so they made you manager. But now you're overseeing someone whose technical skills or raw talent outshine yours. And the natural instinct is either to micromanage to prove you're still in charge, or to withdraw and let them run wild because you feel like a fraud. Luna: Both are bad. I've seen the withdrawal version more often — the manager just stops giving any guidance because they're intimidated. And the employee feels abandoned. Lucas: Right. So there's a classic case from film history that I think illustrates a better way. When Pixar was making Toy Story in the mid-90s, there was a young producer named Ralph Guggenheim who was put in charge of a team that included some of the most brilliant animators and technical directors in the world — people who had been in the industry for decades. Luna: And Guggenheim had never directed a feature film before, right? Lucas: Correct. He was a producer, not an animator. He couldn't out-draw anyone on his team. But he understood that his job wasn't to be the best animator — it was to build the environment where those geniuses could do their best work. He focused on removing obstacles, getting them the right software, managing the schedule so they had creative space, and protecting them from studio interference. Luna: So he shifted from 'I need to be the smartest person in the room' to 'I need to make the smartest people in the room as effective as possible.' That's a whole different job description. Lucas: That's exactly the reframe. And I think there are three concrete moves that make that work in practice. The first one is what I call 'active delegation of authority.' Not just delegation of tasks — that's the easy part. You give them decision rights over the things they're best at. You say, 'You own the technical architecture. I don't need to approve your design choices — I just need to know what you decided and why.' Luna: But that's scary for a lot of managers. You're essentially giving up control. What if they make a mistake? Lucas: Then you support that mistake. You own it as a team. But the key is you don't second-guess them in real time. If you start picking apart their work because you think you could do it better, you undermine their confidence and you prove that you don't actually trust them. And they'll feel it instantly. Luna: So the first move is give them real decision authority. What's the second? Lucas: The second move is publicly crediting them — specifically in front of your boss and their peers. This is counterintuitive because a lot of managers worry that if their employee looks too good, then the manager looks irrelevant. But the research is pretty clear that the opposite is true. When you consistently shine a spotlight on your team's talent, you build a reputation as a manager who develops stars. Luna: Right, you become known as someone who attracts and grows great people. That's way more valuable than being known as the person who personally wrote the best code. Lucas: Exactly. So in a staff meeting, you say, 'I want to highlight Sarah's work on the Q3 forecast — she caught a revenue risk that I completely missed, and her analysis saved us from making a bad call.' That makes you look secure and smart for hiring her. The third move is the hardest for most people: you actively seek their input on your own decisions. Luna: Ooh, that's humbling. You're basically saying, 'I'm not the expert here — teach me.' Lucas: Yeah. You go to them and say, 'I'm thinking about restructuring the team's sprint cadence. You've got more hands-on experience with this than I do — what am I missing?' And then you genuinely listen and incorporate their feedback. That doesn't weaken your authority — it actually strengthens it, because it shows you're confident enough to learn from anyone. Luna: But there's a psychological barrier here. I think a lot of managers feel a kind of quiet resentment — like, 'Why am I managing them if they're the one with all the answers?' How do you deal with that internally? Lucas: I think you have to separate your identity from your technical skill. Your value as a manager isn't in being the best coder or the best salesperson — it's in being the best at building a team that can code or sell better than anyone else. That's a different muscle. And if you can't make that shift, you'll either burn out trying to compete with your own team, or you'll leave management altogether. Luna: So it's almost like managing your own ego is part of the job. You have to be okay with not being the star. Lucas: Exactly. And I'll tell you a quick personal story. Early in my career, I managed a data analyst who was just — she was incredible. She could spot patterns in data that I would never see. And at first, I felt this weird anxiety every time she presented something. I thought, 'What am I even adding here?' But then I realized I was the one who got her the budget for the tools she needed, I shielded her from three different stakeholders who wanted conflicting reports, and I made sure her work got seen by the VP. That was my contribution. Luna: You were the shield and the amplifier. That's actually a really important role. Lucas: Yeah. And once I embraced that, the resentment just dissolved. I was proud of her success because I had a hand in making it possible. So let me wrap up the three moves: delegate real authority, publicly credit their work, and ask for their input on your own decisions. That combination builds a dynamic where you're not competing — you're partnering. Luna: And I'd add one more thing: be honest about it with them. You don't have to pretend you're the expert. You can say, 'Look, you're the best engineer on this team. My job is to clear the path for you. If I ever get in your way, tell me.' That kind of candor builds massive trust. Lucas: Absolutely. And you know, it's funny — if we've helped you think through a situation like this, or any career move really, I want to mention something quickly. This show is completely listener-supported, no ads, no sponsors. And a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo. That's literally what keeps us making episodes like this one. Luna: Yeah, it's a small group but it makes a huge difference. And it keeps the show exactly what it is — just us having real conversations about management, no commercial breaks. Lucas: Right. So back to the main thread — I think the ultimate test of whether you've mastered managing someone better than you is whether they feel safe telling you when you're wrong. Because if they do, you've built a relationship based on mutual respect, not hierarchy. Luna: And that's when the team really starts to outperform. When the manager isn't the bottleneck. Lucas: Exactly. So next time you're in a one-on-one with that star player, ask yourself: did I clear something out of their way today? If the answer is no, that might be where you should start tomorrow.