What is psychological safety?

Psychological safety is a shared belief among team members that it is safe to take interpersonal risks: to ask a question, admit a mistake, disagree or propose an unfinished idea without being humiliated or punished. The definition comes from Harvard professor Amy Edmondson, who introduced the construct of team psychological safety in a 1999 study of 51 work teams. Teams with higher psychological safety showed more learning behaviour, and that learning behaviour was linked to better team performance.

That finding explains the title of this article. In Google's internal research on what makes teams effective, who was on the team mattered less than how the team worked together, and psychological safety came out on top. For managers and founders, this is good news: it is something you can build, not something you have to hire.

Where did the idea of psychological safety come from?

Low psychological safety rarely announces itself. It shows up as people doubting they belong and stress they keep to themselves instead of raising problems early.

It started with a result that looked wrong. As a doctoral researcher, Edmondson studied medication errors in hospital patient-care teams. She expected that better teams would make fewer mistakes. In her own account, "the data were saying the opposite of what I'd predicted. Better teams appeared to have higher, not lower, error rates."

Her published study (Journal of Applied Behavioral Science, 1996) found differences between units not only in how often errors occurred, but in how likely they were to be detected and learned from. Her interpretation, which she later described in detail, was that better teams probably did not make more mistakes; they were more able to talk about them. In teams where admitting an error felt dangerous, errors were still there, just hidden.

That is the core business case. Problems you do not hear about are the most expensive ones.

What did Google's Project Aristotle find?

Google's People Analytics team studied 180 of its own teams, 115 project teams in engineering and 65 in sales, to understand what made some more effective than others. According to Google's re:Work guide, five dynamics stood out:

DynamicThe question it answers
Psychological safetyCan we take risks on this team without feeling insecure or embarrassed?
DependabilityCan we count on each other to do high-quality work on time?
Structure and clarityAre goals, roles and plans clear?
MeaningIs the work personally important to each of us?
ImpactDo we believe the work matters?

Psychological safety was the most important of the five. Just as striking was what did not matter much: Google found that factors such as colocation, consensus-driven decision-making, extroversion, individual performance, workload size, seniority, team size and tenure were not significantly connected with team effectiveness in its data.

One caveat: Project Aristotle was an internal company study, not a peer-reviewed paper. Its findings are consistent with academic research, but it is best read as one well-documented organisation's experience.

What does the wider research say?

The academic evidence is broader than one company. A meta-analysis by Frazier and colleagues in Personnel Psychology (2017) pooled 136 independent samples covering more than 22,000 individuals and nearly 5,000 groups. It mapped what predicts psychological safety and what it predicts in turn, including task performance and helpful behaviour beyond formal duties, and examined whether it adds something distinct from related ideas such as work engagement and good leader relations.

Is psychological safety just about being nice?

No, and this is the most common misunderstanding. Edmondson's definition is about interpersonal risk, not comfort. A psychologically safe team can be demanding. People disagree openly, give direct feedback and hold each other to high standards, precisely because they are not afraid that doing so will cost them their reputation.

What psychological safety is not:

  • Not lowering standards. It is about being able to say "this is not good enough yet" without fear.
  • Not avoiding conflict. Task conflict is healthier when people trust it will not turn personal.
  • Not therapy at work. Managers do not need to become counsellors.
  • Not guaranteed comfort. Learning, admitting mistakes and hearing criticism will still feel uncomfortable.

How can managers build psychological safety?

Psychological safety is built in small, repeated moments, most of them in ordinary meetings. A few practices tend to shift how a team behaves:

Manager behaviourWhat the team learns
Asking "what am I missing?" before decidingDisagreement is wanted, not tolerated
Admitting own mistakes out loudErrors are information, not shame
Thanking people for bad newsRaising problems early is rewarded
Responding to failure with "what did we learn?"Experiments are safe if they are thoughtful
Making sure quieter voices are heardStatus does not decide whose idea counts

Some practical starting points:

  • Frame work as learning. Say explicitly that a project is uncertain and you need everyone's input to get it right.
  • Run blameless reviews after incidents, focused on the process rather than on who to blame.
  • Watch your first reaction. The way you respond the first time someone brings you bad news sets the rule for everyone watching.
  • Ask, then wait. Silence after a question is often people deciding whether it is safe to speak.
  • Separate people from performance. Be clear about expectations while showing respect for the person.

How does psychological safety connect to mental health?

Psychological safety is a team concept, not a clinical one, but the two meet in daily work. When people cannot admit they are overloaded or struggling, problems stay hidden until they become absences or resignations. The WHO's 2022 guidelines on mental health at work recommend mental health training for managers so they can recognise distress in their teams and respond, and address work-related stressors. A team where it is safe to say "I'm not coping this week" gives managers the chance to act early.

Where does Dzeny fit?

Psychological safety is built by people, not by software. Dzeny is an AI-based mental wellbeing app that individuals use privately; it cannot make a team safe. What it can do is help an employee prepare for a hard conversation, sort out what they actually want to say to a manager, and manage the anxiety that often makes speaking up feel risky. That is a support for individuals inside a culture that leaders are responsible for building.

The bottom line

The best teams are not the ones with the most impressive CVs. They are the ones where people can say "I don't know", "I made a mistake" and "I think we're wrong" without fear. That is psychological safety at work, and it is mostly built by managers, one meeting at a time.

⚠️ Important

This article is for informational purposes only and is not a substitute for professional medical or psychological advice. If you or someone you know is in crisis in the US, call or text 988 (Suicide and Crisis Lifeline, 24/7). Elsewhere, contact your local emergency number.