Psychological Safety: The Foundation of a High-Performing Scrum Team
In 2012, Google set out to answer a deceptively simple question: what makes a team effective? Over two years, researchers studied 180 teams across the organisation, measuring everything from individual IQ and personality traits to communication patterns and team composition. The project, known as Project Aristotle, produced a result that surprised many of the researchers: the single strongest predictor of team effectiveness was not who was on the team. It was how the team interacted — specifically, whether the team had psychological safety.
Psychological safety, as defined by Harvard Business School professor Amy Edmondson, is the belief that the team is safe for interpersonal risk-taking. It is the shared understanding — reinforced by experience — that you can raise a concern, admit you do not know something, ask a question that might seem obvious, or propose a half-formed idea without being humiliated, punished, or dismissed. It is the difference between a meeting where people say what they think and one where people say what they think is safe to say.
Why It Matters for Scrum
Scrum is built on a set of ceremonies whose value depends entirely on people being honest. The Sprint Retrospective is the most obvious example. A retrospective is designed to surface what went wrong, what could have been done better, and what the team wants to try differently in the next Sprint. If team members do not feel safe raising real problems — if they fear that identifying a process issue will be interpreted as a personal attack, or that admitting a mistake will affect their performance review — the retrospective becomes a performance of team improvement rather than the real thing.
The Daily Scrum has the same dependency. The three questions — what did I do yesterday, what will I do today, what is blocking me — only produce value if the team is genuinely surfacing blockers. In a team with low psychological safety, blockers are often absorbed, worked around, or minimised rather than openly stated. The Daily Scrum becomes a status report rather than a coordination tool, and the Scrum Master is left with a distorted picture of what is actually slowing the team down.
Sprint Reviews, backlog refinement sessions, and even the way the team discusses estimates are all affected. When people are afraid to look incompetent or uncertain, they stop asking questions, stop challenging assumptions, and stop raising risks. The collective intelligence of the team — which is the point of agile team design — is quietly suppressed.
How to Build It
The Scrum Master is not the only person responsible for psychological safety, but they are the most positively positioned to shape it. The single most effective thing a Scrum Master can do is model vulnerability: admit their own uncertainty, acknowledge when they do not know the answer, share mistakes without defensiveness. This is not performative humility — it is a genuine signal to the team that uncertainty is normal and honest conversation is expected.
Reinforcing courage when someone speaks up is equally important. When a team member raises a difficult issue, disagrees with an assumption, or admits a mistake, the Scrum Master's response sets a precedent. Responding with curiosity — asking follow-up questions, treating the input as valuable, exploring what the concern reveals — sends a clear signal. Responding with defensiveness, dismissal, or implied criticism sends the opposite signal, and it will be remembered long after the specific incident is forgotten.
Responding to failure with curiosity rather than blame is perhaps the most sustained test of a team's psychological safety culture. Failures happen in every Sprint. The way they are processed — whether the instinct is to find out what happened and how to prevent it, or to establish who was responsible — shapes how safe it feels to be honest about the next failure.
Structural interventions also help. Retrospective formats that allow anonymous input, turn-taking that ensures quieter voices are heard, and explicit team agreements about how feedback is given and received can all create conditions where psychological safety grows.
How to Measure It
Amy Edmondson's original seven-item survey is widely used and validated: it asks team members to rate statements like "If I make a mistake on this team, it is not held against me" and "It is safe to take a risk on this team" on a Likert scale. Running this survey periodically — and, importantly, discussing the results openly with the team — provides a concrete, trackable signal.
Qualitative signals are equally revealing. How many people speak in a retrospective? Does the same person dominate? Are blockers raised in the Daily Scrum or only discovered after the fact? Do team members disagree with each other in meetings, or only in private conversations? These patterns are observable and meaningful even without a formal survey instrument.
The Scrum Master who takes psychological safety seriously — who tracks both the formal and informal signals and adjusts their facilitation accordingly — is building the foundation that every other Scrum practice depends on.
XNM Consulting supports organisations in building high-performing agile teams. For coaching, training, or hands-on Scrum implementation support, visit our Program and Project Delivery page.