Psychological safety

The phrase goes back to Edgar Schein and Warren Bennis in the 1960s. It became a management staple through the research of Harvard's Amy Edmondson, who studied hospital teams in the 1990s expecting the best-performing units to record the fewest errors. The strongest teams reported more. They were not more careless, they were more willing to say what had gone wrong. That is the whole concept in one finding.

Why the simple definition misleads people

Read quickly, "safe to speak up" sounds like "nobody here gets upset". That reading has done real damage. Teams use psychological safety as a reason to soften feedback, avoid difficult conversations and treat discomfort itself as a breach of the rules. The result is a group that feels pleasant and learns nothing.

Safety is not the opposite of pressure. Edmondson pairs it with accountability, and the pairing is the point. High standards with low safety produces anxiety, and people hide problems until they explode. High safety with low standards produces a comfortable team that misses its numbers.

Psychological safety does not lower the bar. It is what makes a high bar survivable, because people can say "I'm stuck" before the deadline rather than after it.

The second misreading treats it as an individual quality, as if some people are simply braver. The same person will challenge a decision confidently in one meeting and say nothing in the next. What changed is not their courage. It is the room.

What it looks like in practice

In a team with psychological safety you routinely see:

• Someone says "I don't understand" in a meeting where everyone else is nodding, and nobody exchanges glances.
• Bad news travels upward early and unprompted, while it is still cheap to fix.
• A junior person contradicts a senior one on the substance, and gets a follow-up question rather than the same position restated more slowly.
• Mistakes are described in the first person, with specifics, not laundered into "there were some issues on the delivery side".
• Meetings contain visible disagreement, and decisions still close.

Absence is harder to spot, because low safety is quiet. It shows up as meetings that end early in unanimous agreement, real opinions arriving afterwards in private messages, questions phrased as compliments, and problems that appear fully formed as crises. A team that never disagrees in front of you is not aligned. It has moved the disagreement somewhere you cannot see it, which is what suppressed storming looks like.

Psychological safety vs the things it gets confused with

How to build it

Almost all of the work sits with whoever holds the most power in the room. Announcements do not move the number. Reactions do.

• Respond to the first bad news the way you want the tenth to arrive. Thank the person for the information before reacting to the information. One flash of visible irritation costs months.
• Frame the work honestly as uncertain. "We have not done this before and will get parts of it wrong" gives people permission to report the wrong parts. Calling it routine execution makes every problem look like somebody's failure.
• Say your own mistakes out loud, with detail. "I misread the brief and we lost two weeks" sets the standard for how specific others may be. Vague self-deprecation does nothing.
• Speak last, and ask questions you do not know the answer to. State your view first and you will only hear elaborations of it.
• Give quiet members structured airtime: written positions before discussion, or one round where everyone contributes before open debate. Good facilitation makes safety a process rather than a personality contest.
• Keep feedback about behaviour, using a repeatable structure such as the SBI model. Specific criticism is far easier to receive than a verdict on someone's character.
• Deal with the person who punishes candour. Everything else is theatre until the senior individual who humiliates people in public faces a consequence. Nothing teaches a team faster than watching what you tolerate.

How to tell whether you have it

Edmondson developed a short survey instrument, and most engagement surveys now carry a version of it: whether mistakes are held against you, whether tough issues can be raised. Scores are worth tracking, but behavioural evidence is more honest. Ask yourself, with dates:

1. When did someone last disagree with me in a meeting, in front of other people?
2. When did I last hear about a problem before it became urgent, from the person responsible?
3. Who told me I was wrong this month, and what happened to them afterwards?
4. Who has not spoken in the last three meetings, and had I noticed?

The limits of measurement are worth stating plainly. A survey about whether it is safe to speak up is answered by people deciding whether it is safe to answer, so unsafe teams tend to report better than they are. Averages also hide distribution: safety is usually lowest for the newest, most junior, remote or second-language members while the team score looks fine. Use the number to start a conversation, never as a verdict.

Common myths and mistakes

• "We ran a session on it, so we have it." It is rebuilt or lost every week, in ordinary moments, mostly by managers not thinking about it.
• "It means no negative feedback." The opposite. Safety is the precondition for feedback direct enough to be useful.
• "It protects poor performance." It exposes poor performance earlier, while the problems are still small.
• "Our team gets on well, so we're fine." Some of the least safe teams are the friendliest, because nobody will risk the friendship.
• "It's the same across the company." It is local. One manager can hold a safe island inside a fearful organisation, and destroy a safe team inside a healthy one.

This is why psychological safety is hard to teach from a slide deck and easy to demonstrate through experience. Put a team into a short challenge with a real chance of failure and within twenty minutes you learn who speaks, who withholds, and whose objection gets ignored. It is the same pattern they run at work, except that in a learning environment everyone can watch it happen.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.