What psychological safety is and why it matters most.
An interactive explainer that introduces participants to the concept of psychological safety, drawing on Google's Project Aristotle research to establish why it matters for team performance. Covers what psychological safety is, what it looks like in practice, and the specific behaviours that build or erode it.
This module grounds psychological safety in the research that made it widely known. Google's Project Aristotle study, which examined 180 teams over three years, found that psychological safety was the most important factor in team performance, ahead of individual talent, experience, and every other variable measured. The module introduces Amy Edmondson's definition: the belief that you can speak up, take risks, and make mistakes without fear of punishment or embarrassment.
From there, it moves to the practical: what a team with high psychological safety looks and feels like, and what it looks like when it is absent. Participants examine their own team through this lens, identifying the specific dynamics that create safety and those that erode it. The goal is a clear, personal sense of what psychological safety means in their specific context, before moving into the scenario and strategy work that follows.
Participants understand what psychological safety is and why it is the single most important factor in team performance. They can identify the conditions that create it and the everyday behaviours that build or undermine it in their own team.
Open with a short silent reflection to make the topic personal, then introduce what psychological safety is and the research behind it, and have people rate their own team. Keep the focus on personal recognition before any group verdict.
Ask people to think of a moment when they held back from saying something at work because it felt risky. No sharing is required at this stage, which creates immediate personal relevance before anything conceptual is introduced.
Introduce the definition: psychological safety is the belief that you can speak up, take risks, ask questions, and make mistakes without fear of embarrassment, exclusion, or punishment. The term was named and studied by Amy Edmondson at Harvard Business School, and Google's Project Aristotle research brought it to wide attention. Google studied 180 teams over three years, and what they found was that who was on the team mattered far less than how the team worked together. Of the five factors they identified, psychological safety was by far the most important: teams with high psychological safety were better at catching mistakes, more willing to share new ideas, and significantly better at adapting under pressure. A useful analogy is that psychological safety is the condition that makes it safe to pull the fire alarm when something is wrong, and where it is absent, people see the smoke and say nothing. Then walk through what it looks like in practice. In a team with high safety, people ask questions without fear of looking uninformed, challenge ideas without damaging relationships, admit problems early, and give honest feedback. In a team where it is low, meetings are smooth on the surface, bad news travels slowly, and good ideas stay private.
Ask people to rate their own team on a simple scale, placing it honestly where it is right now, then reflect briefly in pairs. Keep this light and private, since the goal at this stage is personal recognition before the scenario and strategy work that follows.
Use Psychological Safety 101 when a group is meeting the idea for the first time and you want a grounded introduction backed by the research. Google's Project Aristotle study gives the room a clear, evidence-based sense of why safety drives team performance.
Using this tool with a skilled facilitator means that discussions are focused, time is used efficiently, and the group moves toward consensus, making the session productive and impactful.
