Employees do not always withhold knowledge because they want to block the company. Often, they protect their status, react to missing recognition, lack time, or distrust how their knowledge will be used. For mid-sized companies, this becomes risky when customer, process, and experience-based knowledge remains trapped in individual heads.
Why do employees sometimes avoid documenting what they know?
Many companies know this sentence: “Just ask Tom. He knows.”
Tom really does know. He knows the customer, the old quote, the exception in the service contract, the strange integration, the supplier contact, the ERP workaround, and the reason why a certain solution was rejected three years ago. Tom is helpful. Tom is fast. Tom saves the day.
But Tom barely documents anything.
That does not automatically make him difficult. It does not necessarily make him lazy. Sometimes it is a rational reaction to a workplace that needs knowledge but does not truly reward knowledge work. The person who documents rarely gets attention. The person who solves the emergency gets asked again. The person who is the only one who knows remains important.
This is why knowledge management is not mainly a software problem. It is a leadership, culture, and incentive problem. A new knowledge base will not help much if employees quietly believe: “If I write everything down, I become easier to replace.”
Hacker News discussions show this pattern regularly. Developers and knowledge workers often describe documentation as a problem of time pressure, unclear ownership, poor searchability, and weak motivation rather than a pure tooling issue. In one discussion about company knowledge bases, a commenter describes a habit of checking and improving documentation before answering repeated questions, showing that knowledge sharing is not a one-time upload but a working discipline.
Why can knowledge feel like power inside a company?
Knowledge inside organizations is never completely neutral. The person who holds critical knowledge has influence. Not always formal authority, but practical authority.
People ask that employee. They depend on that employee. That employee shapes decisions because no one else fully understands the context. If a process works only because one person knows the invisible rules, that person becomes a central node in the company.
This is especially common in mid-sized businesses. Roles are often broad, processes have grown over years, and responsibilities are not always cleanly separated. A long-tenured employee does not only know their job. They know exceptions, history, customer preferences, and silent agreements. That knowledge is valuable. That is exactly why it may be withheld.
This does not always happen consciously. It may happen slowly. An employee does not document because there is no time. Then everyone starts asking them. Then that feels important. Then documentation becomes even less attractive.
Knowledge becomes status.
Why is missing documentation not always laziness?
Leaders often judge missing documentation too quickly. “People are lazy.” “Nobody follows the process.” “The wiki is ignored.”
Sometimes that is true. Often it is incomplete.
Employees do not document when they see no benefit. They do not document when documentation is unpaid extra work. They do not document when nobody reads it. They do not document when outdated pages are never cleaned up. They do not document when corrections are treated as personal criticism. They do not document when knowledge sharing is expected but not planned into the workday.
APQC identifies trust as one of the key barriers to knowledge sharing. Employees need trust in the knowledge management program itself and in the available information, learning resources, and expertise. When that trust is missing, knowledge flows more slowly.
That is the key point. Employees do not share knowledge just because a tool exists. They share knowledge when it feels useful, safe, and valued.
What role do recognition and incentives play?
In many companies, knowledge sharing is praised in speeches but not rewarded in practice.
The project delivery counts. The billable hour counts. The fast fix counts. The clean documentation afterwards disappears between meetings, calls, and new tasks.
That sends the wrong signal: knowledge sharing is nice, but not career-relevant.
Gallup and Workhuman found that well-recognized employees were 45 percent less likely to have left their organization two years later. Recognition is therefore not a soft side issue. It is a retention and culture factor.
For knowledge management, this matters directly. Employees who document decisions, explain processes, surface mistakes, and train colleagues should not become invisible. Otherwise, the incentive system becomes distorted. The person who hoards knowledge remains indispensable. The person who shares knowledge appears less exclusive.
Strong organizations reverse this logic. They do not treat the employee who alone knows everything as the hero. They treat the employee who makes others capable as valuable.
Why is there often simply no time?
The most honest reason is often simple: documentation does not fit into the day.
Employees know it would be useful. They know handovers would become easier. Still, urgent work wins against important work. The customer is waiting. The quote must go out. The service case is stuck. The inbox is full. A colleague asks for help.
Knowledge is then shared informally: quickly in chat, briefly on a call, between two meetings. It works in the moment. It creates a problem for the organization.
Microsoft reported in its 2023 Work Trend Index that 62 percent of respondents struggle with spending too much time searching for information during the workday. That matches the reality in many companies: knowledge exists, but it is distributed, incomplete, outdated, or hard to find.
If documentation is not part of the workflow, it becomes leftover work. And leftover work almost always loses.
Why can AI even make the problem worse?
AI can make knowledge easier to find. It can summarize documents, detect similar cases, search across sources, and answer questions based on approved material. That is useful.
But AI can also create distrust.
If employees believe their knowledge is being extracted in order to replace them, they may become more careful. Their documentation may become thinner, more generic, or more tactical. This creates a new leadership challenge: companies must explain why knowledge is collected, who can access it, how sources are evaluated, and what benefit employees get from the system.
Microsoft and LinkedIn reported in the 2024 Work Trend Index that 75 percent of global knowledge workers use generative AI at work. At the same time, 78 percent of AI users bring their own AI tools to work. Employees are not necessarily waiting for official company systems; they are creating their own workarounds.
For mid-sized companies, this is both an opportunity and a risk. Without rules, shadow processes emerge. With the right structure, AI can make knowledge more usable without making employees feel devalued.
What motives are behind knowledge withholding?
Not all knowledge withholding has the same cause. That is why blanket accusations rarely help.
| Motive | What employees may think | What companies often get wrong | Better response |
|---|---|---|---|
| Status protection | “If I document everything, I become less important.” | Treating documentation as duty without recognition | Reward useful knowledge sharing visibly |
| Time pressure | “I do not have time for this.” | Adding documentation on top of existing work | Build documentation into workflows |
| Distrust | “This may be used against me.” | Collecting knowledge without explaining purpose | Clarify purpose, access, and benefit |
| Frustration | “I have explained this three times already.” | Allowing repeated questions forever | Turn repeated answers into maintained knowledge objects |
| Quality anxiety | “My notes are not good enough.” | Expecting perfect documentation | Allow raw knowledge and curate it |
| Bad tools | “Nobody will find this later anyway.” | Creating storage instead of searchability | Define structure, metadata, and ownership |
The table shows the main point: this is rarely just an individual employee problem. It is usually a system problem.
Why is knowledge withholding dangerous for mid-sized companies?
Mid-sized companies are often large enough to have complex operations but not always large enough to have mature knowledge structures. This is where the most dangerous dependencies appear.
A sales employee knows the special logic of key customers. A project manager knows which subcontractors are reliable. A service technician knows recurring defects in certain systems. An administrator knows how a specific public authority really wants documentation submitted. A developer knows the integration that nobody officially wants to touch anymore.
As long as those people are available, the company appears stable. When they are sick, leave, or retire, it becomes clear that the stability was not in the system. It was in people’s heads.
Gallup’s 2026 Germany country data shows that only 11 percent of employees in Germany are engaged at work. At the same time, 67 percent say it is a good time to find a job in their city or area. Companies should therefore not assume that key people will simply stay.
That is uncomfortable, but realistic. If a company starts securing knowledge only after the resignation arrives, it is already late.
How does a culture of voluntary knowledge sharing emerge?
A good knowledge culture does not start with a new tool. It starts with a different message.
Not: “Document so you become replaceable.”
But: “Document so nobody has to carry the same problems alone.”
That changes the tone. Knowledge sharing is no longer framed as control. It becomes relief. Employees do not have to answer the same questions repeatedly. New colleagues become productive faster. Decisions become easier to understand. Mistakes are less likely to repeat. Customers receive more consistent answers.
APQC defines knowledge management as a structured process that helps information and knowledge flow to the right people at the right time. That is the core idea: knowledge should move, not sit unused in an archive.
For mid-sized companies, this works best in a pragmatic way. Not with long manuals nobody reads. Instead, with short, maintained knowledge objects: “This is how we calculate this case.” “This exception applies to customer X.” “This mistake must not happen again.” “This decision was made for the following reason.”
How should a company handle knowledge as power?
Knowledge as power does not disappear through slogans. It must be addressed structurally.
First, expectations must be clear. Critical knowledge does not belong to one person alone. It belongs to the company. This should be communicated calmly and respectfully, without blaming employees.
Second, recognition matters. Sharing knowledge is real work. It should appear in goals, feedback, role descriptions, and promotion criteria.
Third, time must be allocated. Knowledge work must be planned. If every hour is filled with operational tasks, documentation remains a statement of intent.
Fourth, systems must be usable. A knowledge base nobody can search will only increase cynicism. A Company Brain must therefore do more than store content. It needs context: source, freshness, owner, approval status, and links to customers, processes, and decisions.
Fifth, trust is essential. Employees must understand that shared knowledge is not used against them but used to make their work calmer, more resilient, and less dependent on constant interruption.
How can a Company Brain help?
A Company Brain is not a magic container for everything employees know. It is a structured system for making relevant company knowledge findable, reliable, and usable.
The difference from ordinary documentation is context.
A shared drive contains files.
A wiki contains pages.
A Company Brain connects knowledge with questions, roles, decisions, processes, customers, cases, and owners.
That makes knowledge usable rather than merely stored. An employee does not need to know the file name. They can ask: “How do we handle this type of customer?” “Which mistakes happened in similar projects?” “Which quote logic was used last time?” “Which exception applies to this contract?”
This does not replace leadership. It does not replace trust. But it creates a framework in which knowledge sharing becomes less risky, less burdensome, and more useful.
What are the first practical steps?
The starting point should not be a huge knowledge initiative. A focused start is better.
Which questions are asked again and again?
Which decisions depend on single individuals?
Which customers have special rules?
Which processes work only because someone has a feeling for them?
Which mistakes have happened repeatedly because old knowledge could not be found?
From these answers, the first knowledge objects can be created. Short, specific, and clearly owned.
Tone matters. Employees should not feel that knowledge is being taken away from them. A better message is: “We make knowledge shareable so work depends less on individual memory.”
A company does not become stronger when everyone protects what they know. It becomes stronger when knowledge is available where decisions are made.
Sources for the statistics used
- Gallup and Workhuman: “Recognition in the Workplace Research”
https://www.gallup.com/analytics/472658/workplace-recognition-research.aspx - Microsoft: “Will AI Fix Work? Work Trend Index 2023”
https://www.microsoft.com/en-us/worklab/work-trend-index/will-ai-fix-work - Microsoft: “AI at Work Is Here. Now Comes the Hard Part”
https://www.microsoft.com/en-us/worklab/work-trend-index/ai-at-work-is-here-now-comes-the-hard-part - Gallup: “State of the Global Workplace: Germany Country-Level Data”
https://www.gallup.com/workplace/705434/state-global-workplace-germany-country-level-data.aspx
Further reading
- Harvard Business Review: “A New Approach to Knowledge-Sharing Within Organizations”
https://hbr.org/2024/08/a-new-approach-to-knowledge-sharing-within-organizations - APQC: “Overcoming Trust as a Barrier to Knowledge Sharing”
https://www.apqc.org/resource-library/resource-listing/overcoming-trust-barrier-knowledge-sharing - Nature Humanities and Social Sciences Communications: “Beyond diversity: the impact mechanism of organizational inclusion on employees’ knowledge hoarding”
https://www.nature.com/articles/s41599-024-04085-z
FAQ
Why do employees not always share what they know?
Employees often do not share knowledge because they lack time, recognition, or trust. Sometimes status protection also plays a role: being the only person who knows something can feel safer and more important. This is rarely just an individual problem. It usually reflects weak incentives, unclear ownership, or missing knowledge processes.
Is undocumented knowledge a leadership problem?
Often, yes. Leaders indirectly decide whether knowledge sharing matters. If only operational output is rewarded and documentation never receives time, attention, or recognition, knowledge sharing becomes secondary. Good leadership defines which knowledge is critical, who owns it, and why sharing it helps the team and the company.
How can a company detect knowledge hoarding?
Typical signs include repeated questions going to the same people, processes that cannot be explained, weak substitution during absences, unclear exceptions, and phrases such as “only John knows that.” Long onboarding times for simple processes are another warning sign that important knowledge is hidden in individual experience rather than shared systems.
Is knowledge hoarding always intentional?
No. Many employees do not consciously withhold knowledge. They fail to document because they are under pressure, have poor tools, or believe their notes are not good enough. Intentional withholding exists, but companies should first examine whether time, trust, recognition, structure, and usability are missing.
How can employees be motivated to document knowledge?
Documentation must be visibly useful. Employees should experience that good knowledge contributions reduce repeated questions, improve onboarding, and receive recognition. Simple templates, dedicated time, clear ownership, and feedback help. People who share knowledge should not become invisible. Their contribution should be treated as part of operational performance.
Why does trust matter in knowledge sharing?
Trust is essential because employees need to understand why their knowledge is collected, who can access it, and how it will be used. If knowledge management feels like surveillance or replacement preparation, people become cautious. If it is framed as relief, quality improvement, and shared capability, participation becomes more natural.
Can AI solve knowledge hoarding?
AI can help make existing knowledge easier to find, structure, and reuse. It can surface similar cases, summarize sources, and answer questions from approved content. But AI does not automatically solve the social causes of knowledge hoarding. Without trust, governance, source quality, and ownership, AI may even increase suspicion.
What should be documented first?
Start with knowledge whose absence would create immediate problems: customer exceptions, quote logic, escalation paths, technical edge cases, process deviations, recurring mistakes, and important decisions. The goal is not bureaucratic completeness. The goal is to protect operational continuity where the company is most dependent on individual memory.
All articles about company brain
