All Resources

Frameworks & Tools · 7 min read

Psychological Safety: the operating system of high-performing teams

Amy Edmondson's 25-year body of research shows psychological safety is the single strongest predictor of team learning, innovation, and performance — confirmed by Google's Project Aristotle.

What it is

Psychological safety is the shared belief that the team is safe for interpersonal risk-taking — that you can speak up with ideas, questions, concerns, or mistakes without being punished or humiliated. It is not about being 'nice,' lowering standards, or avoiding conflict. High-safety teams hold the highest standards because they can talk about what's actually happening.

Edmondson's research at Harvard Business School, replicated across hospitals, manufacturing floors, knowledge teams, and Google's internal Project Aristotle study of 180+ teams, identifies it as the strongest predictor of team performance — above individual talent, tenure, or seniority mix.

Why it matters more in an AI era

When AI accelerates execution, the bottleneck becomes the quality of human judgment — and judgment improves only when people can name what they actually see. Teams without safety hide errors, suppress dissent, and present a sanitized version of reality upward. That blind spot is fatal at the speed AI now enables.

Three takeaways

  1. 01

    Safety is a behavioral climate, not a personality trait — leaders create it or destroy it.

  2. 02

    High-performing teams have both high safety AND high accountability. One without the other breeds either fear or complacency.

  3. 03

    It is built in micro-moments: how a leader responds to the first mistake, the first dissent, the first 'I don't know' on the team.

Three things to implement this week

  • Frame the work as a learning problem, not an execution problem — explicitly acknowledge uncertainty before each major initiative.
  • Model fallibility: as a leader, say 'I was wrong about that' or 'I don't know — help me think' at least once per week, publicly.
  • Reward the messenger. When someone surfaces a problem early, thank them by name in front of the team — even if the news is bad.