The Project Manager Facing Silence: Why People Don't Say What They Really Think

What you hear is not always the reality

There's a scenario almost every project manager has experienced. You leave a progress meeting, satisfied. Everything is going smoothly, the teams seem aligned, and the key users have all given their approval. Then, two weeks later, you discover that the configuration doesn't meet the actual needs on the ground, that the schedule was deemed unrealistic from the start, or that silent resistance has been brewing for weeks.

You haven't lacked information. The truth has simply been hidden from you.

Not out of malice. Out of an instinct for survival.

This phenomenon has a name in organizational psychology: the silent conformity bias. It refers to the tendency of individuals to publicly validate a decision or situation that they privately disapprove of, out of fear of the consequences or a feeling of powerlessness. And in an ERP transformation, digitalization, or reorganization project, it is one of the most underestimated risks.

The open door that remains closed

Many managers pride themselves on having an "open door" policy. "You can tell me anything." The intention is sincere. The result is often nonexistent.

It's not what you say that determines your team's behavior. It's what you've done in the past, and especially what people anticipate you'll do in the future.

If, during a previous meeting, a colleague raised an issue and was met with minimization, an annoyed look, or even a slight defensive response, the message has been sent. It will be remembered, shared in the hallways, and internalized as an unspoken rule: “here, we don’t really say what we think.”

The problem is that you, as the project manager, probably have no recollection of this event. Or worse, you interpreted it differently. This is where the subtlety of the phenomenon lies. Silence cannot be decreed. It is built up gradually, through subtle signals that the leader is generally unaware of.

The four reasons why people remain silent

Understanding silence requires exploring its causes. These are rarely unique and are often combined.

The first is fear of reprisals. This doesn't always take the form of disciplinary action. Often, it's a much more diffuse fear: being perceived as negative, as an obstacle to the project, as someone who "isn't playing ball." In transformation contexts where teams are under pressure, being seen as a hindrance can have real consequences on the relationship with the project manager or on future responsibilities.

The second reason is the feeling of futility. "It won't change anything anyway." This learned helplessness, theorized by psychologist Martin Seligman, sets in when past attempts to report problems have been unsuccessful. The individual is not passive by nature: they have simply learned that talking is pointless.

Third cause: misplaced loyalty. A key user may hesitate to report a malfunction because it involves their own manager, a valued colleague, or a service provider with whom they have a relationship of trust. Informal solidarity then takes precedence over institutional transparency.

Finally, there's simple exhaustion. A long and intense project drains the emotional energy of the teams. At a certain point, resisting, raising the alarm, and arguing requires an effort that many are no longer able to make. It's easier to acquiesce and manage problems locally, behind the scenes.

The actual cost to the project

These dynamics do not remain abstract for long. They materialize in very concrete situations.

The most classic example is that of a “configuration validated in the workshop but unsuitable for production.” The key user agreed in the meeting. They didn't dare say that the proposed workflow didn't reflect the reality of their work, for fear of appearing incompetent or slowing down the project. The result: the switchover reveals major discrepancies that could have been addressed upstream at a tenth of the cost.

Another common situation: a schedule approved by the committee is contested behind closed doors. The team knows the deadline is impossible. But no one says anything officially because the pressure from the sponsor is palpable and no one wants to take responsibility for the delay. The project manager, meanwhile, is operating with inaccurate data.

These situations have one thing in common: they could have been avoided if information had flowed freely. Silence is not neutral. It has a human, organizational, and financial cost.

Breaking the silence: four concrete approaches

The good news is that silence is not inevitable. It can be broken, provided the right factors are addressed.

The first approach is the informal one-on-one interview. Stepping outside the formal setting—a brief conversation on the sidelines of a meeting, an exchange over coffee—frees up a dialogue that the official process inhibits. This isn't superficial, hands-on management. It's a deliberate practice aimed at creating spaces where the truth can emerge without apparent risk.

The second approach is structured anonymous feedback. Simple tools, such as a questionnaire sent after each key phase or a team morale barometer, allow for the collection of subtle signals that meetings often miss. Anonymity alleviates some of the fear of retaliation, provided that the results are actually taken into account and communicated.

Third approach: institutionalize the role of devil's advocate. In design workshops or validation meetings, formally designate a person whose mission is to challenge the decisions made. This role, when structured and rotated, neutralizes the pressure to conform: challenging becomes a responsibility, not a transgression.

Finally, and perhaps most powerfully, be the first to admit you were wrong. When the project manager publicly acknowledges an error in judgment, without drama but clearly, they send a strong signal: here, the truth is better received than appearances. This signal permanently changes the culture of a project.

What silence tells you about yourself

There is an uncomfortable dimension to this subject that few articles dare to address head-on: the silence of your team is often a mirror.

It reflects how you react to bad news. It reflects your actual, not stated, tolerance for uncertainty and contradiction. It reflects what people have learned to expect from you.

This isn't a moral judgment. It's a systemic reality. And that's precisely why the best project managers don't just focus on improving tools or processes. They work on themselves, on how they receive difficult information, on managing their own emotional reactions to failure or questioning.

The most exposed project is not the one where people talk too much. It's the one where they have learned to be silent.