Psychological Safety at Work: What It Means and How Teams Build It

In this article
There is a moment I have learned to watch for when I sit in on team calls for stories about distributed work. The manager finishes walking through a plan, asks "Any concerns?", and the call goes quiet. Sometimes the silence means agreement. Often, when I talk to people afterward, it turns out someone saw a problem and decided that saying so was not worth the risk.
That gap between noticing and saying is what psychological safety is about. The phrase gets used loosely now, sometimes as a synonym for kindness, sometimes as a word on a values poster. This piece goes back to where it came from: what it means in Amy Edmondson's research, what Google's Project Aristotle reported, how it plays out when a team is spread across offices, kitchens and time zones, and what a manager can do about it on an ordinary Tuesday.
What psychological safety means
The definition most researchers use comes from Amy Edmondson's 1999 study of work teams. A 2025 systematic review in Applied Nursing Research quotes it as "a shared belief held by members of a team that the team is safe for interpersonal risk taking," and glosses it as team members being comfortable and confident speaking up about their concerns. Each part of that definition does work.
It is shared. Psychological safety belongs to a team, not to a person's temperament. Two teams in the same company, under the same policies, can feel completely different, because the climate is built by how a particular group and its manager behave with each other.
It is a belief. It is an expectation about what will happen if you speak, and it is formed by what has happened before. If the last person who admitted a mistake got a sarcastic reply in front of everyone, the whole team learned something from that, whether or not anyone meant to teach it.
It is about interpersonal risk. The risks are small and daily: asking a question that might sound basic, admitting an error, disagreeing with the most senior person in the meeting, saying a deadline will slip, floating an idea that might be wrong. In later work, quoted in a 2022 paper in Frontiers in Psychology, Edmondson describes people in psychologically safe environments as believing that others will not penalize them or think less of them for making mistakes, or resent them for asking for help, information or feedback.
What it is not
- It is not niceness. Psychologically safe teams often disagree more openly, because people are willing to say the awkward thing.
- It is not lower standards. The combination to worry about is high pressure with low safety, where people meet targets by hiding problems. High standards with high safety is the combination good teams aim for.
- It is not immunity from feedback. Performance problems still get addressed. What changes is how: privately, specifically, and without humiliation.
- It is not personal confidence. A confident person can sit on an unsafe team and stay quiet, and a shy person can speak up freely on a safe one.
What Google's Project Aristotle found
According to a 2026 Frontiers in Psychology article on team science, Google studied 180 of its own teams between 2012 and 2014, looking at hundreds of team attributes. The company started with assumptions about what made teams succeed, such as having the smartest or highest-performing individuals, matching or complementing temperaments, or experienced managers. What the most successful teams actually had in common were psychological safety, dependability, role clarity, meaningful work, and a belief that members' efforts were making an impact.
Google presented psychological safety as the first of those five key dynamics, as a 2021 study in Nursing Open notes, citing a 2015 write-up Google published on its re:Work site. The 2025 review linked above describes the Google findings as showing the importance of leaders' psychological safety practices (communication, encouraging participation, and proactively acknowledging team members) in raising productivity and innovation.
Three things are worth keeping in mind when you hear the study retold:
- It is one company's look at its own teams. It carries weight because it lines up with a much larger body of academic work. The 2022 Frontiers paper, for instance, summarizes a 2017 meta-analysis by Frazier and colleagues that linked psychological safety to task performance, information sharing, commitment, learning behavior and creativity.
- Behavior mattered more than who was on the team. That is good news for managers, because behavior can change. You cannot hire your way to a safe team.
- Safety was one of five. A team where everyone speaks up but nobody follows through, or nobody knows who owns what, is not working either. Dependability and clarity sit right next to safety on the list.
What it looks like on an ordinary day
Psychological safety is easiest to see in small moments. Here is how a few of them tend to go on teams where it is present and where it is missing.
| Moment | Where it is present | Where it is missing |
|---|---|---|
| Someone spots their own error in a shared file | They post it in the team channel with the fix | They quietly patch it and hope nobody noticed |
| A new hire doesn't know an acronym | They ask in the meeting | They search for an hour, then guess |
| A project will miss its date | The owner flags it two weeks out | It surfaces the day before, all at once |
| The manager's plan has a flaw | Someone says "Can I push back on step three?" | People nod, then complain in private messages |
| A customer complaint comes in | The team asks what in the process allowed it | The team looks for someone to blame |
Psychological safety in remote and hybrid teams
Distance does not create or destroy psychological safety. What it does is thin out the signals people use to judge whether speaking up is safe, and magnify the small moments that remain. In my reporting on distributed teams, the same few pressure points come up again and again.
Silence is harder to read
In a conference room, a manager can see a frown or a glance across the table. On video, silence after a question could be agreement, audio lag, or someone deciding to stay out of it. Cameras off is not a warning sign by itself (people have plenty of good reasons), but it does remove one more cue. The fix is to stop treating silence as consent. Ask questions that need an answer ("What is one risk you see in this plan?"), and collect input in the chat or a shared document at the same time, so the first person to speak does not set the direction for everyone else.
Hybrid meetings tilt toward the room
When some people are together and others dial in, the people in the room tend to talk first, finish each other's sentences and keep the conversation going in the hallway afterward. Remote colleagues end up commenting on decisions that are already made. Teams that handle this well invite remote voices first, have everyone join from their own laptop when the meeting is mixed, ask one person to watch the chat, and write decisions down where everyone can see them.
Writing things down raises the stakes
Asynchronous work runs on written messages, and written disagreement in a public channel feels permanent in a way a comment in a meeting does not. So dissent drifts into private messages to the manager, where nobody else learns from it. Leaders can lower the stakes by thanking people publicly for pushback and by posting their own corrections in the open: "I got the numbers wrong in yesterday's update. Corrected version here."
Time zones and timing
The person joining at 7 p.m. or 6 a.m. is tired and less likely to argue a point. Rotate meeting times when you can, and gather written input before the call so that people at the edges of the day can contribute when they are sharp.
The one-to-one carries more weight
Without hallway check-ins, a regular one-to-one is often the only private channel a remote employee has. Use part of it for questions that invite candor: "What is something we're not talking about as a team?" or "What would you change about how we run our meetings?" The companion piece on isolation in remote teams covers the rituals that keep that kind of contact going.
Practical habits for managers
None of these needs a budget or a workshop. They work because they are repeated until the team believes them.
- Say where the uncertainty is. "We haven't done this before, and I expect us to hit problems. I need to hear about them early." Naming the risk makes raising it part of the job rather than a complaint.
- Ask real questions, then wait. Count to ten in your head after you ask. Most managers fill the silence too soon.
- Make your first response to bad news a thank-you. "Thanks for flagging that. What do you need?" How you react to the first piece of bad news teaches the team what the second will cost.
- Go first with your own mistakes. If the most senior person on the call can say "I got that wrong," everyone else can too.
- Review the system, not the person. After something goes wrong, ask what in the process allowed it. Keep individual performance conversations separate and private.
- Close the loop. When someone raises a concern, tell them what happened to it, even when the answer is no and here is why. Ideas that disappear without a reply teach people to stop offering them.
- Spread the airtime. Notice who speaks and who doesn't. Invite quieter colleagues privately or through written input, rather than cold-calling them in front of the group.
- Deal with put-downs quickly. A peer's eye-roll or sarcastic remark, left alone, undoes a lot of good intentions. Address it privately and promptly.
- Keep expectations clear. Clear goals, owners and deadlines are part of safety, not its opposite. Remember that dependability and role clarity were on Google's list too.
Psychological safety is also what makes it possible for someone to tell you they are struggling. The guide to talking with employees about mental health covers what to say, and what to leave to professionals, when that conversation happens.
How to tell if it is missing
No single sign proves anything. A pattern of several is worth taking seriously.
- The meeting after the meeting. Agreement in the room, objections in private messages or on the walk back to desks.
- Bad news arrives late and all at once. Problems were visible weeks ago to the people closest to them.
- Mistakes are discovered, not reported. Errors come to light through a customer or another team.
- New hires go quiet. They ask plenty of questions in their first weeks, then stop.
- Ideas only travel downward. Suggestions come from senior people, and everyone else executes.
- Questions move to private channels. People ask the manager directly instead of asking in the team space.
- Survey results that look too good. Uniformly glowing scores, low participation, or comments along the lines of "nothing will change." The piece on reading engagement surveys for mental health signals explains how to read those patterns at group level.
If you want a wider view than one team, our workplace mental health self-check looks at culture and climate alongside awareness, access to care and leadership, and takes a few minutes.
Where mental health comes in
Psychological safety is not a mental health program, and it does not treat anything. But on teams where admitting difficulty is costly, people tend to hide that they are struggling until it has become serious. On teams where it is safe to say "I'm behind and I'm not doing well," managers hear sooner and can point people toward help sooner.
If someone on your team tells you they are struggling, listen, avoid diagnosing, and point them to the employee assistance program, their doctor or a licensed counselor. If they mention thoughts of suicide or seem to be in crisis, the 988 Suicide & Crisis Lifeline is available by call or text at 988, at any hour.
Two books for going deeper
How we chose: these two were picked on the authors' credentials and expertise, along with publisher information and published reviews. Edmondson is the researcher whose 1999 study gave the field its standard definition, and her book The Fearless Organization is written for leaders who want to put the research into practice. Brené Brown is a researcher who studies courage and vulnerability, and her book Dare to Lead focuses on trust and hard conversations for managers. Neither is a substitute for training or professional support.
If you only change one thing this week, make it your reaction to the next piece of bad news. Thank the person, ask what they need, and fix the problem in the open. The team will remember that reply long after they have forgotten the slide deck about values.



