Psychological Safety
The term was coined by researcher Amy Edmondson (Harvard Business School) in 1999 and popularized by Google's Project Aristotle (2016), which analyzed the factors that distinguish the most effective teams at the company. Psychological safety was the first factor identified as a differentiator, ahead of individual experience, intelligence, or team structure.
Why it matters in agile contexts
Agile frameworks—especially the retrospective—implicitly assume that the team can speak honestly about what has gone wrong and how to improve. Without psychological safety, this assumption breaks down: retrospectives become sessions where nobody points out the real problems, impediments go unspoken, and collective learning does not happen.
Psychological safety does not mean the absence of conflict or permanent consensus: it means that conflict and disagreement can be expressed constructively without negative personal consequences.
How its presence and absence manifest
In teams with high psychological safety:
- Mistakes are reported quickly and analyzed as a source of learning, not blame.
- People ask "uncomfortable" questions without fear of appearing incompetent.
- Experimental ideas are put forward even if they might fail.
- Conflicts are addressed directly instead of being escalated or avoided.
In teams with low psychological safety:
- Problems are hidden until they become impossible to ignore.
- Nobody points out the "elephant in the room."
- The retrospective produces superficial feedback with no commitment.
- People act according to what they believe those in power want to hear.
Factors that build it
It cannot be forced, but it can be deliberately cultivated. Some practices that foster it:
- Leadership sets the example: when leaders admit mistakes, show vulnerability, and ask for genuine feedback, they normalize those behaviors within the team.
- Handling mistakes as learning: distinguish between avoidable mistakes (negligence) and experimentation mistakes (calculated risk in unknown territory). The latter deserve analysis, not sanction.
- Transparency about decisions: when teams understand the reasoning behind the decisions that affect them, trust increases. Opacity breeds negative interpretations.
- Explicit space for disagreement: techniques such as Focus-on/Focus-off or the black hat of the six thinking hats create structured spaces where voicing concerns is the norm, not the exception.
Psychological Safety and AI
The introduction of AI tools into teams creates new threats to psychological safety that leaders and Scrum Masters must actively manage:
- Uncertainty about whether AI will replace jobs can create an atmosphere of distrust and concealment. Team members may fear that admitting they don't know how to use an AI tool will make them seem expendable.
- Transparency about the real role of AI in the organization (is it used to empower people, or to monitor and replace them?) is a necessary condition for maintaining trust.
- Teams need a safe space to express their doubts, fears, and mistakes with new AI tools, especially during the initial learning curve.
Common mistake
Confusing psychological safety with niceness or with a lack of high standards. A team with high psychological safety can be very demanding about quality and have very direct debates. What does not happen is that those debates create fear of speaking up in the future. Psychological safety does not protect against the consequences of poor work: it protects against the consequences of speaking honestly about it.
References
Edmondson, Amy C.
- (1999). "Psychological Safety and Learning Behavior in Work Teams". Administrative Science Quarterly, 44(2), pp. 350-383.
- (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.