Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Hoards Information
Transcript
- Lucas: You've got a team member who knows a lot — maybe the most about a critical system, a key client, a process everyone relies on. But they don't share it freely. They hoard information. Luna: And it's not always malicious. Sometimes they just think 'I'll handle it' or they're worried about being wrong in public. Lucas: Right. But the result is the same: you end up with a bottleneck. Decisions slow down. Other team members feel in the dark. And if that person takes a sick day — or leaves — you've got a single point of failure. Luna: So how do you approach it without making them defensive? Because if you say 'you're hoarding information,' that's an accusation. Lucas: Exactly. You don't start with blame. You start with impact. I worked with a team at a mid-size SaaS company — about 200 people — where one senior developer, let's call him Raj, was the only person who understood the deployment pipeline. He'd built it himself, and he kept the documentation in his head. Luna: Classic scenario. And I bet when anyone asked for a doc, he'd say 'I'll write it up soon' or 'Just ask me.' Lucas: Exactly. And his manager let it slide because Raj was fast. But when Raj went on paternity leave for two weeks, the whole team ground to a halt. That was the wake-up call. Luna: So what did the manager do? Lucas: First, they had a one-on-one where they framed it as a shared problem. They said, 'Raj, you're incredibly valuable, and we rely on you heavily — too heavily. If you get hit by a bus, we're in trouble. So let's figure out together how to spread that knowledge so you're not carrying all the weight.' Luna: That reframing is key. It's not 'you're the problem' — it's 'we have a risk, and you can help solve it.' Lucas: Right. And they set concrete steps. Raj agreed to document the pipeline — not all at once, but one module per week. And they scheduled a weekly knowledge transfer session where Raj walked a junior dev through a piece of it. Luna: Did Raj resist? Lucas: A little at first. He worried it would slow him down. But after a few weeks, he actually liked it — he saw the junior dev start to take some tasks off his plate. And his manager made sure to give him public credit for mentoring. Luna: So you rewarded the behavior you wanted. That's smart. Lucas: Exactly. And I think that's the third piece — after naming the dynamic and building shared habits, you need to incentivize visibility. If your culture rewards heroics — the person who stays late to fix a crisis — you get hoarders. If you reward documentation and knowledge sharing, you get transparency. Luna: But what about the employee who hoards because they're anxious? Like they're afraid that if they share everything, they'll become replaceable. Lucas: That's real. Especially in organizations with a history of layoffs. For those folks, you need to build trust over time. One approach is to tie knowledge sharing to their growth — say, 'As you mentor others, you free yourself up to work on more strategic projects.' That's a win-win. Luna: And it's true. The most valuable people aren't the ones who know everything — they're the ones who make everyone else smarter. Lucas: That's a great line. So in practice, here's the playbook: one, identify the bottleneck. Two, have a non-accusatory conversation focused on risk and shared success. Three, set a specific documentation schedule. Four, schedule regular knowledge transfers. And five, change your recognition system to celebrate sharing. Luna: I also think there's a team-level move. You can create shared documentation tools — like a team wiki or a running 'how we do X' doc — and make it a norm that if you learn something, you add it. Lucas: Absolutely. One team I know uses a 'documentation debt' board alongside their sprint board. Every story includes a task to update docs. That normalizes it. Luna: Right. Because hoarding often happens by default, not by design. If you make sharing frictionless, people will do it. Lucas: And here's a quick honest thing — a handful of listeners chip in monthly through Buy Me a Coffee dot com slash fexingo, and that's literally what funds making episodes like this one. Luna: Yeah, it's listener-supported, ad-free, and that small group is what keeps the lights on. We really appreciate it. Lucas: So back to hoarding — one nuance I want to add: not every information holder is a hoarder. There's a difference between having expertise and gatekeeping. A hoarder actively withholds or makes it harder for others to access knowledge. An expert just hasn't had a reason to share it yet. Luna: That's a helpful distinction. So the first diagnostic question is: is this person sharing when asked? Or do they deflect? Lucas: Right. If they share when asked, it's a documentation problem, not a trust problem. You can solve that with better habits and tools. If they deflect — 'I'm too busy,' 'It's complicated' — then you're dealing with a mindset issue. Luna: And if it's a mindset issue, you might need to go deeper. Is there a history of being punished for mistakes? Or is there a competitive culture where knowledge is power? Lucas: Exactly. I saw a case where a marketing director hoarded campaign performance data because she was afraid her team would be blamed for low numbers. She was protecting them. But it meant the leadership team couldn't make informed decisions. Luna: So the manager had to address the underlying fear — not the hoarding itself. Once they promised no blame for sharing bad news, she opened up. Lucas: That's a great example. So the root cause can be fear, or it can be ego, or it can just be inertia. Your job as a manager is to diagnose before you prescribe. Luna: And sometimes you need to model it. If you as a manager are transparent with your own work, your team will follow. Lucas: Absolutely. Leaders set the tone. If you share your thinking, your mistakes, your decision criteria — you make it safe for others to do the same. Information hoarding thrives in secrecy. It starves in sunlight. Luna: Alright, so practical takeaway: next time you notice a bottleneck, don't label the person. Look at the system, the incentives, and the fears. Then build the bridge. Lucas: And remember, the goal isn't to make everyone an expert in everything. It's to remove single points of failure and let the whole team move faster. Luna: Good stuff. That's it for this Monday.