Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Hoards Knowledge
Transcript
- Lucas: You've got a senior developer on your team who knows every inch of the legacy codebase. When anyone asks how to fix a bug, she fixes it herself overnight. But she never documents the fix, never explains what she did, and the rest of the team stays dependent on her. Luna: I've seen that exact person. And everyone on the team breathes a sigh of relief that she's there — until she goes on vacation and nobody can deploy. Lucas: Right. And as a new manager, you might think, well, she's productive, she's engaged, what's the problem? But the problem is single point of failure and stunted team growth. So today we're going to talk about how to manage a team member who hoards knowledge — without making them feel punished for being good at their job. Luna: Before we go deep — Lucas, I want to say, if you've ever found yourself nodding along to these scenarios, and this show helps you figure out how to handle them, consider supporting us. It's listener-supported, no ads, and it really does keep us going. You can do that at buy me a coffee dot com slash fexingo. Lucas: Yeah, and it's a small thing that makes a big difference for us. So back to our knowledge hoarder. First step: diagnose the why. Because knowledge hoarding almost never looks the same. Luna: Give me a few categories. I'm guessing it's not always malicious. Lucas: Not at all. I'd say there are three common drivers. One: job insecurity. They worry that if they share everything, they become expendable. Two: perfectionism. They don't think anyone else can do it as well, so they'd rather just do it themselves. Three: lack of incentive. The company has never rewarded sharing, and it's actually faster for them to just do the work. Luna: And each one probably needs a different response, right? Insecurity versus perfectionism versus lack of reward. Lucas: Exactly. If it's insecurity, you need to build trust. You might say, 'I'm not asking you to give away your expertise. I'm asking you to help the team grow so we can all take on bigger challenges — and that makes you more valuable, not less.' Luna: But if it's perfectionism, that's almost the opposite problem. They think nobody can do it right, so they might need to see that a decent solution from someone else is actually good enough. Lucas: Right. And the third one — lack of incentive — is the easiest to fix structurally. You build documentation or knowledge transfer into their goals. You give them credit for it in performance reviews. You publicly acknowledge when they teach someone else. Luna: So step one is diagnose. What's step two? Lucas: Step two: create low-risk sharing opportunities. Don't put them on the spot in a big meeting and say, 'Hey, can you explain the database schema to everyone?' That's a recipe for defensiveness. Instead, ask them to pair with one junior person for an hour on a specific task. Or ask them to write a short internal how-to guide — just for one process. Luna: Make the ask concrete and bounded. I like that. 'Hey, could you show Sarah how to run that report? It'll take you fifteen minutes.' Not 'please train the team on everything you know.' Lucas: Exactly. And after that first small success, you celebrate it. You say, 'That report you showed Sarah? She ran it herself and it saved us an hour. Thank you for making that happen.' That starts to wire in the new behavior. Luna: But what if they push back? What if they say, 'It's faster if I just do it' or 'She's not ready to handle that alone'? Lucas: Then you name the trade-off explicitly. You say, 'I know it's faster for you to do it yourself right now. But every time you do it alone, the team stays dependent on you. My job is to make sure the team can operate without any single person being a bottleneck — including you. So I need us to invest that time now so we can all move faster later.' Luna: That's direct. And it frames it as a leadership priority, not a criticism of their work. Lucas: Step three: redesign the reward system. If your organization only rewards individual heroics — the person who fixed the late-night outage, the salesperson who closed the biggest deal — then you're incentivizing hoarding. You have to systematically celebrate collaboration and knowledge sharing. Luna: Give me a concrete example. How do you do that in practice without a whole cultural overhaul? Lucas: Start small. In your one-on-ones, ask, 'Who on the team did you help this week?' If they say, 'I helped so-and-so debug a problem,' note it. Mention it in team stand-ups. In performance reviews, include a section on 'knowledge contribution.' If you're in a company that gives bonuses or spot awards, nominate them specifically for teaching someone else. Luna: I've also seen managers set aside a 'learning hour' each week where someone presents something — and you rotate who presents. That normalizes sharing without making it feel like a burden. Lucas: Great idea. And you can pair that with a 'documentation day' once a sprint, where the whole team updates wikis or writes guides. That way the knowledge hoarder isn't singled out — it becomes a team norm. Luna: One more nuance: what about the person who genuinely has intellectual property concerns? Like they've developed a proprietary method and they're afraid it'll get misused or they won't get credit. Lucas: That's a legitimate concern, and you need to treat it seriously. You can set up a system where they retain authorship credit — like a named process or a document that says 'developed by so-and-so.' Also, you can create a formal handoff process with sign-offs, so they feel their work is protected. Luna: So it's not about forcing them to dump everything they know into a shared drive. It's about finding a structure that works for them and the team. Lucas: Exactly. And remember, some knowledge actually does require context and experience to use properly. The goal isn't to turn them into a library — it's to lower the bus factor and build a learning culture. Luna: What's the biggest mistake new managers make with knowledge hoarders? Lucas: Two things. One: they ignore it and hope it resolves on its own. It never does. Two: they confront the person aggressively, saying things like 'You're a bottleneck' or 'You're not a team player.' That kills trust and makes the person even more defensive. Luna: So the sweet spot is diagnostic, incremental, and reward-focused. Lucas: Yeah. And one more thing: be patient. If someone has been hoarding knowledge for years, they're not going to change overnight. You're building a new habit, and that takes repetition and reinforcement. Luna: Any final thought on how to know you've succeeded? Lucas: When you can take a vacation and the team doesn't miss a beat. When a junior person solves a problem that used to be the senior person's domain. That's the win. And the senior person feels more valuable because they're enabling others, not just doing the work. Luna: Alright, that's a good place to leave it. Next week we'll talk about how to manage a team member who always challenges your decisions. Lucas: Looking forward to it. See you next Monday. Luna: See you.