Psychological safety is the shared belief, held by the members of a team, that the team is safe for interpersonal risk-taking — that you can ask a question, admit a mistake, raise a concern or disagree with the boss without fear of being embarrassed, punished or judged incompetent. Defined by Harvard’s Amy Edmondson, it is the single biggest predictor of high-performing teams — because it decides whether people’s best thinking actually gets said out loud.
The definition, and where it comes from
The term was defined by Harvard Business School professor Amy Edmondson, whose research on hospital teams turned up a surprise: the better teams appeared to make more mistakes. What was actually happening was that the better teams felt safe enough to report their mistakes, while the weaker ones buried them. The difference wasn’t error rate — it was candor.
That is the whole idea in one line: psychological safety is whether people believe it’s safe to be honest here. Not honest in the abstract — honest when it costs something: when the honest thing is “I don’t understand,” “I think we’re wrong,” or “that was my mistake.”
Why it matters more than almost anything else
In 2012 Google set out to find what made some of its teams excel and others stall. The project — Project Aristotle — studied 180 teams expecting the answer to be the right mix of talent. It wasn’t. The single biggest differentiator of the highest-performing teams was psychological safety. The who mattered far less than whether the team was safe to speak up.
The logic is simple once you see it. Every capability your team already has — the sharp objection, the early warning, the half-formed idea, the admission that unblocks everyone — is worth nothing if it stays in someone’s head. Fear is a tax on intelligence. Psychological safety is what lets a team actually spend the talent it’s paying for.
What psychological safety is not
This is the part most people get wrong, so it’s worth being blunt: psychological safety is not niceness, comfort, lowered standards or the absence of conflict.
- It is not being nice. Safe teams argue more openly, not less — because the disagreement is about the work, and no one’s standing is on the line.
- It is not lowering the bar. Safety pairs with high standards, not instead of them. Drop the standards and you don’t get safety — you get complacency.
- It is not comfort. The point isn’t to make people comfortable; it’s to make it safe to be uncomfortable together — to say the hard thing.
Edmondson maps this as two axes. Pair high standards with high psychological safety and you get the learning & high-performance zone. High standards but low safety produces anxiety. High safety but low standards produces a comfortable, complacent team. Low-low is apathy. You want both dials turned up.
The four stages of psychological safety
Organizational theorist Timothy R. Clark describes safety as something a team builds in four stages, roughly in order. Each answers a different question running quietly in people’s heads.
| Stage | What it means | The question in people’s heads |
|---|---|---|
| 1. Inclusion safety | You’re accepted as a member of the group | “Do I belong here?” |
| 2. Learner safety | It’s safe to ask questions, experiment and make mistakes | “Is it safe to learn?” |
| 3. Contributor safety | It’s safe to use your skills and add real value | “Is it safe to contribute?” |
| 4. Challenger safety | It’s safe to question the status quo and push for change | “Is it safe to challenge?” |
Most teams get stuck between stages 2 and 4. People will quietly do their jobs (contributor safety) long before they’ll tell a senior leader the plan is flawed (challenger safety) — and challenger safety is exactly the one that prevents the expensive, avoidable failures.
How to build psychological safety
Here is the uncomfortable truth for leaders: your team’s psychological safety is mostly a reflection of your own behavior, repeated. It’s built in small, observable moments — how you react the first time someone disagrees — not in a single offsite. Five moves do most of the work:
- Frame the work as a learning problem. Say out loud that the work is uncertain and interdependent, so everyone’s voice matters. When the goal is “figure it out together” rather than “execute flawlessly,” speaking up feels necessary instead of risky.
- Model fallibility first. Admit your own mistakes, gaps and uncertainty before you ask anyone else to. “I got that wrong” and “I don’t know” from the person in charge give everyone else permission to be human.
- Ask genuine questions and invite dissent. Ask questions you don’t know the answer to, and explicitly invite disagreement — “What am I missing?” “Who sees it differently?” — then wait through the silence. Inquiry signals that other views are wanted, not just tolerated.
- Respond to failure and bad news with curiosity. Your reaction the first time someone brings a mistake or a challenge sets the tone for months. Meet it with curiosity and thanks for the candor. Punish the messenger once and the messages stop — you’ll just stop hearing about problems, not stop having them.
- Hold high standards and safety. Make it clear safety isn’t a softer bar. Pair a demanding standard with genuine support, so the team lands in the high-performance zone rather than in comfort or fear.
How to measure it
The best-known instrument is Edmondson’s seven-item survey — people rate statements like “If you make a mistake on this team, it is often held against you” and “It is safe to take a risk on this team.” It’s a useful baseline. But self-report has the same weakness here as everywhere: it captures what people say the climate is, not what happens when the pressure is real.
A behavioral read is stronger. Put a team into a live, high-stakes situation and watch: who speaks up and who goes quiet, whether junior people challenge senior ones, how the group receives bad news in the moment. That behavior — not a survey score — is the truth about a team’s safety.
Where team building comes in
You can’t lecture a team into psychological safety, and a one-day workshop rarely moves it. What moves it is a shared experience where people take a small interpersonal risk together and find out it was safe — then carry that back to work. That’s the mechanism behind a well-run give-back team building event: people problem-solve, stumble, ask for help and succeed together, outside the usual hierarchy.
For leadership teams specifically, the fastest way to see a team’s real safety is to pressure-test it. Team LFS drops a leadership team into a live, AI-driven crisis simulation and captures exactly the behaviors that reveal psychological safety — who challenges, who defers, how the group handles a curveball — then turns it into a team debrief you can coach against. It pairs naturally with an executive team building program or ongoing team coaching to build the safety the simulation exposes. If your team keeps having the same breakdown, our guide on why team building fails is a useful companion read.
Frequently asked questions
What is psychological safety? +
The shared belief, held by members of a team, that the team is safe for interpersonal risk-taking — you can ask a question, admit a mistake, raise a concern or disagree with the boss without fear of embarrassment or punishment. The term was defined by Harvard’s Amy Edmondson.
Why is psychological safety important? +
Because it decides whether a team’s talent actually shows up. Google’s Project Aristotle studied 180 teams and found psychological safety was the single biggest differentiator of its highest performers — above individual skill. Without it, people stay quiet and the best ideas never surface.
Is psychological safety the same as being nice? +
No. It isn’t about lowering standards, avoiding conflict or keeping everyone comfortable. It pairs with high standards. A safe team argues more openly, not less — it just argues about the work, without people fearing for their standing.
What are the four stages of psychological safety? +
Timothy Clark’s model: inclusion safety (I’m accepted), learner safety (safe to ask and make mistakes), contributor safety (safe to add value), and challenger safety (safe to question the status quo). Teams tend to build them in that order, and get stuck before challenger safety.
How do you build psychological safety? +
Mostly through leader behavior, repeated: frame the work as a learning problem, admit your own mistakes first, ask genuine questions and invite dissent, respond to failure with curiosity instead of blame, and hold high standards and safety at the same time. It’s built in small moments, not one workshop.
How do you measure psychological safety? +
The common tool is Edmondson’s seven-item survey. A behavioral read is stronger: watch a team under real pressure and see who speaks up, who goes quiet and how bad news lands — which is exactly what a live team simulation like Team LFS captures.
James Carter
Founder, Be Legendary (Building Teams) · Denver, CO
25 years helping hundreds of executive and leadership teams do what they didn’t think was possible. Author of Lost Disciplines of Leadership and co-author alongside Stephen Covey, Ken Blanchard, Deepak Chopra and Brian Tracy.
See how safe your leadership team really is — under pressure.
Team LFS is a live, AI-driven crisis simulation built from your organization. It reveals who speaks up, who goes quiet, and how your team handles the hard moment — then turns it into a plan.