Skip to main content
Psychological safety is the shared belief that the team is safe for interpersonal risk-taking. It means people feel able to speak up, ask questions, admit mistakes, and challenge ideas without fear of embarrassment, punishment, or rejection. Amy Edmondson at Harvard Business School coined the term and has spent decades researching it. Google’s Project Aristotle - a multi-year study into what makes teams effective - found psychological safety to be the single most important factor. More than individual talent, more than process, more than anything else 🧠

​
What it looks like in practice

A team with high psychological safety:
  • Surfaces problems early rather than hiding them
  • Challenges assumptions, including the leader’s
  • Asks “I don’t understand” without embarrassment
  • Admits mistakes without fear of blame
  • Tries new things knowing failure is a learning event, not a career risk
A team without it does the opposite. People say what they think the leader wants to hear. Problems stay hidden until they’re crises. Nobody challenges the plan in the room - they just don’t execute it well afterwards 💡

​
What creates it

Psychological safety is built primarily by leaders through their behaviour - specifically how they respond when someone takes an interpersonal risk. When someone admits a mistake and the response is curiosity rather than blame, safety goes up. When someone challenges an idea and the response is genuine engagement rather than dismissal, safety goes up. When someone asks a “stupid question” and gets a respectful answer, safety goes up. The inverse is faster: one public shaming, one idea dismissed with contempt, one mistake met with anger - and the team learns the lesson quickly. The asymmetry between building and destroying psychological safety mirrors trust 🙌

​
The performance paradox

Psychological safety is sometimes misunderstood as making people comfortable - keeping conflict low, avoiding hard conversations, accepting everything. That’s not it. Edmondson distinguishes psychological safety from comfort. High-performing teams are often highly challenging environments where standards are demanding and feedback is direct. What psychological safety provides is the belief that the challenge is in service of the work, not a personal attack. You can hold people to high standards while making it safe to be honest about falling short.

​
For product teams specifically

Discovery work depends on psychological safety. If people are afraid to say “I don’t think this is the right problem”, or “this test result is worse than we hoped”, the team loses its ability to learn. The whole premise of continuous discovery - running experiments, being wrong, adjusting - requires an environment where being wrong isn’t dangerous. Lesson learned: the clearest signal of a psychologically safe team I’ve experienced was when a junior designer said in a full team meeting “I don’t think we’ve validated this assumption” - and the room stopped and agreed she was right. That kind of moment doesn’t happen by accident.