How to build psychological safety in a team

Amy Edmondson's research put the term into general use, and Google's Project Aristotle made it famous by finding it was the factor its most effective teams had in common. Neither tells you what to say on Monday morning when someone finally admits the client has been unhappy for six weeks. That is what this guide is for: sentences, sequence, and what to do when it goes sideways.

What it is, and what it very much is not

Psychological safety is not comfort and it is not niceness. Teams with high safety usually argue more, not less, because disagreement stops being expensive. Four things it is not:

• Not lowering the bar. Edmondson's own framing pairs safety with high standards. Safety without standards produces a very pleasant team that ships nothing.
• Not everyone gets a veto. People need to feel heard, not obeyed. You can take a decision someone hates and keep safety intact, provided they know you heard the objection and why you went the other way.
• Not a survey score. The score is the result. What you do in the ten seconds after someone takes a risk is the cause.
• Not a workshop you attend once. It is a hundred small responses, most under ten seconds long.

The mechanism: the ten seconds after someone takes a risk

Safety is built and destroyed in the moments right after somebody sticks their neck out: they admit an error, question the plan, or say they do not understand. Whatever you do next is your team's actual policy on speaking up. Everything else is a poster in the corridor.

So the work is small and repetitive: notice the moment, and respond in a way other people can copy.

What you say in the ten seconds after someone brings you bad news is your team's real policy on speaking up. Everything else is decoration.

Go first, and be specific when you do

Managers are told to model fallibility, and most do it uselessly: "I'm not perfect either." That costs nothing, so it buys nothing. Going first means naming one recent, expensive mistake of your own, out loud, with the consequence attached.

Weak: "I make mistakes too, obviously." Better: "I got the launch date wrong last quarter. I anchored on the first estimate, I did not ask any of you to challenge it, and it cost us three weeks. If I do that again, say so in the room, not afterwards."

The first five minutes of your next team meeting

1. Name the change in one sentence. "I want to change how bad news travels on this team, and I need to go first."
2. Tell one real story against yourself. Recent, specific, with the cost named. Thirty seconds, no performance.
3. Make the ask concrete. Not "be open with me". Try: "I want to hear about a slipping deadline the week it starts slipping, not the week it lands."
4. State the guarantee and its limit. "Nobody gets punished for telling me early. Standards do not drop. The standards and the fear are separate things, and I am only removing one of them."
5. Stop talking. Expect silence the first time. Silence on day one is not failure, it is people checking whether you meant it.

Four questions that do most of the work

Most of what a manager needs here is asking rather than telling. These four are worth learning by heart, because in the moment you will not invent them.

• "What is the strongest argument against this?" Better than "any concerns?", because it asks for analysis rather than courage.
• "What would have to be true for this to fail?" Lets people voice a worry without having to own it as their personal objection.
• "What am I missing?" Only works if you visibly change something because of the answer. Ask it twice, ignore both answers, and you have taught the team that asking is theatre.
• "Who has a different read on this?" Assumes disagreement exists. "Everyone happy?" assumes the opposite and reads as a request to end the meeting.

This is ordinary active listening under pressure. The hard part is not knowing the questions. It is asking them when you are behind schedule and already sure you are right.

Run the meeting so that speaking up is cheap

Structure does more for safety than encouragement does. In sequence, for any decision that matters:

1. Collect written positions first. Two lines each, sent before the meeting. It removes the cost of being the first to say the unpopular thing.
2. Speak last yourself. Once the most senior person in the room has a view, you are no longer collecting opinions, you are collecting agreement.
3. Go round the room by name on the decision. "Vik, then Ana, then Tom." Open-floor questions get answered by the same three extroverts every week.
4. Ask for the unsaid before you close. "What did we not say in the last hour that someone will say in the corridor in ten minutes?"
5. Follow up within 48 hours. Act on one thing somebody raised and attribute it publicly: "We changed the rollout order because Ana pushed back on Tuesday." That sentence is worth a quarter of encouragement.

When it goes wrong

Four failure modes, in roughly the order they turn up.

1. Nothing happens for weeks. Normal, especially if the last manager punished candour. Recovery: shrink the question and move it one to one. "What is one thing about this project that quietly annoys you?" gets answers where "any feedback for me?" gets a shrug. Bring what you hear back to the group, with permission and credit.
2. Someone tests you, badly. The first real challenge usually arrives clumsily, in public, at the worst moment. Flinching once undoes a month. Recovery: buy time without retreating. "That is a real point, and I want to give it a proper answer rather than a defensive one. Can we come back to it at four?" Then come back to it.
3. Safety gets used as a shield. Someone underperforms and reaches for the language: "I thought this was a safe environment." Recovery: separate the two lines explicitly, in one breath. "You will never be in trouble for telling me something is going wrong. This is a different conversation: the work is not at the standard, and I need a plan from you by Thursday." Holding both at once is the job; the mechanics are in how to give constructive feedback at work and the SBI feedback model.
4. You are safe, your boss is not. Your team speaks up, you carry it upwards, and it comes back down as a reprimand. Recovery: be honest about the boundary rather than promising what you cannot deliver. "I can promise this room. I cannot promise what happens two floors up, and I am not going to pretend otherwise. Tell me anyway, and I will tell you what I did with it." Pretending the wider organisation is better than what your team can plainly see costs you more than the original problem did.
5. One senior voice dominates. The room can be safe for everyone except the four people sitting nearest the loudest person. Recovery: pre-brief them. "Tomorrow I am coming to you last, deliberately. I want the team's read before yours." People agree when asked in advance and bristle when corrected live.

How to tell whether it is actually working

Not from the engagement survey. Watch for behaviour that costs the speaker something:

• Bad news arrives earlier. You hear about the slipping deadline in week one instead of week six.
• Somebody corrects you in front of other people, and the meeting simply carries on.
• "I don't know" gets said out loud by someone who is not you.
• The meeting after the meeting gets shorter, because the real conversation happened in the meeting.
• The most junior person in the room asks a question without prefacing it with three apologies.

If none of that has shifted in a couple of months, the problem is rarely the team. It is one habit of yours that contradicts everything you said, and you will be the last person in the building to spot it.

Why reading this is not enough

None of this is complicated: a handful of sentences and a bit of meeting design. Managers still get it wrong because the moments arrive fast, in front of an audience, when you are stressed and defensive. Under that pressure people revert to the manager they had at 24, not the one they meant to be.

That gap closes through rehearsal and honest feedback: saying the line badly a few times somewhere low-stakes, having it played back to you, trying again. It is why experiential learning beats a slide deck on this topic, and why reading a guide like this one rarely moves behaviour on its own. Try one line in your next meeting, badly, and watch the ten seconds after somebody speaks.

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.