Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Hogs the Spotlight
Transcript
- Lucas: You know that team member who always seems to be standing in the spotlight, even when the work was a group effort? The one who pipes up first in the all-hands to recap the project — and somehow forgets to mention the three other people who did half the work. Luna: Oh, I think everyone has worked with that person. Or at least seen one from across the org chart. It's one of those dynamics that can quietly poison a team if you don't address it. Lucas: Exactly. And today I want to get specific about why it happens and what you actually do about it as a manager. Because the instinct is often to assume bad intent — that this person is a narcissist or a ladder-climber. But a lot of the time, it's something more fixable. Luna: Like what? Lucas: Insecurity, for one. Or a reward system that's accidentally incentivizing individual visibility over team outcomes. I was looking at some research from Adam Grant's book 'Give and Take' — he cites a study where teams with one chronic credit-taker performed about 30 percent worse on collaborative tasks, even if that person was individually talented. Luna: That's a huge drag. And it makes sense — because other people start pulling back. Why go the extra mile if your contribution is going to get erased in the next stand-up? Lucas: Right. So let's ground this in a real example. I was talking to a manager at a mid-stage fintech company — about 200 employees — and she had a senior analyst named Priya. Priya was technically excellent. Caught errors no one else saw, delivered clean models, met every deadline. But she had this pattern: in quarterly review meetings, she'd present the team's findings, and she'd say things like, 'I discovered that the churn rate was actually...' when the discovery was a group effort. Luna: Oof. I've seen that exact move. And the manager is stuck, because if she confronts Priya too hard, she risks losing a star performer. But if she does nothing, the rest of the team starts to check out. Luna: And honestly, if this episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It's how we keep the show ad-free and focused on real management challenges like this one. Lucas: Yeah, listener support makes a big difference. And we're grateful for anyone who throws in a couple bucks. Alright, back to Priya. The manager's first move was a private one-on-one she called an 'impact audit.' Basically, she sat down with Priya and said, 'I want to walk through the last quarter and map out who did what.' No accusation, just data. Luna: So she fact-checked the credit allocation in real time, with Priya in the room. That's brave. How did Priya react? Lucas: Initially, defensively. She said, 'Well, I led the analysis.' And the manager said, 'You did lead it — and you also had two juniors running the SQL queries and a designer building the dashboard. When you say 'I discovered,' it erases their fingerprints.' The manager was calm but precise. She didn't say Priya was wrong; she showed the gap between Priya's language and the actual division of labor. Luna: That's the intent versus impact framework, right? Priya probably didn't mean to exclude people. She was just excited or anxious to prove her value. But the impact was real. Lucas: Exactly. The manager framed it exactly that way. 'I know your intent isn't to take sole credit, but the impact on the team is that they feel unseen.' And she gave a specific behavioral ask: 'In the next presentation, I want you to start by naming the contributors. Say 'Sarah and James pulled the data, Maria designed the viz, and I synthesized the findings.' Luna: That's concrete. And it's hard to argue with. But I wonder — did Priya actually follow through? Lucas: She did, mostly. The manager checked in after the next quarterly review, and Priya had scripted her opening. It wasn't perfect — she still tended to revert to 'I' when she got nervous — but the shift was noticeable. The manager also made a structural change: she started rotating who presented the team's work in all-hands meetings. Priya still got her turn, but so did other team members. Luna: That's smart. Because it takes the burden off Priya to be the sole representative. And it signals to the whole org that this is a team, not a one-person show. Did the team notice? Lucas: Yeah, within a month. One of the juniors told the manager, 'I finally feel like my work is being seen.' That's the win. The manager didn't publicly shame Priya, she didn't write her up. She just created a system where visibility was more distributed, and gave Priya a clear, low-stakes way to adjust. Luna: I've got a story from my own past that's the inverse. I once had a boss who would, in team meetings, say things like, 'Luna came up with this approach,' even when I was just executing his idea. He was actively giving me credit I didn't fully deserve. At first I felt awkward, but then I realized he was modeling how to spread the spotlight. Lucas: That's a great example of leadership by design. He was probably aware that senior people naturally absorb credit, so he overcorrected. What did that do for the team culture? Luna: It made people generous. When you see your boss handing off praise, you start doing it too. Within a few months, our stand-ups became a round-robin of 'shout-outs.' It felt genuine, not forced. Lucas: That's the ideal end state. But for a manager dealing with a Priya today, you don't have months to wait. So let me give a third move that complements the impact audit and the rotation: specific feedback in the moment. Not in the meeting itself — don't embarrass them — but in a follow-up message within 24 hours. Luna: Like what? A quick Slack? Lucas: Yeah, or an email. Something like, 'Hey, great job in the presentation. One thing I noticed: when you said 'I built the model,' I know you and Alex paired on it. Next time, maybe say 'Alex and I.' Short, private, no judgment. Done repeatedly, it rewires the habit. Luna: I like that because it's low-friction. And it gives the person a chance to correct without losing face. But what about the case where the spotlight-hogger is actually your highest performer? Do you handle it differently? Lucas: Interesting question. I think the core moves stay the same — audit, rotate, give micro-feedback — but you might need to address the underlying anxiety. High performers often hog credit because they're terrified that if they don't, their contribution will be invisible come promotion time. So you can proactively say, 'I see your work. You don't need to claim it loudly for me to know. And I'll make sure leadership knows too.' Luna: That's reassuring. Because the worst outcome is that you correct the behavior but the person feels punished for being good at their job. You want them to keep their drive, just channel it more collaboratively. Lucas: Exactly. And the research backs that up. When people feel their competence is recognized, they're less likely to grab for visible credit. So the manager's job is to make psychological safety and recognition abundant enough that no one feels they have to hoard it. Luna: Alright, I want to zoom out for a second. Is there a scenario where the spotlight-hogger is just toxic and no amount of coaching can fix it? Lucas: Sure. If they're aware of the impact, you've given clear feedback multiple times, and they still do it — that's a values mismatch. At that point, it's a performance issue, not a coaching issue. You'd move to a formal performance improvement plan. But I'd say 80 percent of these cases are fixable with the three moves we talked about, especially if you catch it early. Luna: So start with the impact audit, rotate presentation ownership, and deliver micro-feedback in private. That's a solid playbook. One last thing — what if the spotlight-hogger is your peer, not your direct report? Lucas: That's a whole other episode. But short answer: you can't do the audit or the rotation. You can only do the micro-feedback, and you have to be more diplomatic. Something like, 'Hey, when you presented the Q3 results, I noticed you mentioned your team's work but didn't mention the ops team that also contributed. I think it would go over well if you included them next time.' Luna: That's good. It frames it as helpful advice rather than criticism. Alright, I think we've given managers a lot to work with. My big takeaway: don't assume bad intent, but don't let it slide either. The team is watching. Lucas: Exactly. And the team's trust is harder to rebuild than any one person's ego is to manage. Thanks for listening, everyone. We'll be back next Monday with another real management challenge.