Article
Below-the-Surface Leadership

Strong teams: why maximum safety is counterproductive

Raymond Honings 23 March 2026
A leadership team using the language of psychological safety without having built the underlying capacity.
Summary

Strong teams do not maximise safety. A board in Germany told me collectively that anything could be said here, and individually every member without exception said they held things back. That gap is not a communication problem but a maturity problem: the team had the language of safety, not the capacity for it. The language takes two meetings to learn, the capacity takes years to build.

Key Insights
  • The difference between language and capacity of safety is bigger than teams think. The words can be right while the capacity to carry them is missing.
  • Maximum safety does not create strong teams. It creates fragility: feedback is softened, hard topics stay unsaid, conflict is avoided to preserve harmony.
  • The real question is not 'do we feel safe?', but 'how mature are we under pressure?'. Personal, relational and structural maturity decide whether safety holds.

Strong teams do not maximise safety.

A board in Germany

A few years ago I was coaching the board of a manufacturing company in Germany. Openly and honestly, they all said the same thing: anything can be said here. Nobody holds back.

Then I spoke to them individually.

What I heard surprised me. Not because it was unusual. Because it was identical. Without exception, every person told me they did not dare to say everything.

That gap is not a communication problem. It is a maturity problem.

Language versus capacity

The team had created the language of safety. Not the capacity for it.

And that is a crucial difference. Most teams I encounter already have the language. 'Anything can be said here.' 'We trust each other.' The words are right.

What is much rarer is the capacity behind those words. The ability to stay present when the conversation becomes uncomfortable. To stay connected when the answer is uncomfortable. The language takes two meetings to learn. The capacity takes years to build.

That difference is not just nuance. It decides whether a team holds in the first difficult situation or quietly falls apart. A team with language without capacity sounds strong in a retreat and collapses as soon as it gets hard. A team with capacity without language often works better than it can name.

When safety becomes the highest goal

When safety becomes the highest goal, something quietly goes wrong.

  • Feedback gets softened.
  • Hard topics stay unsaid.
  • Conflict gets avoided to preserve harmony.

That may feel safe. But it creates fragility.

A team that avoids conflict to protect the relationship protects the relationship by removing exactly what makes it grow. No relationship deepens without occasional friction that gets addressed. Anyone who switches off the friction also switches off the deepening mechanism. The team feels harmonious while it quietly becomes superficial.

What strong teams actually do

In genuinely strong teams I see something different.

  • People tolerate difference.
  • They stay human towards each other when it gets uncomfortable.
  • They address tension instead of suppressing it.
  • They regulate themselves instead of blaming the environment.

None of those features asks for perfect communication. All of them ask for the willingness to stay in the room when things get hard. A team with that willingness needs less safety ritual, because it is not afraid of the moments the ritual is meant for.

Three forms of maturity

Psychological safety is not the starting point. It is often the by-product of something deeper.

Personal maturity: the ability to stay present under pressure. Not slipping into defensiveness, not fleeing into silence, not attacking to cover your own vulnerability.

Relational maturity: the capacity to stay connected when things get uncomfortable. To keep moving towards the other even when they say something you do not want to hear, without damaging the relationship.

Structural clarity: agreements that hold when stakes are high. How do we make decisions, how do we deal with disagreement, what do we do when someone crosses a line. Not as bureaucracy, but as shared ground under feet that would otherwise slip.

The different question for teams

The real question for teams is not 'do we feel safe?' but 'how mature are we under pressure?'.

The first question gets a social answer. People often rate themselves higher than they actually function. The second question gets a behavioural answer. People look at what actually happens in difficult moments and build from there. The question shapes the type of team you get.

In every country where I work, from Germany to South Korea to the US, this is the gap I encounter most. The appearance differs per culture, the mechanism is the same everywhere. Teams know the words, but the capacity underneath is thinner than the words suggest.

This week: one conversation

This week: one conversation. One person. One question you have avoided.

Not to prove something. Not to make a statement. To notice what happens when you stop managing the answer.

That is the laboratory in which maturity grows. Not in an offsite, not in a training. In an ordinary working week, in a conversation you would rather have avoided, with a person who probably does not see it coming either. An hour that looks small, and that makes the difference between a team that has the language of safety, and a team that builds the capacity underneath.

A Take-Home Message

The real question for teams is not 'do we feel safe?', but 'how mature are we under pressure?'.

This week: one conversation. One person. One question you have avoided. Notice what happens when you stop managing the answer.

Frequently Asked Questions

What is the difference between the language and the capacity of psychological safety? +
Language is what a team says about itself. 'Anything can be said here.' 'We trust each other.' Capacity is what the team can actually carry when things get uncomfortable. A team can be fluent in the language and at the same time have no capacity, because the practice of staying connected under pressure is not yet there. The language takes two meetings to learn. The capacity takes years to build.
Why is maximum safety counterproductive? +
Because a team that sets safety as its highest goal implicitly discourages anything that could disturb safety. Feedback gets softened, hard topics stay unsaid, conflict gets avoided. On the surface it looks peaceful. Underneath, small unsaid things stack up, until the team becomes fragile for the first real test. Safety is a precondition, not an end goal.
What is maturity under pressure in a team? +
The ability to stay present and connected when the work becomes uncomfortable. Personal, that you do not walk away, shut down or attack as soon as tension rises. Relational, that you keep moving towards the other when they say something you do not want to hear. Structural, that the team's agreements hold even when stakes are high. Maturity is not a character trait, it is a capacity that can be practised.
How do you recognise the difference between a safe team and a mature team? +
A team that is safe in name avoids conflict. A mature team addresses it. A team that is safe in name softens feedback to almost nothing. A mature team brings the uncomfortable to the table and stays in the room afterwards. A team that is safe in name regulates the environment. A mature team first regulates itself. The difference shows within one difficult conversation, even though it can take years to move from the first to the second.
How do you start building capacity instead of only language? +
By starting one concrete exercise. Identify one conversation you have avoided, with one specific person, about one specific question. Have that conversation this week, without trying to manage the outcome. Notice what happens in you and what happens in the other. That is not a technique. It is a laboratory in which the capacity that the language pretends to already have actually emerges.
Raymond Honings
About the author

Raymond Honings

Raymond is the founder of Seemotion. He works with managers and leadership teams across cultures, helping them build self-reliant teams that perform under pressure. Over the past years he has worked with more than 1,000 managers worldwide. Today most of his work takes place in Asia, mainly in Korea, Taiwan, China and Japan.