Knowledge held back when asked

When rewards go to individuals, when people compete inside the team, or when they worry about being replaced, holding knowledge back becomes the sensible choice. Someone is asked for what they know and gives a vague answer, stalls, or explains why they can't help. The cause is the setup, not the person.

• Direct requests for help get vague answers or slow replies.
• Templates, examples, and methods stay private.
• People compete for the same credit.

This one is hard to see from outside, so ask privately. Who: three people who depend on each other in this workflow. Ask: "When did you last ask a colleague for something and not get a straight answer?" Look at: whether rewards and recognition go to individuals or to the team. You're probably looking at this pattern if people describe requests being dodged and the rewards favor individuals. Probably not if people share freely but the knowledge still doesn't reach the work. If not, compare it with Knowledge stuck behind team lines.

The Change Barriers entry Replacement fear, where experienced people hold back their methods because AI might replace them. That is one cause of this pattern.

No move in the Spark Library yet. See Replacement fear in Change Barriers, and the ground rules on your watch list.

Two large combined analyses (104 studies and 66 studies) found that holding knowledge back goes with lower performance and creativity (Arain and colleagues, 2023; Zhang and colleagues, 2025), and the second found it rises with rudeness at work, abusive managers, and conflict. Established association, mostly one-time surveys. In a lab study with small groups of students, competing groups solved a shared problem 33% of the time, against 93% for cooperating groups. The main reason was that competing members stopped questioning their first preference. In a second experiment, mistrust drove both the holding back and the refusal to reconsider (Toma and Butera, 2009). Emerging.