Back to articles

Leadership & collaboration

Why teams stay silent when problems arise

How polite agreement becomes a leadership risk

A woman sits thoughtfully in a meeting while other participants listen.

The meeting goes pleasantly. The project management reports on progress, the business units nod, and at the end the executive board thanks everyone for the good cooperation. Nobody raises any objections. The minutes record that the next steps have been agreed.

Two days later, a different story is heard in the corridor. The requirements are said to be unclear. The deadlines are said to be unrealistic. An interface, it is said, will not work in the planned scope. Several people already knew this during the meeting. Nobody said it.

What happened here? The simple accusation is that those involved failed to take responsibility. Sometimes that is true. But the more important question is why it seemed sensible to them to stay silent.

When a team only speaks openly in informal conversations, this is not merely a communication problem of individual people. It is an indication of the rules by which dissent is handled in that team.

I have dealt with the wider context of false harmony and conflict avoidance in project management in the article "When everyone nods, the project is in danger" (https://hosang-consulting.com/en/articles/scheinharmonie-projektmanagement). Here the focus is on the narrower question of why employees hold back recognisable problems and what leadership can concretely change about it.

Why silence can be rational

Employees constantly make small risk decisions. Should I point out that the plan will not work? Should I question my superior's assumption? Should I say that I have not understood something? Or is it wiser to wait for now?

Anyone who has repeatedly experienced, in a given environment, that objections are regarded as disloyalty becomes cautious. Perhaps someone received a poor performance review after asking a critical question. Perhaps bad news was publicly attributed to the messenger. Perhaps people who raise risks are afterwards described as difficult.

Then silence is not simply a lack of courage. It can be an understandable reaction to foreseeable consequences. The organisation has learned that unpleasant information can become costly. As a result, it receives less of it.

This is dangerous because problems do not disappear as a result. They merely leave the official communication channel. A risk that does not appear in the project report continues to exist technically, economically or organisationally.

Silence takes many forms

Not all silence is the same. Someone may say nothing because they lack information. Another holds back because they are linguistically unsure or do not master the specialist field of the other participants. Yet another sees a conflict of objectives but fears the personal consequences of a confrontation.

Some stay silent out of politeness. Others because they see no prospect of their feedback changing anything. Still others deliberately wait until a decision is ripe. These differences matter: an organisation should not psychologise every instance of reticence.

Leadership must find out which conditions produce the silence. Is it enough to provide better information? Is a different framework for discussion needed? Is an effective decision-making path missing? Or are relationships so strained that criticism feels dangerous?

Anyone who wants to respond to every situation with the appeal "Just be open" underestimates the actual cost of dissent.

The importance of psychological safety

The organisational researcher Amy Edmondson describes psychological safety as a shared belief that a team offers a safe space for interpersonal risks. In her 1999 study, this belief was associated with learning behaviour in teams. It does not follow that a pleasant climate automatically produces good results. It suggests that people are more likely to raise mistakes, doubts and gaps in knowledge if they are not socially punished for doing so.

The term is occasionally misunderstood. Psychological safety does not mean that every opinion is right, that nobody may be criticised or that performance no longer matters. On the contrary: a team that takes difficult tasks seriously needs open feedback precisely when something is not working.

The goal is not harmony at any price, but the ability to disagree objectively. A leader can set high standards and at the same time ensure that problems become visible without anyone losing face. They should not play down mistakes, but nor should they humiliate the person who discloses them.

The costly misunderstanding about loyalty

In some organisations, loyalty is equated with agreement. Anyone who points out risks supposedly damages the joint undertaking. Anyone who criticises a decision apparently undermines authority. This is a convenient but dangerous definition.

Loyalty can consist precisely in voicing an unpleasant truth early. Anyone who knows of a significant risk and still stays silent may be protecting the mood, but not the company. Responsible leadership should therefore distinguish between criticism of an idea and rejection of the shared task.

This also demands something of the person voicing criticism. They should make their observations comprehensible, examine other perspectives and distinguish between facts, assumptions and judgements. Open criticism is no licence for disparagement. Anyone who exposes others creates, in turn, a climate in which people stay silent.

A good conflict culture is demanding because it requires courage and consideration at the same time.

A project nobody wanted to stop

Let us imagine an IT project whose go-live date is politically and economically significant. Management has been communicating the date for months. In the project team, there are mounting signs that the data migration could not be tested sufficiently. In the steering committee, however, people continue to speak of a controllable risk.

Why? Perhaps the project management fears that a postponement would be interpreted as a failure of leadership. Perhaps the business unit does not want to explain that the requirements were delivered later than agreed. Perhaps IT does not want to ask for further resources. Every party has reasons to protect its own role.

In the end, an apparently joint decision is reached without the actual risk having been explicitly accepted. Approval has formally been given, but the people involved may have understood it under different assumptions.

This example is hypothetical. Its pattern illustrates why an organisation needs more than just a risk register. It needs a path by which a critical finding changes a decision. Otherwise documentation becomes the administration of knowledge that nobody wants to use.

How leadership itself produces silence

A team does not orient itself solely by official rules. It observes how its leadership reacts. When a leader's first response to bad news is to look for someone to blame, those present register the message. When they brush off a legitimate question with impatience, employees learn to hold back similar questions in future.

Equally significant is how leadership deals with its own uncertainty. Anyone who never admits to not knowing something sets an example that others cannot follow without withholding information. The ability to name an ambiguity openly is therefore not a weakness. It can be a precondition for joint problem-solving.

A helpful question is: "Which assumption in our plan could be wrong?" It opens up more space than the prompt: "Are there any objections?" At the end of a long meeting, the second question can easily sound like an invitation to finally wrap up. The first makes the search for counter-arguments part of the task.

What is decisive is the reaction that follows. Anyone who asks for objections must also deal with them. Otherwise the new openness is quickly exposed as a ritual.

From feedback to decision

Not every difficulty raised can be resolved immediately. But every relevant piece of feedback deserves recognisable handling. It should be clear who will examine it, when a decision is expected and how the outcome will be reported back.

A team can use short, recurring formats for this. What matters is less the tool than the commitment. Even a joint retrospective is worthless if the same problems are repeatedly mentioned without a responsible person reacting to them.

Leadership must also set limits. Endless discussion is no better alternative to enforced harmony. After a fair examination, someone has to decide. Those involved may continue to hold a different opinion, but are obliged, within their roles, to help implement a lawful and clearly communicated decision. New significant risks must nevertheless still be able to be raised again.

The combination of open discussion and clear decisions is more difficult than the two extremes: authoritarian top-down rule or non-committal talk without consequences.

Why anonymous channels alone are not enough

It is sometimes suggested that complaints and ideas for improvement be collected anonymously. This can make sense in strained environments. It offers an additional way of making information visible, especially where there are power imbalances or fear of consequences.

But an anonymous form does not repair a dysfunctional culture of discussion. If the official handling of dissent remains unchanged, all that emerges is a second channel for information that nobody wants to put a face to in the meeting.

Such a channel must be operated confidentially, securely and transparently. In the case of serious allegations, harassment or unlawful conduct, separate protection and reporting procedures may be required. An ordinary team meeting does not replace these procedures.

For everyday substantive risks, the long-term task remains: people must experience that a respectful warning is welcome and leads to a visible response.

Open language also protects against false harmony

A team can get on well and still avoid important conflicts. Friendliness is valuable, but it is not enough for difficult decisions. When everyone nods, very different reasons can lie behind it. Agreement, uncertainty, resignation, politeness or fear look similar from the outside.

Leadership should therefore not count visible agreement alone. More interesting is whether relevant counter-arguments were genuinely examined. Who was heard? Which alternatives were rejected? What remains open? And can people say, after the decision, why it was made?

An organisation does not need constant conflict. It needs the ability to endure disagreement in such a way that better insights emerge from it.

Criticism also needs to be cross-checked

Not every critical statement is correct. Employees may overestimate risks, defend interests or have incomplete information. Anyone who wants to create an open culture therefore does not have to adopt every warning. But they must examine the warning before rejecting it.

Good handling of dissent distinguishes between observation, interpretation and demand. What was actually established? What assumption do we derive from it? What consequence do we propose? Through this separation, an accusation may become a question that can be tested.

The role of professional authority also remains important. A team should not vote on technical safety requirements as if they were matters of taste. Knowledgeable people must explain what is mandatory, what uncertainty exists and which options are permissible. Open communication raises the quality of a decision; it replaces neither expert review nor responsible decision-making authority.

A leadership task, not a test of courage for employees

I have little time for shifting the responsibility for open communication exclusively onto those who have to take a risk. Of course employees need integrity and a willingness to raise problems. But if the organisation responds to concerns with disparagement, ignorance or sanctions, the problem is not solved by a workshop on courage.

Leadership bears a particular responsibility for shaping the conditions of the conversation. It must distinguish criticism from personal attack, make risks visible, give answers and stand by decisions. It must also be able to correct its own mistaken assumptions.

A team is not healthy because nobody disagrees. It is healthy when relevant problems can be voiced, taken seriously and dealt with.

The first improvement therefore does not consist in yet another call to be open. It consists in handling the next uncomfortable concern in such a way that people see: here, there is a point in speaking the truth.

Related insights