Quick Answer: Psychological safety means team members believe they can speak up, admit mistakes, ask questions, and challenge ideas without fear of humiliation or punishment.
Harvard professor Amy Edmondson coined the term in 1999 after discovering that the best-performing hospital teams reported more errors, not fewer, because they felt safe enough to talk about them. Google’s Project Aristotle confirmed her findings in 2016, naming psychological safety the single most important factor in team effectiveness across 180 teams.
Teams with high psychological safety show 31% more innovation, 19% higher productivity, and attrition risk below 3% (BCG, 2026). The steps to build it: model fallibility as a leader, invite input with genuine questions, and respond to candor without punishment. This applies equally to people managers, Agile coaches, HR leaders, and Scrum Masters.
Key Highlights About Psychological Safety in the Workplace Google’s Project Aristotle studied 180 teams and found psychological safety was the single most important predictor of team effectiveness, more important than individual talent, team size, or seniority Only 26% of leaders actively create psychological safety for their teams, per McKinsey research cited in 2026 Teams with high psychological safety showed 31% more innovation and 19% higher productivity, according to Boston Consulting Group research across 28,000 professionals in 16 countries Sales teams with high psychological safety exceeded revenue targets by 17%; those with low safety missed targets by 19% (Google Project Aristotle data) Psychological safety ranks among the top 3 workplace priorities for 84% of employees, trailing only pay rises and flexible work (Oyster HR, 2023) The 2026 COE Psychological Safety Study, spanning 47 countries, confirms it as the bedrock of high-performing teams and the next major psychosocial risk leaders must prepare for The Question That Changes Everything About Your Team Before your next team meeting, ask yourself this: if someone on your team noticed a serious problem with your current approach, would they tell you immediately, or would they stay quiet to avoid the awkward conversation?
If your honest answer is ‘they would probably stay quiet,’ you have a psychological safety gap. And that gap is costing your organization more than you realize.
Psychological safety in the workplace is the shared belief that a team is safe for interpersonal risk-taking. It is not about being comfortable. It is not about avoiding conflict. It is specifically about whether your people believe they can speak up, disagree, or admit a mistake without facing humiliation, exclusion, or punishment.
The research is unambiguous. Google studied 180 internal teams over two years in what became known as Project Aristotle , and found that psychological safety was, by far, the most important factor in team effectiveness. Not IQ, not experience, not team size. Whether people felt safe to take interpersonal risks.
This guide gives you the research, the framework, and the specific daily behaviors that build psychological safety, whether you lead a small agile team or a 500-person organization.
What Psychological Safety Actually Means Amy Edmondson, Novartis Professor of Leadership and Management at Harvard Business School, coined psychological safety in a 1999 study of medical teams . She defined it as a shared belief held by members of a team that the team is safe for interpersonal risk-taking.
Her discovery was counterintuitive. She expected the best-performing medical teams to make fewer errors. Instead, they reported more errors. Not because they were less competent, but because they felt safe enough to talk about mistakes openly. The lower-performing teams were hiding problems, and those hidden problems were compounding.
That same dynamic plays out in every workplace every day. A junior developer who spots a critical flaw in the architecture stays quiet because the senior engineer seems certain. A product manager who knows the feature will miss the mark says nothing because the CEO is excited. A Scrum Master who sees the team burning out does not raise it because last time they were told to be more positive.
Psychological safety is not an individual trait. It is a team climate, shaped primarily by leader behavior. And that means it is something you can deliberately build.
What Psychological Safety Is NOT Misconception What It Actually Means Being nice or conflict-free Candid feedback and productive disagreement are signs of high safety, not threats to it Lowering performance standards High safety teams hold each other accountable more effectively because feedback is welcomed Comfort or consensus-building It enables uncomfortable conversations, not the avoidance of them Permission to avoid accountability People in safe teams take more responsibility because they are not protecting themselves from blame A culture of no consequences Mistakes still have consequences; people just are not punished for being honest about them
What the Data Says About Psychological Safety in 2026 If you need to make a business case for investing in psychological safety, the numbers are straightforward.
The Google Project Aristotle Findings In a landmark study from 2012 to 2016, Google’s People Analytics team studied 180 teams to identify what made teams effective. They measured intelligence, personality, experience, and leadership structure. None of those predicted performance as strongly as one factor: how safe team members felt taking risks in front of each other.
The specific results: sales teams with high psychological safety exceeded revenue targets by 17%. Teams with low safety missed their targets by 19%. High-safety teams were rated as effective twice as often by management as low-safety teams. The study concluded that who is on a team matters less than how team members interact with each other.
The 2026 Research Picture BCG surveyed 28,000 professionals across 16 countries and found that psychological safety cuts attrition risk to below 3% and increases retention up to 6x for employees from underrepresented groups, according to research summarized by Metaintro A July 2025 Gartner survey of 313 senior leaders found that organizations adapting change plans based on employee responses are four times more likely to achieve change success, a direct function of psychological safety in the feedback loop The 2026 COE Psychological Safety Study , conducted across 47 countries with clinical insights from workplace wellbeing professionals, confirms that inclusive leadership is the single most important factor in creating psychological safety According to research compiled by workplace health experts, employees who trust their employers are 260% more motivated to work, take 41% fewer sick days, and are 50% less likely to look for other jobs Only 26% of leaders currently create psychological safety for their teams, according to McKinsey, which means the majority of organizations are underinvesting in what drives their biggest performance gap The Four Stages of Psychological Safety Dr. Timothy Clark, CEO of LeaderFactor, developed a four-stage model that builds on Edmondson’s foundational research. The stages represent a progressive journey from basic inclusion to full contribution. Each stage unlocks the next.
Stage 1: Inclusion Safety At this stage, people feel safe simply belonging to the team. They are not afraid of being excluded or marginalized for who they are. Without inclusion safety, no one takes the risk of speaking at all.
What it looks like: employees ask basic questions without worrying they will be judged for not knowing. New team members contribute in their first few weeks. Remote and hybrid employees feel equally included in conversations.
What breaks it: leaders who dominate conversations, interrupt junior team members, or respond dismissively to questions destroy inclusion safety immediately.
Stage 2: Learner Safety At this stage, people feel safe making mistakes, asking for help, and experimenting. This is where innovation begins. Edmondson’s hospital research showed that learner safety is what separates teams that learn fast from teams that hide problems.
What it looks like: retrospectives produce honest failure analysis. People raise blockers early instead of hiding them until sprint review. Postmortems are blameless.
What breaks it: a single instance of public blame or ridicule after a mistake can destroy learner safety for months. As Edmondson notes, every time people withhold their thoughts, the team loses small moments of learning that compound into stalled innovation.
Stage 3: Contributor Safety At this stage, people feel safe contributing their skills and ideas fully. They take ownership without being asked. They offer solutions, not just problems. This is where high performance lives.
What it looks like: team members challenge each other’s assumptions constructively. Engineers push back on product decisions. Scrum Masters raise systemic issues to leadership.
What breaks it: micromanagement, taking ideas without attribution, or dismissing suggestions without explanation all erode contributor safety.
Stage 4: Challenger Safety This is the rarest and most valuable stage. At Stage 4, people feel safe challenging the status quo, including the decisions of senior leaders. This is where transformational innovation comes from.
What it looks like: a team member tells the CEO the strategy is wrong. A developer questions an architecture decision from the CTO. A manager publicly disagrees with a policy in a constructive, solution-focused way.
What breaks it: any punitive response to a well-intentioned challenge immediately resets the team to Stage 1 or 2. The higher the stakes, the more a single negative response spreads through the team.
Amy Edmondson’s 3-Step Leader Framework In her book The Fearless Organization , Edmondson gives leaders a concrete three-step framework. These are not values statements. They are specific behavioral changes.
Step 1: Set the Stage Frame your work honestly. Tell your team what you do not know. Make clear that failure is possible and that you need everyone’s eyes open. This is not vulnerability for its own sake. It is a rational acknowledgment that in complex work, no one person has the complete picture.
Edmondson recommends language like: we are going to need all the ideas you have, I do not have the answers myself, please speak up the moment you see something going wrong. This kind of explicit framing gives people permission to contribute before any individual behavior is even at risk.
Step 2: Invite Participation Ask good questions and mean them. Not rhetorical questions, not leading questions. Real questions that signal you value what the other person thinks.
Specific questions that build safety: what am I missing here, and what would you do differently, and what concerns do you have that we have not talked about. These are not soft questions. They are strategic ones. By asking them consistently, you build a team norm where speaking up is expected, not exceptional.
Google’s research found that teams where leaders ask more genuine questions outperform teams where leaders give more directives. The act of asking creates a small but consistent psychological permission structure that compounds over time.
Step 3: Respond Productively This is the step most leaders underestimate. Your response to candor determines whether you get more of it or less of it. Every time someone speaks up, admits a mistake, or challenges an assumption, they are watching your reaction closely. So is everyone else in the room.
Productive responses: thank you for catching that, that is a fair pushback, tell me more about what you are seeing. Even when you disagree with the content of what someone said, you can acknowledge the act of speaking up.
Edmondson’s central warning to leaders is simple: do not shoot the messenger. Do not get angry when you hear a dissenting view or bad news. According to Harvard Business School’s Working Knowledge , the fastest way to destroy psychological safety is a leader who becomes visibly displeased when someone delivers unwelcome information.
7 Daily Behaviors That Build Psychological Safety at Work Frameworks are useful. Daily behaviors are what actually change culture. Here are seven specific practices you can start this week.
1. Model Fallibility Publicly Share a mistake you made recently in a team setting. Be specific: what you did, what happened, what you learned. When leaders show they are not immune to error, they lower the perceived risk of everyone else admitting mistakes. This does not require over-sharing. A 90-second story once a week is enough to shift the norm.
2. Respond to Bad News Without Defensiveness When someone brings you a problem, your first response is the most important thing you say all week. If you get defensive, blame, or dismiss, you have just taught everyone watching that bad news is dangerous to share. A simple thank you for telling me this early accomplishes more than an hour of culture training.
3. Create Regular Low-Stakes Speaking Opportunities In your next team meeting, create a 5-minute round where everyone answers a non-threatening question: what is one thing you are not sure about this sprint? Low-stakes practice at speaking reduces the anxiety around high-stakes moments. Teams that speak up in small moments speak up in big ones.
4. Blameless Postmortems When something goes wrong, run a postmortem focused entirely on systems, processes, and circumstances, not on individuals. SRE teams at Google use this standard: no names in postmortems, only event sequences. This practice directly builds learner safety by demonstrating that failure analysis is for improvement, not punishment.
5. Attribute Ideas to Their Source When someone’s idea becomes part of your work, say so out loud, for example, this came from what Priya flagged last week. This is not just courtesy. It signals that contributing ideas is rewarded, not absorbed without credit. Idea attribution is one of the fastest-building trust levers available to a manager.
6. Ask, Then Wait When you ask a question in a meeting, do not fill the silence. Silence after a question is not awkwardness. It is the sound of people deciding whether it is safe to speak. Most leaders talk again after three seconds of silence. Wait seven. The answers that come after the silence are almost always better than the ones that come immediately.
7. Set Explicit Team Norms Around Disagreement Write down how your team agrees to disagree. Something as simple as: we separate the idea from the person, we respond to concerns before we dismiss them, we do not use meeting time to say what we think the senior leader wants to hear. Written norms make the implicit expectation explicit, which is particularly important in multicultural or cross-functional teams where assumptions about speaking up differ.
Building Psychological Safety in Agile and Hybrid Teams Agile teams have structural advantages in building psychological safety. Sprint retrospectives are a built-in mechanism for candor. Daily standups create regular low-stakes speaking practice. But these ceremonies only work if the safety exists to make them honest.
The most common failure mode: retrospectives where everyone says things are fine because the Scrum Master is also the line manager. The ceremony runs perfectly; the safety is zero.
For Scrum Masters and Agile Coaches Your role is uniquely positioned to model psychological safety. You facilitate spaces that are supposed to be safe. If you are also evaluating team members’ performance, that dual role creates a safety conflict that needs to be named and managed explicitly.
Run anonymous retrospective inputs before discussion. Tools like EasyRetro or TeamRetro let teams submit feedback privately before the group session Invite challenges to your own facilitation: is there a better way I could have run that last ceremony? Track psychological safety explicitly using Edmondson’s four-question survey at the team level each quarter: are mistakes held against you, can you bring up problems, is it safe to take risks, are you rejected for being different NextAgile’s Psychological Safety Workshop teaches Scrum Masters and Agile coaches exactly how to assess and build safety within their teams. It is one of our most-requested leadership programs for organizations running agile at scale.
For Remote and Hybrid Teams Remote work changes the safety calculus. Non-verbal signals, the primary safety cue in in-person settings, are invisible or compressed on video. Silence on a call is even more ambiguous than silence in a room.
Use asynchronous input channels before synchronous discussion. Shared Notion docs, Miro boards, or pre-meeting forms let quieter team members contribute before the dynamic of the live call takes over Rotate speaking order deliberately in video calls. Starting with the most junior voice instead of the most senior shifts who sets the conversational tone Separate reflection from decision in hybrid meetings. Give remote participants 24 hours to contribute async before decisions are finalized How to Measure Psychological Safety in Your Team You cannot improve what you cannot measure. Amy Edmondson developed a validated survey instrument with seven questions that leaders can use to assess their team’s safety level.
Edmondson’s 7-Item Psychological Safety Scale Question Scoring If you make a mistake on this team, it is often held against you Reverse scored – higher agreement = lower safety Members of this team are able to bring up problems and tough issues Higher agreement = higher safety People on this team sometimes reject others for being different Reverse scored It is safe to take a risk on this team Higher agreement = higher safety It is difficult to ask other members of this team for help Reverse scored No one on this team would deliberately act in a way that undermines my efforts Higher agreement = higher safety Working with members of this team, my unique skills and talents are valued and utilized Higher agreement = higher safety
Run this quarterly, by team, not by organization. Organization-level averages hide the team-level gaps where safety actually lives or dies. A score difference of 0.5 on a 5-point scale between two adjacent teams in the same department is significant.
For agile teams, also track speak-up frequency in retrospectives, number of impediments raised early versus at sprint review, and whether postmortems produce systemic insights or individual blame. Our guide to agile metrics and KPIs covers how to build these indicators into your team’s regular reporting cadence.
6 Mistakes Leaders Make When Trying to Build Psychological Safety Running a safety survey with no follow-up. Asking people how safe they feel and then not acting on the results is more damaging than not asking. It confirms that leadership is not listening. Confusing psychological safety with low standards. Safety without accountability produces complacency, not performance. High-safety teams have high standards. They just meet those standards through candor and learning, not fear. Treating safety as an HR program rather than a leadership behavior. You cannot build psychological safety through a workshop alone. It is built in the reaction of a manager when an employee brings bad news at 4pm on a Friday. Fixing blame quietly. A leader who blames a team member privately rather than publicly still creates a fear environment. Word gets around. The story of what happened to a colleague who told the truth travels faster than any memo about culture. Creating safety only at the top of the hierarchy. Psychological safety must exist in the team, not just in leadership. A senior leader who is accessible and transparent cannot compensate for a middle manager who punishes dissent. Skipping the hard work of responding to challenge. Inviting challenge is the easy part. Responding to it when it is uncomfortable, expensive, or inconvenient is where most leaders fall short. Our conflict management guide covers exactly how to navigate this moment without retreating into defensiveness. Psychological Safety and Agile Transformation: Why the Connection Matters The most common reason agile transformations stall is not that teams do not understand Scrum or SAFe. It is that they do not feel safe enough to use the framework honestly. Ceremonies run, but retrospectives produce surface feedback. Sprint reviews show polished demos, not real progress. Backlog items hide scope problems.
This is what NextAgile calls ceremony theater: going through the motions of agile while the underlying safety conditions for honest agile practice are absent.
The fix is not more framework training. It is explicit safety work alongside the framework adoption. At NextAgile, we integrate psychological safety assessment into every agile transformation engagement. Our Agile Culture and Mindset guide shows teams what honest agile practice looks like, and our leadership coaching teaches managers the specific daily behaviors that make honesty feel safe.
For leaders managing the change resistance that comes with any transformation, psychological safety is the foundation of your change management strategy. A team that cannot speak up cannot tell you what is not working. Our guide to AI change management tools covers how to detect and address that resistance with data.
Build safety first. The framework scales on top of it.
How Real Organizations Built Psychological Safety Google: The Origin of the Research Google’s Project Aristotle is the canonical example. After studying 180 teams over two years, Google found that the five factors making teams effective, in order, were psychological safety, dependability, structure and clarity, meaning, and impact. Psychological safety ranked first and enabled all the others.
Google’s practical response: they trained managers in active listening, removed competitive internal ranking systems that incentivized information hoarding, and began explicitly rewarding managers whose teams showed high safety scores. They also stopped optimizing for individual brilliance and started optimizing for team candor.
A Hospital That Got It Right Edmondson’s original research showed that the best-performing hospital units in her study reported significantly more errors than lower-performing units. Upon investigation, the pattern was clear: the better units had senior nurses and doctors who actively modeled admitting mistakes, asked questions publicly, and responded to bad news without punishment. The result was not more errors occurring. It was more errors being caught and corrected before they harmed patients.
What Happens Without It: The Wells Fargo and NASA Cases Edmondson cites two well-known safety failures driven by the absence of psychological safety, documented in a comprehensive science-backed guide for business leaders . Wells Fargo employees who knew about fraudulent account practices stayed silent because speaking up had historically led to termination. The cost of that silence was billions in fines and lasting reputational damage. NASA’s Challenger and Columbia disasters both involved engineers who had serious concerns and stayed quiet because the culture made dissent professionally dangerous. The cost was catastrophic.
Where to Start Building Psychological Safety This Week You do not need a six-month culture program. You need three specific behavior changes that are visible to your team this week.
In your next team meeting: share one thing you got wrong recently and what you learned from it. Keep it genuine and specific. Watch how the room changes. After this week’s standup: ask one team member privately, is there anything you have been hesitant to raise with the team? Then listen without defensiveness for the entire response. In your next retrospective: run the first input round anonymously. Read the results aloud and respond to the most uncomfortable feedback first. That response is the safety signal everyone is watching for. Psychological safety is not built in a single conversation. It is built in a thousand small moments where people watch how their leader responds to honesty. Each of those moments is a deposit or a withdrawal from the trust account that makes your team’s performance possible.
NextAgile’s Psychological Safety Workshop gives leadership teams a structured, evidence-based pathway to build and sustain safety across teams. It draws on Edmondson’s research, Timothy Clark’s four-stage model, and NextAgile’s 16 years of experience in enterprise transformation. You can also explore our leadership coaching services or reach our team directly through the contact page to discuss a customized safety program for your organization.
Frequently Asked Questions 1. What is psychological safety in the workplace? Psychological safety is the shared belief among team members that they can speak up, ask questions, admit mistakes, or challenge ideas without fear of humiliation or punishment. It was defined by Harvard professor Amy Edmondson in 1999 and confirmed as the most important factor in team effectiveness by Google’s Project Aristotle (2012-2016). It is a team climate, shaped primarily by leader behavior, not an individual personality trait.
2. How do you build psychological safety in a team? Leaders build psychological safety through three core behaviors identified by Amy Edmondson: setting the stage by framing work honestly and acknowledging uncertainty, inviting participation through genuine questions that signal you value input, and responding productively to candor without defensiveness or punishment. Daily practices like blameless postmortems, idea attribution, and deliberate silence after questions compound these behaviors into a team norm.
3. Why does psychological safety matter for agile teams specifically? Agile teams depend on honest retrospectives, early impediment raising, and genuine sprint reviews to improve. Without psychological safety, these ceremonies become theater. Team members perform compliance rather than genuine inspection and adaptation. Google’s Project Aristotle data showed that teams with high psychological safety had lower turnover, more diverse ideas, higher revenue, and were rated as effective twice as often as low-safety teams.
4. What are the four stages of psychological safety? Dr. Timothy Clark identified four progressive stages: Inclusion Safety, feeling safe to belong, Learner Safety, feeling safe to make mistakes and ask questions, Contributor Safety, feeling safe to offer ideas and take ownership, and Challenger Safety, feeling safe to question the status quo, including decisions from senior leaders. Each stage unlocks the next. Most organizations reach Stage 2 or 3 but fall short of consistent Stage 4 safety.
5. How do you measure psychological safety? Amy Edmondson developed a validated 7-item survey measuring team-level psychological safety. Questions include whether mistakes are held against you, whether problems can be raised openly, and whether it is safe to take risks. Run this quarterly at the team level, not organization-wide. Aggregate scores hide team-level gaps. Also track behavioral indicators: frequency of early impediment raising, quality of retrospective honesty, and whether postmortems assign blame or identify system causes.
6. Can psychological safety coexist with high performance standards? Yes, and it must. Psychological safety without high standards produces complacency. High standards without psychological safety produce fear, which drives mistakes underground rather than surfacing them for correction. The most effective teams operate in what Edmondson calls the Learning Zone, where both standards and safety are high. Leaders achieve this by being clear about expectations while responding to mistakes with curiosity rather than blame.
7. What is the difference between psychological safety and trust? Trust is primarily a belief one individual holds about another, such as I trust you to do what you said. Psychological safety is a group-level belief about the team environment, such as in this team it is safe to take interpersonal risks. They reinforce each other but are not the same thing. You can have high interpersonal trust between two people while both feel unsafe to challenge their manager. Psychological safety operates at the team climate level and is shaped by observable leader behavior.
Anuj Ojha is Co-Founder & Consulting Head at NextAgile. Anuj has designed & led multiple turnkey transformation journeys across industries, domains & geographies and has 16+ years of experience as an agile practitioner. He has worked with CXOs, CTOs & Key Leaders to translate their business objectives on the ground, contextualizing org transformations and creating buy-in across level, leading a team of coaches/consultants to implement agility across 150+ teams & trained more than 12k team members. Anuj’s core area of interest is business agility & working with leaders & teams to achieve long term sustainable, Agile culture & mindset.
Skip to content 
