
← All articles
Team connection
Psychological safety is more than being nice
Psychological safety is often mistaken for politeness. What the idea really means, how to spot it on an ordinary Tuesday, and why the moment after bad news matters most.

Joost
Co-founder & CEO
·
7 min read
Picture the end of a project review. The plan is on the screen, the project lead asks whether anyone has concerns, and the room goes politely quiet. A few people nod. The meeting finishes early, which everyone appreciates. Twenty minutes later, in a private chat, two colleagues agree that the timeline is impossible and the second phase makes no sense. Nobody was rude. Everyone was nice. And the one thing the team most needed to hear was said in the wrong place.
Few ideas have travelled from research into everyday HR language as quickly as psychological safety, and somewhere along the way it has come to mean something softer than it should: a team where everyone is pleasant, nobody gets challenged and difficult conversations are politely avoided. In my experience, the teams that feel safest are rarely the most polite ones. They are the teams where someone can say ‘I think this is wrong’ or ‘I got that badly wrong’ and the room leans in instead of going stiff. In the sessions we run at Uncommon Club, I can often see the difference within minutes, usually in how a group reacts the first time something goes wrong.
Safety means you can take a risk out loud
The idea is most closely associated with Amy Edmondson, who has studied it at Harvard Business School for decades. In her work, psychological safety is a shared belief within a team that it is safe to take interpersonal risks: to ask a question that might sound naive, admit a mistake, disagree with someone more senior, or raise a concern before it becomes a crisis. Every item on that list involves a small moment of exposure. Safety is not about removing the risk of speaking. It is about what happens to you after you have spoken.
One story from her early research is worth knowing. Studying hospital teams, she expected the units with better leadership and relationships to report fewer medication errors. The data seemed to show the reverse. Her explanation was that the stronger teams were not making more mistakes; they were more willing to report them. That is the heart of it. A safe team is not one without problems. It is one that sees its problems early, because people are prepared to name them.
Safe is not the same as comfortable
Edmondson draws a distinction that clears up most of the confusion. Psychological safety and high standards are two separate things, and a team can have any combination of the two. With little of either, you get apathy: people do what is asked and keep their heads down. Safety without standards gives you comfort, a friendly atmosphere in which nobody is stretched. Standards without safety give you anxiety, where expectations are high and being wrong in public feels expensive. Only the combination of both produces what she calls the learning zone, where people aim high and talk openly about what is getting in their way.
Most teams that worry about psychological safety are not stuck in comfort. They are in anxiety: real pressure, ambitious targets and an unspoken sense that it is wiser to keep a problem to yourself until you have fixed it. The answer is not to lower the standards, or to be nicer. It is to make it normal to talk honestly about how the team is going to meet them. In that setting niceness can even make things worse. When everyone is careful to be pleasant, a disagreement starts to feel like a breach of manners rather than a contribution.

You can see it on an ordinary Tuesday
Surveys have their place, but you learn more by watching how your team behaves when nothing special is happening. In a safe team, bad news arrives early rather than in the week before a deadline. People ask basic questions in front of each other, including the brave one about what an acronym actually stands for. Someone disagrees with the boss in a meeting, and the conversation carries on normally afterwards. Mistakes get described in the first person, ‘I missed that’, rather than in the passive voice, where mistakes were somehow made by nobody.
The signs of its absence are just as visible once you look for them. The real discussion happens in private messages after the meeting. Every status update is green until it suddenly turns red. People check with each other before they raise something with you, and feedback only ever travels downwards. None of this means anyone is behaving badly. It means the team has quietly learned what it costs to speak, and is adjusting accordingly.
The moment after matters more than the speech
Edmondson describes the leader’s part in three broad moves: setting the stage, inviting participation and responding productively. Setting the stage means naming what is uncertain before the work begins: ‘We have not done this before, we will get parts of it wrong, and I need to hear about it early.’ Work framed as a learning problem invites questions, while work framed as pure execution makes every question sound like a lack of competence. Inviting participation means asking questions you cannot answer yourself, such as ‘What are we missing?’ or ‘What would make this fail?’, and asking them before you share your own view, so people respond to the problem rather than to you.
The third move is where most of the teaching happens. How you react when someone brings you bad news shows the whole team what happens to messengers, far more clearly than anything you say about openness. Thank the person before you start solving the problem, and separate the mistake from the person. Not every failure deserves the same response, either. In her later writing Edmondson distinguishes basic mistakes in familiar work, which good systems can usually prevent, from the intelligent failures that come from trying something new. Treating both the same way, with blame or with a shrug, sends the wrong signal.

The stage rehearses the moment after
This is where my own world comes in. Performers know that a person on stage is only as brave as the audience lets them be, a thought I followed further in a piece on what a stage teaches about speaking up. In an Impro Theatre session, scenes fall apart all the time. Someone forgets a name, contradicts a partner or freezes halfway through a sentence. What the group learns, quite quickly, is that the moment after the mistake decides everything. If the others build on it, the mistake often turns into the best scene of the afternoon. If they wince, the next person plays it safe.
I want to be honest about the limits here. One afternoon with an artist will not make a team psychologically safe. Safety is built or worn down in hundreds of small daily interactions, and most of them involve the team lead. What a well-held session can offer is a shared reference point, less a technique than a memory: we have seen each other get it wrong, and it was fine. That memory only helps if you connect it to real work in the days afterwards, for instance by asking what makes it easier or harder to raise a concern in this team, or when someone here last changed your mind.
Start with the next piece of bad news
If you lead a team, you do not need a programme to begin. Pick the next time someone brings you a problem, and decide in advance how you will respond: a thank you first, a question second, and the solution some time after that. Then notice how long it takes before the next problem reaches you a little earlier than the last one did.
Psychological safety is less a feeling to install than a habit to practise, mostly in how we answer each other on difficult days. Being nice is pleasant. Being safe is useful. The best teams I know manage both, but when they have to choose in a given moment, they choose the honest sentence, said kindly, in the room where it can still change something.
Psychological Safety
Trust
Leadership

About the author
Joost
Co-founder & CEO
Joost leads Uncommon Club’s brand, proposition and commercial direction, shaping how the collective’s artistic practice becomes something companies understand, trust and bring into their teams. He co-founded the club after a cycling trip through Patagonia.
Keep reading




