For hospital nurse managers: when do nurses withhold knowledge?

What counts as withholding knowledge?

Knowledge withholding occurs when someone has information another person needs but avoids answering a specific request. Organizational research distinguishes between evasive answers, pretending not to know, and a refusal accompanied by an explanation. On a ward, the first step is to establish exactly what was asked, what information was needed for the task, and what answer was actually given. The question might have concerned operating equipment, an exception covered by a procedure, or information about a patient. An incomplete answer alone does not prove intent: the nurse may not have known the detail, had time to discuss it, or been authorized to share the information. A refusal with an explanation, especially one involving protected information, need not be harmful knowledge withholding either.

The cost of a delay

When an answer does not arrive, the effect on work is usually easiest to spot: someone repeats a task, looks for another person, or needs an additional consultation. It is worth recording when the information was available, who needed it, and what was delayed because it was not shared. This describes an organizational consequence, not evidence of an effect on treatment outcomes. A meta-analysis covering 95 samples and 26,767 people examined workplace exclusion, attitudes, and well-being; it also suggests that ostracism can coincide with reduced help from colleagues. It does not, however, justify treating every lack of contact as deliberate exclusion or drawing direct conclusions about patient safety. On the ward, the priority is therefore to observe a specific delay rather than assume a clinical consequence.

Why someone might withhold information

Before a nurse manager interprets an evasive answer as rivalry, they should ask about possible obstacles. A nurse may fear losing status, being judged for revealing a mistake, facing sanctions, or being given more work after answering. It is also worth checking whether the division of work leaves one person as the sole expert on an important process and rewards that monopoly. Lack of trust and the team's usual way of responding to questions may hinder knowledge sharing, but any individual's motive needs to be established. The concept of knowledge withholding was developed in three organizational studies, not in a hospital sample. Distinguishing between evasion, feigned ignorance, and a justified refusal helps keep the conversation free of automatic accusations.

Limits on sharing information

Not all information should be shared with everyone, even if doing so would make a conversation during a shift easier. Knowledge needed to perform a task must be distinguished from data whose disclosure would breach confidentiality. Patient information should go only to those involved in care and only to the extent necessary. Refusing to share it with someone else may be an appropriate boundary, not knowledge withholding. At the same time, the team needs an authorized channel for questions about procedures and documentation, so that restricted access does not end the conversation without a solution. If the person asked does not know the answer or cannot verify it, they should identify who can. That way, the request reaches the right source without widening access to protected data.

Discussing the behavior

It is best to begin the conversation with an event both parties can check. The nurse manager can recall what question was asked about carrying out a task, what answer was given, and why the person asking then had to look elsewhere. This describes the effect on work without deciding whether the cause was bad intent, lack of knowledge, or an inability to answer. The next step is to ask what got in the way and agree on how to handle a similar request: answer it, point to the right source, or clearly explain the restriction. It is also worth agreeing on a way to raise the problem without publicly embarrassing anyone. The aim is a predictable way to share knowledge, not to force an admission of intentions that have not been established.

Designing how knowledge flows

Even a good conversation is not enough if knowledge of an important process remains in one person's head. Critical instructions and information about rarely used procedures should be kept in a shared location and updated. The procedure should say where to find the current version, who answers questions during a shift, and whom to contact when that person is absent. There also needs to be someone who can cover for the staff member who was previously the only one familiar with the process. Checking that a document exists is not enough to test the solution: a new nurse on the night shift must be able to find and use it. Organizing knowledge this way reduces dependence on one person without encouraging anyone to bypass access rules.

Checking for improvement

Improvement is best assessed through subsequent care-related questions: how long people waited for an answer, whether it was useful, and whether cover worked when the designated person was absent. The number of documents alone will not show whether information arrived in time. Nurses should also be asked whether they can admit they do not know something without fear of ridicule; otherwise, a misleading answer may feel safer than pointing someone to a source. A study of 51 teams at a manufacturing company introduced the concept of psychological safety and provides a basis for considering this question, but it did not study hospital wards. Local checks should therefore focus on team behavior and the quality of answers rather than treating findings from another industry as evidence of improved patient care.

An evasive answer does not always signal bad intent. A nurse manager can start by establishing what information was requested, what its absence delayed, and how the team should respond next time.

Empatyzer and knowledge sharing among nurses

A nurse once again receives an evasive answer to a question about how to carry out a task. Before asking again, she can practice a matter-of-fact question with Em: what information she needs, why she needs it, and whom to ask if her colleague cannot answer. A comparison with that particular colleague and the relationship view can help her choose how to approach the uncomfortable conversation without assuming bad intent. If the same problem recurs across shifts, the nurse manager can talk with Em in team mode about a rule for sharing essential knowledge: who answers, where they direct people for a source, and what happens when they are absent. Em can also help her prepare a conversation about sharing information without attributing unverified intentions. Micro-lessons can help staff practice giving a brief, useful answer or pointing to the right source. This preparation supports the conversation and shared agreements; it does not replace checking the facts, access permissions, or whether an answer actually arrives in time the next time someone asks.