Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Hoards Credit
Transcript
- Lucas: So, Luna, let me ask you something. Have you ever had an employee who, every time the team ships something great, their name is all over it, and the rest of the team is basically invisible? Luna: Oh, I've seen that. It's the exact opposite of the quiet achiever. It's almost like they've got a spotlight built into their badge. Lucas: Right. And it's a tricky one for managers because, on the surface, they're not doing anything wrong. They're sharing results, they're being visible, they're celebrating wins. But what they're actually doing is slowly draining the motivation out of everyone else. Luna: So what do you do? Do you call them out in front of the team? Do you start correcting the record every time? Lucas: Let's back up a second. Because the worst move is to make it a public shaming. You'll get compliance, maybe, but you'll also get a very resentful employee who now feels like they have to defend their reputation. The better approach is a private, structured conversation that gets at the root of why they're doing it. Luna: And what is the root? Is it just ego? Lucas: Sometimes, but more often it's anxiety. They're worried that if they don't claim the visibility, their work won't be noticed. Or they genuinely don't realize they're leaving teammates out because they're so focused on the outcome. Luna: I've seen that. One of my old teammates would present a project and say 'I did this' and 'I solved that' — but they honestly believed they were the only one who did anything. They'd never once asked the others what they contributed. Lucas: Exactly. So the first step is to figure out which category your person falls into. Is it fear of being overlooked, or is it a genuine blind spot? You can't have the same conversation for both. Luna: How do you tell the difference? Lucas: Watch their reaction when you ask a simple question like, 'Who else contributed to this?' If they can rattle off names and specifics, it's probably a blind spot. If they get vague or defensive, it's probably fear. Luna: Okay, so you've diagnosed it. What's step two? Lucas: Step two is the conversation itself. And the key is to make it about team effectiveness, not about their character. You're not saying 'You're a credit hog.' You're saying 'When the team sees that everyone's contributions are recognized, we get more of that behavior.' Luna: And you're also modeling the behavior you want, right? Like, if you as the manager are always giving credit to the team, they see that that's the norm. Lucas: That's a great point. Actually, research on team dynamics shows that managers who consistently share credit publicly see their teams innovate more and collaborate better. It's not just about fairness, it's about performance. Luna: So what does the actual script sound like? Give me the words. Lucas: You start with a specific example, not a general complaint. Something like, 'In the kickoff meeting yesterday, you mentioned the new dashboard launch and you said 'I' several times. I know you did a lot of work on that, but Maria and Dev also spent significant time on it. What would it look like to include them in that narrative next time?' Luna: That's direct but not accusatory. I like that. And what if they push back and say 'I did do most of the work'? Lucas: Then you ask a follow-up: 'What did Maria and Dev contribute?' And you let them answer. Often they'll pause and say, 'Well, they did the data pull.' And you say, 'Right, so how do we make sure that's acknowledged too?' Luna: And if they still don't get it? Like they keep saying 'Yeah, but I'm the one who put it all together.' Lucas: Then you escalate the consequence. You say, 'When teammates feel their contributions are invisible, they're less likely to go the extra mile. And that directly affects our team's output. So this isn't just about recognition, it's about our results.' Luna: That's a strong frame. It moves it from 'you're being rude' to 'you're hurting the business.' Lucas: Exactly. And then you set an expectation. You say, 'Going forward, I'd like you to name at least two teammates in any project update you give. And I'll do the same when I talk about our work.' Luna: So you're making it a habit, not a one-time apology. Lucas: Right. And you follow up. After the next project, you check in and say, 'I noticed you mentioned Priya and Sam in your update. Nice.' Positive reinforcement works better than another lecture. Luna: Okay, but what if it's a pattern that's been going on for months and the team is already resentful? Is there a point where you need to do a team-level reset? Lucas: Absolutely. If the damage is done, you might hold a team meeting where you talk about recognition norms. Not pointing fingers, but saying, 'I want to make sure we're all acknowledging each other's contributions. What does that look like for us?' Luna: And you can also start doing shout-outs at the start of your one-on-ones, or in team meetings, to rebalance the narrative. Lucas: Exactly. And you have to be careful not to overcorrect by ignoring the credit-hoarder's actual contributions. They might start to feel punished. You still want to recognize their work, just in a way that's shared. Luna: Yeah. I've seen managers go too far the other way and end up with a new problem — the employee who feels invisible because they never get credit for anything. Lucas: So it's a balancing act. And it's worth getting right, because the cost of getting it wrong is real. A study from a few years back found that in teams where credit wasn't fairly shared, turnover risk went up by nearly 40 percent over two years. Luna: Forty percent. That's huge. So this isn't just a soft-skill issue, it's a retention issue. Lucas: Exactly. And that's why it's worth doing the work. You're protecting your best people from quietly checking out. Luna: And you know, this whole conversation reminds me of why we do what we do here at Fexingo. We're all about helping people navigate the messy parts of work, not just the resume-building parts. Lucas: Absolutely. And we keep these episodes free because we believe that good management advice shouldn't be locked behind a paywall. If you've found value in what we do, and you want to help us keep it that way, you can support us at buy me a coffee dot com slash fexingo. It's a simple way to say thanks, and it genuinely helps us keep putting out these conversations. Luna: Yeah, even a small gesture goes a long way. And we really appreciate it. Lucas: So, back to the credit-hoarder. One last piece: you also want to check your own behavior. Are you, as the manager, accidentally encouraging this? Like, do you only ever praise that one person in meetings? Luna: That's a tough question to ask yourself. But it's important. Because if you're the one giving them all the spotlight, you're part of the problem. Lucas: Right. And once you fix that, you create the conditions for the whole team to share credit naturally. It's not about policing every sentence, it's about building a culture where recognition flows freely. Luna: So what's the takeaway for a manager who's dealing with this right now? Lucas: First, diagnose: is it fear or blind spot? Second, have a private, specific conversation that links credit-sharing to team results. Third, model the behavior yourself and reinforce progress. And fourth, if the pattern is entrenched, reset the team norms around recognition. Luna: And remember, the goal isn't to humiliate the credit-hoarder, it's to help them become a better teammate and a better leader. Lucas: That's exactly right. And that's what separates a manager from a boss. A boss corrects behavior. A manager develops people. Both things happen, but the intention is key. Luna: Well said. Next week, we'll dig into another tough management moment. Until then, keep building those 1-1s.