7 Tips on How to Combat Knowledge Hoarding at Work

Knowledge hoarding, also called information hoarding, is keeping what you know to yourself, whether or not anyone asks. We recommend finding out whether anyone has asked before you pick a fix. If nobody has, it is often a friction problem: answering in a direct message is faster than writing a page. If someone asked and got nothing, researchers call that knowledge hiding and link it to distrust, and to job insecurity when jobs feel at risk. The seven tips below follow that split.
Why people keep knowledge to themselves
- Job insecurity: if sharing what you know makes you feel replaceable, holding onto it feels safer. In a three-wave study of 346 Korean workers, employees who felt their jobs were at risk identified less with their organization and withheld more knowledge from colleagues who asked for it.
- Status: being the only person who knows something is its own kind of recognition, and sharing it dilutes that.
- Distrust: employees who do not trust their colleagues, or do not see how sharing knowledge at work helps the organization, quietly stop doing it.
- Friction: without an effective knowledge sharing strategy or an easy-to-use knowledge sharing tool, documenting competes with a heavy workload, and the workload usually wins.
- No expectation and no credit: a team that never asks people to document what they know, or credits them when they do, trains them not to.
Work stalls whenever the one person who knows the answer is out, in a meeting or slow to reply, and knowledge that lives in one head leaves when that person resigns.
7 ways to combat knowledge hoarding
1. Find out whether anyone has asked
Researchers separate knowledge hoarding, keeping knowledge to yourself, from knowledge hiding, which is intentionally withholding knowledge that another person has asked for. The fix differs. If nobody asked, you have a hoarding problem and tip 2 applies. If someone asked and got a pretended “I don’t know”, a promise of an answer that never came, or a reference to confidentiality, that is hiding, and distrust predicted all three forms in the original studies. Then work on the relationship between the two people, not on documentation.
2. Make sharing cheaper than not sharing
Someone can be entirely willing to share and still end up as the only source of truth, because answering a colleague in a direct message is faster than writing a page, and the message leaves no trace for the next person who asks. Remote teams feel this most, since there is no desk to walk to. Ask people to post questions in a shared channel so each answer has an audience, and see our list of the 30+ best remote collaboration tools for teams if you are still choosing a chat tool.
If the expert dislikes writing, do not ask for a document. Have a colleague interview them for half an hour and write the page, with the expert only checking it. The expert talks and reviews, and the person who needs the answer does the writing.
Give the page a home: an online knowledge sharing platform, such as an internal wiki or internal knowledge base, gives people somewhere to put what they know instead of just their own notes.
3. Keep documentation drives away from layoffs and reorganizations
Job insecurity makes people hold back what they know, so a push to write down everything, run while jobs feel at risk, reads as a request to make themselves replaceable. We recommend running a documentation push when roles are settled, saying in writing what the pages will be used for (cover during leave, training for new hires), and having managers coach people through the change. In the same Korean study, coaching leadership softened the effect of job insecurity on how closely people identified with their organization.
4. Credit the people who share
Build a knowledge-sharing culture by recognizing the people who share, not just the people who look busy, and do it by name where the whole team can see it. Credit also feeds employee engagement.
5. Write the expectation down
Make sharing an explicit expectation, not an unwritten one. A concrete version is a handover page at the end of each project or when someone changes role, listed in the role’s expectations and checked in the performance review, so people know what “documented” means before they are measured on it.
6. Cross-train on real work
Have a second person do a task once beside the expert, then alone with the expert reviewing. That passes on judgment calls a document leaves out, and it means the team is not stuck when one person is out.
7. Find the questions only one person can answer
Audit for knowledge gaps. List the questions that only one person on each team can answer, and start with the ones that would stall work if that person were away for two weeks. Making sharing that specific information a priority gives the tips above a first target.
.jpg)
.jpg)

