Psychological Safety in Agile Teams: What It Is and Isn't

Most agile practices assume that people will speak up. Daily Scrums depend on someone saying "I'm stuck." Retrospectives depend on someone naming what went wrong. Sprint Reviews depend on stakeholders hearing bad news early. When people stay quiet to protect themselves, those practices stay on the calendar but stop working.

That is why psychological safety has become one of the most discussed ideas in agile coaching. It is also one of the most misunderstood. Some people hear it as "be nice," others as "no one can be held accountable," and both readings miss the point.

This guide explains where the concept comes from, what it does not mean, and how a coach or Scrum Master can help a team build it.

Where the Idea Comes From

The concept is most closely associated with Amy Edmondson, a professor at Harvard Business School. Her 1999 paper "Psychological Safety and Learning Behavior in Work Teams," published in Administrative Science Quarterly, introduced team psychological safety as "a shared belief held by members of a team that the team is safe for interpersonal risk taking."

Two parts of that definition matter. It is shared, describing a team's climate rather than one person's confidence. And it is about interpersonal risk: the risk of looking ignorant, incompetent or disruptive in front of colleagues.

Edmondson's study looked at 51 work teams in a manufacturing company. She reported that team psychological safety was associated with learning behavior, and that learning behavior in turn mediated the link between psychological safety and team performance. The paper also proposed that team leader coaching and context support, such as access to resources and information, are antecedents of psychological safety.

Edmondson later expanded the idea for a general audience in her 2019 book The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation and Growth.

Why It Matters for Agile Teams

The paper describes learning behavior as the activities through which a team obtains and processes information so it can adapt and improve. Its examples are seeking feedback, sharing information, asking for help, talking about errors and experimenting.

Read with an agile team in mind, that list is almost a description of inspection and adaptation. Edmondson also explains why these behaviors are hard: asking for help or admitting an error can make a person look incompetent, with real costs if it creates a bad impression on people who influence promotions or assignments. So people often hold back even when speaking up would help.

The Scrum Guide makes a related point. Among the five Scrum values, it says the team and its stakeholders "are open about the work and the challenges," and that team members "have the courage to do the right thing, to work on tough problems." Both are easier when the interpersonal cost of speaking up is low.

What Psychological Safety Is Not

Edmondson has addressed common misreadings directly.

• It is not niceness. In a Psychology Today post, she writes that "Psychological safety is not about being 'nice.'" A safe team can be blunt, because people trust that disagreement will not be held against them.
• It is not the same as a close-knit group. Her 1999 paper notes that psychological safety is not the same as group cohesiveness, because cohesive groups can become less willing to challenge each other, as in groupthink.
• It is not permissiveness. The same paper says the term suggests "neither a careless sense of permissiveness, nor an unrelentingly positive affect" but confidence that the team will not embarrass, reject or punish someone for speaking up.
• It is not lower standards. On her website, Edmondson calls the idea that psychological safety means lowering standards or giving up accountability a common misperception.

To show the relationship with standards, Edmondson uses a two-by-two grid of psychological safety and performance standards. Low safety with low standards is the apathy zone. High safety with low standards is the comfort zone, where people are collegial but not challenged. Low safety with high standards is the anxiety zone, where people are reluctant to offer ideas or ask for help. High safety with high standards is the learning zone, where people collaborate and learn in the service of high performance.

For coaches, the grid is a useful corrective. The goal is not a comfortable team but one that can handle demanding work because problems surface early.

How Coaches Can Help Build It

Edmondson's 1999 paper suggests that when a leader is supportive, coaching-oriented and responds non-defensively to questions and challenges, team members are likely to conclude the environment is safe. When leaders act in authoritarian or punitive ways, people tend to hold back.

1. Frame the work as uncertain. In a Psychology Today post on leading when you are not the boss, Edmondson recommends saying things that frame the challenge ahead, such as noting that the work is uncertain, challenging or interdependent, so it is clear nobody is expected to have every answer.
2. Ask genuine questions. The same post recommends asking colleagues what they are up against and what their concerns are, then listening and responding thoughtfully.
3. Model the behavior first. She also suggests acting as if the environment is already psychologically safe, which means taking a small interpersonal risk yourself so others can follow.
4. Respond well to the first hard truth. How a team reacts the first time someone admits a mistake shapes whether anyone does it again. Thank the person, focus on what the team can learn, and avoid searching for blame.
5. Coach the leaders, not only the team. Because members watch leaders' reactions closely, a private conversation with a manager about how they respond to bad news can matter more than any team exercise.
6. Use structure to lower the cost of speaking. Silent writing before discussion, anonymous input and round-robin turns make it easier for quieter people to contribute. Our guide to facilitation techniques for agile teams covers several of these.

A Hypothetical Example

Imagine a team of six whose Sprint Reviews always look green until a week before a release, when serious problems suddenly appear. In one-on-one conversations, the coach learns that developers knew about the risks earlier but did not want to "make the team look bad" in front of a senior stakeholder.

The coach does not lecture about safety. Instead, they work with the Product Owner to open each review by stating what the team is unsure about, ask the stakeholder privately to thank people who raise risks, and add a retrospective question: "What did we know earlier than we said?" The team would then judge from its own experience whether risks start surfacing sooner.

Measuring It, and Knowing Your Limits

Edmondson's research used surveys answered by team members, and some coaches run short anonymous pulse questions about whether it feels safe to take a risk or ask for help. If you do, treat results as a conversation starter, never a target or a way to rank teams or individuals.

Finally, a boundary: coaches are not therapists. If someone seems to be struggling with stress or their mental health, encourage them to reach out to a qualified professional or an employee assistance program if one exists. Coaching is not a substitute for professional care. In a crisis in the US, call or text 988.

Key takeaways

• Amy Edmondson defined team psychological safety in 1999 as a shared belief that the team is safe for interpersonal risk taking.
• Her research linked psychological safety to learning behaviors such as seeking feedback, asking for help and discussing errors.
• Psychological safety is not niceness, cohesiveness, permissiveness or lower standards; the goal is high safety combined with high standards.
• Coaches help by framing work as uncertain, asking genuine questions, modeling candor, responding well to bad news and coaching leaders.
• Use any measurement as a prompt for conversation, never as a target or a ranking.

Sources

• Amy Edmondson, Psychological Safety and Learning Behavior in Work Teams, Administrative Science Quarterly (1999), full text as a course reading hosted by MIT (PDF)
• Harvard Business School, Amy C. Edmondson faculty profile
• Amy C. Edmondson, Psychological Safety Does Not Equal "Anything Goes"
• Amy C. Edmondson, How to Lead When You're Not the Boss, Psychology Today
• Ken Schwaber and Jeff Sutherland, The 2020 Scrum Guide
• 988 Suicide and Crisis Lifeline