AI Knowledge Hiding

Confidence 0.70 · 1 source · last confirmed 2026-06-16

AI knowledge hiding (Anicich & Brouwers, HBR 2026) is the deliberate withholding — by employees — of the AI workflows, prompts, and techniques they discover through private experimentation. The authors frame it as “the suppression of solutions”: where the classic organizational-silence literature studied the hiding of problems (bad news, risks, ethical concerns), AI introduces the hiding of solutions.

Why it is newly consequential

Productivity gains “used to scale by default” — embedded in shared systems, standardized processes, and formal tools that spread improvements structurally. With AI, the most valuable gains come from individual experimentation: a prompt sequence that produces client-ready output in a fraction of the time. That knowledge is portable, easy to refine in private, and easy to keep to yourself. When an individually-discovered workflow cuts a three-hour task to twenty minutes and is trivial to conceal, silence becomes economically consequential in a way it was not before. This is why AI knowledge hiding is a distinct failure mode of enterprise-ai-adoption rather than a restatement of generic knowledge hoarding: high individual adoption can coexist with near-zero collective capability gain.

The empirical claim: trust, not governance

The headline finding is that the binding driver is organizational trust, working largely through psychological safety — not formal AI policy or approved tooling.

• KPMG / University of Melbourne (48,000+ respondents): 57% admit hiding their AI use at work.
• Anicich & Brouwers’ own survey (604 daily-AI users): 30.3% intentionally withheld AI knowledge; the lowest-trust quartile was ~4× more likely to hide than the highest (47% vs 14%); psychological safety showed the same gap (45% vs 17%).
• Trust survived controls for job insecurity, internal competition, distributive fairness, AI policy, sanctioned tools, age, gender, tenure, and job level. Having an AI policy or approved tools, on its own, predicted nothing. Trust mattered more where a shared sanctioned toolset existed (“trust creates the willingness to share; a common toolset creates the opportunity”).
• Corroboration: a 104-study meta-analysis (~31,800 employees) links psychological safety to less knowledge hiding, and abusive supervision / mistreatment / job insecurity to more; a Stanford 51-deployment study found 77% of the hardest adoption challenges were non-technical.

The three rational costs of disclosure

Employees make a rational calculation about the cost of making their AI workflows visible:

1. Reputational — being judged as less capable, or having the work discredited (“a computer did it”).
2. Workload — efficiency treated as spare capacity to fill: “if I automate A and B, they make me do D, E, F.” This is the micro-productivity-trap at the individual level.
3. Replaceability — enterprise tools log prompts and workflows, so a method can be extracted and routed to a cheaper replacement; hence the (perverse) advice to use personal AI tools so learning “stays with you.”

Underlying all three is Amy Edmondson’s distinction: organizations confuse praiseworthy exploratory testing with blameworthy deviance, and so punish exactly the experimentation they need.

What leaders can do (the source’s prescriptions)

Earn the disclosure you want (remove ambiguity; lightweight demos over process memos; credit the contributor); stop taxing efficiency gains (an explicit norm for reinvesting saved time); reward multiplier behavior (credit for adopted workflows; team incentives + pro-sharing norms, since comparison-heavy climates amplify retaliatory hiding); legitimize experimentation, then surface it (Anthropic’s Claude Code “side quests” ≈ 3M 15% / Google 20% time); treat disclosure as a contribution (the manager’s 30-second reaction is the decisive trust signal; don’t turn one demo into a standing obligation). A standing tooling warning: the same logging that lets you credit a discovery also lets you extract it.

Debates and supersession

• Is this distinct from classic knowledge hoarding? The novel claim is the suppression of solutions (not problems) plus the portability/concealability of AI workflows that makes silence newly costly. Single-source so far; the supporting meta-analysis is about knowledge hiding in general, not AI specifically.
• Single-source caveat. Rests on one HBR article (with its own 604-respondent survey + cited studies). Confidence at the single-source floor pending independent corroboration.

Related concepts

• enterprise-ai-adoption — hiding is why high individual adoption need not yield firm-level gains; trust/culture is the binding constraint, not tooling.
• micro-productivity-trap — the workload “tax” is the shared mechanism; hiding is the individual-level response that keeps task gains from aggregating.
• durable-skills / ai-deskilling — the replaceability fear (your logged method becomes someone else’s, or an automation’s).
• responsible-ai — the surveillance/credit-vs-extract trade-off in sanctioned-tool logging.

Open questions

• Does the trust→disclosure finding replicate outside the U.S. / outside knowledge work?
• Do “side quests” and multiplier-reward schemes measurably raise disclosed (not just total) AI productivity?
• How does mandatory enterprise-tool logging net out — does the credit mechanism or the extraction fear dominate as trust varies?