What is knowledge hoarding and how do you stop it?
Knowledge hoarding is when employees intentionally or unintentionally withhold information that others need to do their jobs. It happens when people feel that exclusive knowledge gives them job security, status, or leverage. Stopping it requires building a documentation culture where sharing knowledge is expected, easy, and rewarded.
Why do employees hoard knowledge?
Most knowledge hoarding is not malicious. It stems from structural and cultural issues:
- Job security anxiety — "If anyone can do my job, I'm replaceable"
- Lack of time — Documenting takes effort, and it's never the most urgent task
- No incentive — Performance reviews rarely measure knowledge sharing
- Tool friction — Writing documentation in a wiki feels like extra work on top of actual work
- Unconscious hoarding — People don't realize others need information they consider obvious
In practice, the most common form is unconscious hoarding. The senior engineer who fixes things without explaining how, or the account manager who handles renewals from memory — they're not hiding information on purpose, but the effect is the same.
How do you build a knowledge-sharing culture?
Stopping knowledge hoarding requires changes at the system level, not just individual behavior.
| Strategy | How It Works |
|---|---|
| Make documentation part of the workflow | Use Glyde to capture processes as they happen, so sharing knowledge requires no extra effort |
| Include in performance reviews | Evaluate employees partly on whether their work is documented and transferable |
| Pair documentation with onboarding | When someone teaches a process, require a written SOP as the output |
| Public recognition | Highlight people who write or update documentation in team channels |
| Reduce friction | If documentation requires logging into a separate tool and writing from scratch, people won't do it |
The key insight: make sharing knowledge easier than hoarding it. When documenting a process takes 5 minutes instead of 30, the default behavior shifts from hoarding to sharing.
This answer is part of our guide to capturing and preserving team knowledge.