Psychological Safety: Edmondson's Research Explained
Have you ever sat in a project meeting where everyone nods, no one asks the uncomfortable question, and the problems only surface when it's too late? Then you've seen what a lack of psychological safety does to a team.
The concept had its scientific breakthrough in 1999, when Harvard researcher Amy Edmondson published her study of work teams at a manufacturing company. Her article is today one of the most cited in organizational research, and the concept has become one of the most important tools for understanding why some teams learn and grow while others stagnate.
What does the research say?
Edmondson defines psychological safety as a shared belief within the team that it is safe to take interpersonal risks: to ask a stupid question, admit a mistake, ask for help, or challenge a decision, without being punished or ridiculed. Note that it is a property of the team, not of the individual. The same person may speak up in one team and fall silent in another.
In her study of some fifty teams at a manufacturing company, Edmondson found that teams with high psychological safety showed more of what she calls learning behaviors: they asked for feedback, talked openly about errors, experimented, and sought help. These behaviors were in turn linked to better team performance. So the chain is: safety enables learning behaviors, and learning behaviors drive results.
It's important to understand what psychological safety is not. It is not the absence of standards, mere niceness, or the absence of conflict. Edmondson's point is rather the opposite: safety is what makes high standards and honest disagreement possible, because people only deliver their best thinking when they don't have to spend energy protecting themselves.
What does this mean for you as a project manager?
Go first yourself. Safety in a team is shaped most by how the person with the most power behaves. When you as a project manager say "I misjudged this" or "what am I not seeing here?", you lower the cost for everyone else to do the same. If you wait for the team to open up first, it won't happen.
React the right way to bad news. The decisive moment is when someone tells you about a delay or a mistake. If you respond with irritation, you train the team to hide problems; if you respond with "thanks for telling me now, what do we need to do?", you train them to raise the alarm early. In projects, early warnings are the difference between an adjustment and a crisis.
Actively ask for dissenting views. Silence does not mean agreement. Ask questions like "what speaks against this plan?" or "who sees a risk we haven't talked about?", and let the question hang until someone answers. That makes disagreement an expected part of the work instead of a risk.
How to practice this
The same principle applies to your own development: you learn difficult conversations best in an environment where mistakes cost nothing. That's why consequence-free practice is such a powerful form of training: you can try the direct phrasing, fail, and try again without damaging any relationship. In Project-simulator, you practice exactly these kinds of conversations against AI counterparts and get feedback grounded in your own words. Try it free for a week.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days