In 2012, Google launched one of the most ambitious internal research projects in corporate history. Codenamed Project Aristotle, it set out to answer a deceptively simple question: what makes a team effective?
The research team studied 180 teams over two years, gathering data on team composition, performance metrics, and dozens of organizational variables. They expected to find that the best teams were composed of the most talented individuals, or that the best managers had certain leadership styles, or that the right mix of personality types explained success.
What they found surprised them. None of those factors predicted performance reliably. The single most powerful predictor was something more subtle: psychological safety.
What Is Psychological Safety?
Psychological safety is a team climate in which members believe they will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. It is the shared belief that the team is safe for interpersonal risk-taking.
The concept was first measured and named by Harvard Business School professor Amy Edmondson in the late 1990s. Edmondson was studying medication error rates in hospital nursing teams and expected to find that higher-performing teams made fewer errors. Instead, she found that higher-performing teams actually reported more errors — not because they were performing worse, but because they felt safe enough to acknowledge and discuss the errors they made.
This counterintuitive finding set the direction for decades of subsequent research. Psychological safety does not make teams complacent. It makes teams honest.
"Psychological safety is not about being nice. It's about giving candid feedback, openly admitting mistakes, and learning from each other." — Amy Edmondson
The Research Foundation: Edmondson and Project Aristotle
Amy Edmondson's Original Studies
Edmondson's research established that psychological safety is both measurable and predictive. Her original seven-item survey scale asks team members to rate agreement with statements including:
- "If you make a mistake on this team, it is often held against you"
- "Members of this team are able to bring up problems and tough issues"
- "It is safe to take a risk on this team"
- "It is easy to speak up on this team about what is on your mind"
Teams scoring higher on this scale consistently showed better learning behavior, lower error cover-up rates, and over time, stronger performance outcomes.
In a landmark study of surgical teams adopting a new cardiac procedure, Edmondson found that teams led by surgeons who explicitly framed the learning process as novel and uncertain — normalizing questions and admitting they did not have all the answers — learned the procedure significantly faster than teams whose surgeons projected unquestioned authority.
Google Project Aristotle Findings
Google's research team confirmed Edmondson's findings at scale. Of the five factors they identified as differentiating high-performing teams — psychological safety, dependability, structure and clarity, meaning, and impact — psychological safety was foundational. Without it, the other four factors were difficult to achieve.
In teams with high psychological safety, members:
- Shared information more readily
- Raised concerns earlier, when they were easier to address
- Offered more diverse ideas and approaches
- Acknowledged uncertainty rather than projecting false confidence
- Learned from failure rather than concealing it
Why Psychological Safety Is Not the Same as Comfort
A common misunderstanding is that psychological safety means teams avoid conflict, never challenge each other, or always agree. This is the opposite of what the research describes.
High psychological safety teams are often more challenging environments intellectually — precisely because people feel safe to disagree, raise concerns, and push back on poor ideas. The safety is not safety from hard conversations; it is safety from social punishment for engaging in them.
Low psychological safety does not mean teams argue less. It means they argue less about substantive issues that matter, while social tensions fester below the surface. Critical information about problems gets filtered out as it moves up hierarchies. Teams pursue the most visible, safest option rather than the most creative one.
The distinction matters practically. Managers who try to build psychological safety by suppressing conflict or avoiding difficult feedback are doing the opposite of what the research recommends.
What Destroys Psychological Safety
Understanding what damages psychological safety is as important as knowing what builds it.
Public Humiliation of Mistakes
When a leader responds to a mistake — especially in front of the team — with anger, sarcasm, or blame, the message is clear: this is a team where mistakes are punished. A single visible incident of this type can suppress candid communication for months.
Research by Edmondson and others suggests that the effects are not limited to the person directly humiliated. Observers update their beliefs about safety based on watching how others are treated. The person who sees their colleague embarrassed for raising a concern becomes substantially less likely to raise their own.
Dismissing Ideas Without Engagement
When contributions are consistently ignored or brushed aside without acknowledgment, contributors learn to stop contributing. This is particularly damaging for minority viewpoints and for lower-status team members who already face higher perceived interpersonal risk.
Rewarding Confident Silence
Organizations that consistently promote people who project certainty — and sideline those who acknowledge complexity or ask questions — train employees that admitting uncertainty is career-limiting. The result is systematically overconfident communication that reduces decision quality.
Status Differentials and Interruption Patterns
Research on meeting dynamics consistently finds that higher-status individuals talk more, interrupt more, and have their ideas more readily accepted — regardless of idea quality. In environments where these patterns go unchallenged, lower-status members gradually disengage from substantive contribution.
How to Build Psychological Safety as a Manager
Model Fallibility
The most powerful thing a leader can do is demonstrate that it is acceptable to be wrong, to not know, and to ask for help. This means explicitly acknowledging your own mistakes, saying "I don't know" when you don't, and publicly asking for input and challenge.
Edmondson calls this leader inclusiveness — inviting participation, acknowledging the limits of your own knowledge, and demonstrating that other perspectives have genuine value.
Frame Work as Learning
When teams are working on novel or complex problems, frame the situation as a learning process rather than a performance evaluation. Language matters: "we're going to figure this out together" signals a different climate than "we need to get this right."
This framing has practical consequences. Edmondson's surgical team research found that this language shift — coming specifically from the lead surgeon — was one of the strongest predictors of how quickly teams learned new techniques.
Respond Productively to Bad News
The most critical moments for psychological safety are when someone brings a problem. If a manager reacts with frustration, blame, or minimizing ("why didn't you tell me sooner?" delivered with irritation), they are training people not to bring problems. If they react with curiosity and problem-solving orientation, they reinforce that surfacing problems is safe and valued.
A useful default response to concerning news: "Thanks for telling me. Let's figure out what we can do about it."
Create Structure for Inclusion
Not everyone speaks up equally in unstructured settings. Status, personality, and conversational dynamics create patterns that systematically exclude voices. Meeting practices like round-robins, anonymous idea generation, and explicitly inviting quieter members reduce these structural barriers.
Address Interpersonal Risk Explicitly
Some leaders find it valuable to make the psychological safety norm explicit — naming in team discussions that this is a team where challenge is expected and welcomed, and demonstrating through behavior what that means in practice.
Measuring Psychological Safety in Your Team
Edmondson's original scale remains the most validated measurement tool. A simplified version asks team members to anonymously rate agreement with five to seven statements on a 5-point scale. Team scores are calculated as averages, and variations across team members reveal patterns worth investigating.
Common pulse survey questions include:
| Statement | Low score signal |
|---|---|
| "I feel comfortable raising concerns in team meetings" | Meetings may not feel like safe spaces |
| "My team acknowledges and learns from mistakes" | Error culture may be punitive |
| "I can offer opinions that differ from my manager's" | Hierarchy may be suppressing dissent |
| "Team members do not undermine each other's efforts" | Trust or interpersonal dynamics may be damaged |
Scores should be tracked over time, not treated as one-time diagnostics. Patterns matter more than any single data point.
Psychological Safety, Innovation, and Organizational Performance
The connection between psychological safety and innovation is both intuitive and research-supported. Innovation requires risk-taking — proposing ideas that might fail, sharing work that is incomplete, challenging assumptions that may be correct. In environments where such risks are punished, innovation attempts decline.
A consistent finding across industries is that psychological safety predicts learning behavior — the degree to which teams seek feedback, experiment with new approaches, discuss failures, and ask for help. And learning behavior, in turn, predicts performance in complex, changing environments.
This dynamic is captured in what researchers call the performance-safety paradox: in the short run, psychologically safe teams may appear less polished because they surface more problems and publicly acknowledge more uncertainty. Over time, they solve those problems faster and develop more robust practices.
Psychological Safety in Remote and Hybrid Teams
Remote work created new challenges for psychological safety. Non-verbal cues that signal attention and receptivity are reduced or absent. Asynchronous communication collapses the social context in which tone is understood. And the casual conversations that build interpersonal trust — what researchers call the "psychological water cooler" — disappear.
Research on distributed teams suggests that psychological safety in remote settings requires more deliberate effort:
- Shorter feedback loops — the time between raising a concern and getting a response should be short; long silences are interpreted as disapproval
- Explicit norms for video calls — acknowledging latency and speaking order reduces the status dynamics that suppress quieter voices
- Async inclusion — creating written channels where ideas can be submitted and acknowledged independent of who speaks up in meetings
- More frequent check-ins — brief one-on-one conversations that would happen naturally in office settings need to be scheduled in remote ones
Conclusion
Psychological safety is not a soft concept. It is one of the most robustly measured predictors of team learning and performance in the research literature. It determines whether teams actually use the collective intelligence their members possess, or whether that intelligence stays silent out of social caution.
The work of building it falls primarily on leaders — through how they respond to bad news, how they invite dissent, and how consistently they model the fallibility and openness they want to see. It is built in small moments far more than in grand policy statements. And it is damaged far faster than it is built.
Understanding that reality is the beginning of building teams that work.
Frequently Asked Questions
What is psychological safety?
Psychological safety is a team climate in which people believe they will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. The concept was developed by Harvard Business School professor Amy Edmondson, who first measured it in hospital nursing teams in the 1990s and found it predicted quality of care.
What did Google's Project Aristotle find about psychological safety?
Google's internal research project, codenamed Aristotle, studied 180 teams over two years to identify what makes teams effective. The single most important factor was psychological safety — more important than individual talent, team composition, or any other variable. Teams where members felt safe to take interpersonal risks consistently outperformed those where they did not.
How does psychological safety differ from trust?
Trust is typically about one person's expectations of another individual, while psychological safety is a group-level phenomenon about shared beliefs regarding team norms. You can trust a colleague personally while still feeling unsafe speaking up in a team meeting. Psychological safety is about what happens when you take a risk in front of the group, not in private.
What behaviors destroy psychological safety?
The most damaging behaviors are public humiliation of mistakes, dismissing ideas without engagement, punishing people who raise problems, and rewarding confident silence over cautious honesty. Leaders who react to bad news with anger or blame, even once, can suppress candid communication for months. Status hierarchies and interruption patterns also systematically undermine safety.
Can psychological safety be measured?
Yes. Edmondson's original seven-item scale remains widely used and asks team members to rate agreement with statements such as 'It is safe to take a risk on this team' and 'No one on this team would deliberately act in a way that undermines my efforts.' Organizations including Google use pulse surveys to track psychological safety scores alongside performance metrics.