Knowledge Hiding / Information Hoarding

One-liner: Deliberately withholding information, documentation, or access a colleague needs to do their job, kept as leverage rather than shared as expertise.

Also known as / related terms: Knowledge hoarding, evasive hiding, playing dumb, gatekeeping, information silos.

What it is

Knowledge held back as leverage, not shared as help.

Organizational behavior researchers Catherine Connelly, David Zweig, Jane Webster, and John Trougakos formally defined and measured this construct in their 2012 paper “Knowledge Hiding in Organizations” in the Journal of Organizational Behavior, distinguishing it from simply not knowing something and from organization-wide knowledge loss.

They found it takes three related forms: evasive hiding (pretending to help while giving incomplete or delayed information), rationalized hiding (offering a justification for withholding, like confidentiality, that doesn’t hold up), and playing dumb (pretending not to know).

A 2014 follow-up by Marko Cerne, Christina Nerstad, Anders Dysvik, and Miha Skerlavaj in the Academy of Management Journal traced what happens next: knowledge hiding triggers a reciprocal distrust loop, coworkers who get stonewalled once become less willing to share their own knowledge in return, and the effect compounds through a team over time.

The same study found the damage isn’t one-directional: hiding knowledge measurably reduces the hider’s own creativity too, an effect that gets worse in competitive, performance-focused team climates and softer in cooperative, mastery-focused ones.

Later reporting on Connelly’s continuing research, summarized by the Society for Human Resource Management, links the behavior to a workplace culture where knowledge is treated as power, where holding unique information makes a person feel indispensable, and to low trust between the person asking and the person answering.

What it looks like (workplace)

Before: A veteran everyone routes questions to, the person who has quietly become the sole owner of a critical process.

The incident: The day before a deadline, the “current version” of a shared config file turns out to be outdated. In the fix meeting, it becomes clear the veteran had the working version the whole time.

The month after: The target starts building their own shadow documentation just to stop this from happening again. The veteran calls it duplication of effort.

How it actually unfolds

1. Accumulate. One person becomes the sole holder of a process, a relationship, or a system, and resists documenting it with plausible-sounding reasons.
2. Gatekeep. The three forms Connelly and colleagues named, evasive hiding, rationalized hiding, and playing dumb, form a repertoire, each individually deniable; see Plausible Deniability for why that property matters.
3. Let the cost land. A colleague misses a deadline for want of the withheld piece, and the failure attaches to the colleague, not to the person who withheld it. This sits adjacent to Sandbagging and stands in direct contrast to Weaponized Incompetence: one is performed inability used to avoid a task. This is concealed ability used to control who else can do it.
4. Cash in. A crisis arises that only the hoarder can fix, and indispensability pays off at review, layoff, or negotiation time.
5. The spiral. Cerne and colleagues’ reciprocal-distrust finding plays out directly: targets learn the pattern and start hiding back, and team-wide trust and creativity measurably decline, a cost the hoarder pays too, whether or not they ever connect it back to their own behavior.

Why they do it

Withholding a piece of institutional knowledge keeps a person indispensable and gives them leverage, whether that is job security, credit, or control over decisions that depend on information only they have. The 2014 reciprocal-distrust research complicates the simple leverage story, though: the same behavior that buys short-term security measurably shrinks the hider’s own creativity and the team’s collective trust, meaning the tactic is more self-limiting over time than it first appears.

How to protect yourself

Repeated vague answers are data, not bad luck. Build a second source and a paper trail.

• Ask for documentation and process handoffs in writing and in advance of needing them, not in the moment of crisis.
• Build redundancy: cultivate more than one source for any critical piece of information or access.
• Notice patterns of “helpful but useless” answers. Repeated vague responses are data, not bad luck.
• Route requests through shared channels (tickets, shared docs) so delays and gaps are visible to more than just you.

Cross-links: Weaponized Incompetence, the mirror image, faking inability instead of hiding ability; Sandbagging, the sibling pattern of hoarding output instead of information; Chauffeur Knowledge, the surface-fluency contrast; Credit Theft / Idea Appropriation, what often happens to work built on top of the withheld knowledge; Plausible Deniability, the property that lets each individual instance survive challenge.

Label note: Established, peer-reviewed academic construct in organizational behavior research with a validated measurement scale, not a site coining. The workplace descriptions above are illustrative applications of that research.