How to build psychological safety in teams: 7 research-backed steps

A release slips. In the retro, someone says they saw the risk in the first sprint and didn’t raise it. Nobody punished them for anything. They had seen a colleague push back once and get ignored for the rest of the week. This guide is for the manager in that retro. It gives seven steps you can start in your next meeting, in the order you’d do them. None of them needs a budget, and the free online table covers the round at the end.

What you’re building

Amy Edmondson defined team psychological safety as “a shared belief held by members of a team that the team is safe for interpersonal risk taking.” In her study of 51 work teams in a manufacturing company, that belief went with more learning behavior, and learning behavior carried its link to team performance (Edmondson 1999). Two words in the definition matter for a manager. “Shared” means one person feeling safe isn’t enough. “Risk taking” means the test is what people do: ask, disagree, admit a mistake. A 2023 review of the field sorts later research into four themes: getting things done, learning behaviors, improving the work experience, and leadership (Edmondson and Bransby 2023). The steps below sit in the last one.

1. Name the risk you want people to take

“Speak up” is too wide to act on. Pick one concrete risk that matters for your team this month. It could be flagging a deadline you doubt, saying “I don’t know” in a planning call, or reporting a bug you caused. Say it at the start of a meeting in one sentence: “If you think a date is wrong, I want to hear it in this meeting, not after.” People can’t take a risk they can’t see.

2. Ask for input in words and in deeds

Nembhard and Edmondson studied 23 neonatal intensive care units. They defined leader inclusiveness as “words and deeds exhibited by leaders that invite and appreciate others’ contributions.” In their data, profession-based status went with more psychological safety. Leader inclusiveness changed how strongly status was tied to safety, and safety linked inclusiveness to engagement in improvement work (Nembhard and Edmondson 2006). In a team, status is seniority, a job title, or being the one who wrote the code. The words part is asking. The deeds part is what you do with the answer.

Ask the person with the least status first, before you share your own view. Use an open question: “What would you change in this plan?” Then wait. Silence feels long to the person who asked and short to the person who’s thinking.

3. Thank people for bad news before you fix it

The first reaction to bad news can decide whether there’s a second piece of it. One sentence of thanks comes first, then a question about the facts: “Thanks for raising it. When did you first notice?” Save the fix for after you’ve heard the whole thing. If the news is about your own decision, say so out loud. That can carry more weight than any statement about open doors.

4. Even out who talks

Woolley and colleagues tested 699 people in groups of two to five. A group’s performance across many tasks correlated with how evenly conversational turns were spread, and with members’ social sensitivity. It was not strongly tied to the average or highest individual intelligence (Woolley et al. 2010). The study measured group performance, not safety. Still, it suggests that the pattern of who talks is worth watching.

There are three cheap ways to even out turns. Go around in a fixed order, so nobody has to fight for a slot. Give everyone a few minutes to write before anyone speaks. Keep a tally of who talked in your last three meetings, and look at who’s missing.

5. Make passing free

An invitation only counts if a no costs nothing. The Thesis rules open with this line: “Before you start, agree together how passing works.” At work, agree that anyone can pass without a reason, and say it before the first turn. Then let people pass without comment. A short answer counts too. The rule card puts it in one line: “A short answer is a full answer. You can always ask for more.”

6. Practice with small risks first

Speaking up can start smaller than telling a manager the plan is wrong: saying something minor and watching what happens. A short round at the start of a meeting gives that practice. Each person picks a word and says a few sentences about it. The risk is low, everyone gets a turn, and the manager gets to show how they react to answers they didn’t expect. For prompts for that slot, see our check-in questions for team meetings.

Trust
Window
Card 34: Trust / Window. Tap to turn it over.

Trust has Window on its back. For a team, Trust can be about a handover that went well or a colleague who covered a shift. The Window side gives anyone who’d rather stay light a way in: the view from their desk, or a window they keep open on their screen all day.

Courage
Bicycle
Card 29: Courage / Bicycle. Tap to turn it over.

Courage has Bicycle on its back. It fits this step because answers can be about a first try: a first presentation, a first week in a new job. Someone who picks the bicycle might talk about learning to ride, which is a story about falling in front of other people.

7. Show what changed because someone spoke

Speaking up can feel pointless when nothing follows. Close the loop in the next meeting. Name what was raised, by whom if they’re fine with it, and what you changed. If you changed nothing, say why. This step turns one person’s risk into evidence for the rest of the team.

Why the obvious advice doesn’t stick

Telling people “my door is always open” is easy. People may judge from what they’ve seen happen in meetings. One person on a developer forum describes giving softened feedback and getting ignored for a week afterward. Another describes a whole career of staying quiet for fear of looking dumb. A speech may not change either of their minds. Watching several people take a risk and come out fine can. That’s why the steps above are things you do in the room, many times.

Questions that invite a small risk

The questions below ask for an opinion or a doubt, and each one can be answered in one sentence:

  1. What’s one thing in this plan you’d question?
  2. Where are we most likely to be wrong?
  3. What did you expect to happen this week that didn’t?
  4. What’s something you’d like a second opinion on?
  5. What would you do differently if this were your project?
  6. Which part of this are you least sure about?
  7. What’s a question you held back in the last meeting?
  8. What should we stop doing?

Running the word round

With the deck or the online table, each turn follows the same steps. Draw a card, choose the idea or the thing, roll the die, and look at the word from that side. The die has six plain words: MEMORIES · BODY · PEOPLE · VALUES · CHILDHOOD · FUTURE. The only instruction is “Look at the word from that side.” The others ask what they’re curious about. The rule card gives three examples: What did that feel like? Who else was there? Has it always meant that to you?

Roll the die

Honesty is a third word for a team round, with Radio on its back. For more on running it at work, see Thesis for teams and classes. For the studies behind the deck, see the research. To play on paper, see the rules and the box. Related: psychological safety examples: 12 everyday moments at work.

For your next meeting, write down the one risk from step 1. Say it at the start, then ask the least senior person in the room what they think, and wait.