The Transformation

It usually starts the same way. A brilliant engineer becomes a tech lead, then a manager. They're so good at what they do that leadership assumes they'll naturally share their knowledge.

But something happens on the way to leadership. The same traits that made them exceptional—deep expertise, ownership, the ability to solve hard problems—morph into something different.

They become the only person who knows certain systems. They become the bottleneck for certain decisions. They become the "go-to" person for everything, and they wear this as a badge of importance.

What they don't see: they're building a trap. For themselves, and for their team.

The Mathematics of Hoarding

Let's do the math on knowledge hoarding.

As an individual contributor, your value is in what you personally produce. If you know something that no one else knows, you're valuable—because you're the only one who can do certain work.

As a leader, your value is in what your team produces. If you know something that no one else knows, you're a bottleneck—because you're the only one who can make certain decisions, explain certain systems, or solve certain problems.

The knowledge that made you valuable as an IC makes you dangerous as a leader. And most organizations never explain this transition.

The Symptoms

How do you know you have a knowledge hoarder on your team?

1. The Single Point of Failure

Certain decisions can only be made by one person. Certain systems can only be understood by one person. Certain context only exists in one person's head.

This is architectural fragility. And it's always caused by human choices, not technical necessity.

2. The Gatekeeper

Anyone who wants to make progress on certain topics needs approval, input, or access from the hoarder. They're not malicious—they genuinely believe they need to be involved.

But the result is the same: nothing moves without them.

3. The Expert Who Can't Explain

The hoarder may know everything, but they can't transfer that knowledge. Their documentation is sparse. Their explanations assume too much context. When they leave, they take understanding with them.

4. The Team That Can't Operate Without Them

The team functions only when the hoarder is available. Vacations create crises. Departures create catastrophes. The team has learned to defer rather than decide.

The Real Cost

Here's what leaders underestimate about knowledge hoarding:

Bottlenecking velocity. Nothing moves fast when everything needs one person's approval. The team's speed becomes the hoarder's availability.

Creating bus factor of one. When only one person knows something critical, you're one person away from disaster. This isn't hypothetical—it's how teams fail.

Preventing team growth. Junior engineers can't grow if they're always deferring to the expert. The hoarder unintentionally creates dependency, not capability.

Losing the knowledge. When hoarders leave—and they always leave eventually—they take years of institutional knowledge with them. This is the most common cause of technical debt I've seen.

Killing their own career. Here's the irony: hoarders think they're making themselves indispensable. But in reality, they're making themselves unscalable. The moment they can't handle the load, they're replaced—and the team moves on without them.

The Hexaco Profile

Knowledge hoarding correlates strongly with specific personality traits in the HEXACO model.

Low Altruism. Hoarders score low on the Altruism dimension. They're not naturally inclined to help others at personal cost. Sharing knowledge feels like giving something away.

Low Fellowship. They don't get satisfaction from social interaction or group belonging. The team is a collection of individuals, not a community they care about.

High Prudence. They're careful, risk-aware individuals. Sharing knowledge feels risky—what if someone does it wrong? What if they lose control?

Low Liveliness. Low energy for social interaction means they don't naturally reach out to share, teach, or collaborate.

Understanding these traits helps leaders create systems that counteract the natural hoarding tendency.

The Cure

Knowledge hoarding isn't about being a bad person. It's about a bad system. And it can be fixed.

1. Make Knowledge Sharing Visible

If you only measure what people produce, you'll get producers. If you measure knowledge transfer, you'll get teachers.

Build knowledge sharing into performance reviews. Track: How many people has this person mentored? What documentation have they created? How many team members can now do what they used to do alone?

2. Create Documentation Rituals

Don't just ask for documentation—create time for it. Make it part of the Definition of Done. If knowledge isn't shared, the work isn't complete.

3. Rotate Responsibilities

Deliberately move knowledge around. Have different people own different systems. Force the distribution of expertise.

4. Celebrate Teaching

When someone successfully transfers knowledge—when they coach someone to the point of competence—celebrate it. Make it as visible and valued as shipping code.

5. Remove the Rewards for Hoarding

If someone's value is in being the only one who knows something, that's a system problem. Redefine value as what you create through others, not what you control alone.

What Hoarders Need to Hear

If you're a leader and you recognize yourself in this description, here's what you need to understand:

Your job has changed. As an IC, you were measured by what you produced. As a leader, you're measured by what your team produces through you.

Your knowledge is a liability. Everything you know that no one else knows is a risk. To yourself, to your team, to the organization.

Your growth is blocked. You can't advance beyond what you can personally produce. Your ceiling is your own capacity. Multiply your impact by letting go.

Your job security is an illusion. The moment the organization decides the bottleneck costs more than it's worth, you're replaced. But if you build a team that doesn't need you, you become invaluable.

The Bottom Line

Knowledge hoarding is the silent killer of engineering teams. It looks like expertise. It feels like dedication. But it's actually a form of control that destroys teams from within.

The best leaders I've known have one thing in common: they're constantly working themselves out of a job. They're building teams that don't need them, transferring everything they know, and measuring their success by what they create through others.

That's the opposite of hoarding. And it's the only math that works for leadership.

This article is part of the Leadership Unfiltered series on engineering team dynamics. For more insights on building high-performing teams in the AI era, explore LU Teams.