What is psychological safety at work?

Psychological safety at work is the shared belief within a team that it is safe to take interpersonal risks — to speak up, ask questions, admit mistakes, and challenge the way things are done — without fear of punishment, embarrassment, or rejection.

The concept of psychological safety at work was developed by Harvard Business School professor Amy Edmondson, who first observed it while researching medical teams in the 1990s. She noticed something counterintuitive: the best-performing teams were actually reporting more errors, not fewer. The reason was not that they made more mistakes — it was that they felt safe enough to talk about them. Psychological safety was not the absence of failure. It was the presence of honesty.

Google's internal Project Aristotle found that psychological safety at work was the number one predictor of team performance, above talent, resources, or any other single factor.

This article covers what psychological safety is, Edmondson's four stages, six ways to build it as a manager, and what it is not.

Why psychological safety at work matters for managers

Psychological safety at work does not maintain itself. Most managers know that teams perform better when people speak up. What is less obvious is how fragile that dynamic is — and how much of it depends on manager behaviour.

A single moment of ridicule, dismissal, or visible frustration when someone raises a concern can silence an entire team for months. People do not calculate risk consciously. They observe, learn, and adapt. When the evidence suggests that speaking up leads to negative consequences — even subtle ones — they stop.

The cost is not just a quieter team. It is:

• Hidden problems that surface too late. Issues go unraised until they become crises.
• Surface agreement over honest pushback. You get yes-people, not collaborators.
• Missed learning. Mistakes get concealed rather than turned into improvements.
• Reduced innovation. New ideas require the willingness to look foolish. Without psychological safety, people default to safe and familiar.
• Talent attrition. High performers who have options leave environments where they cannot contribute meaningfully.

Edmondson's four stages of psychological safety at work

Building on her original research, Edmondson and Timothy Clark identified four stages of psychological safety at work of psychological safety that teams move through sequentially.

Stage 1: Inclusion safety

People feel accepted as members of the team. They can be themselves without fear of rejection. This is the baseline — without it, no other stage is reachable.

Manager signal: Do you include everyone? Do newer or quieter team members get acknowledged? Is your culture visibly welcoming to people who are different from the majority?

Stage 2: Learner safety

People feel safe to ask questions, make mistakes, and experiment without fear of embarrassment. This is where genuine learning happens — or doesn't.

Manager signal: How do you respond when someone asks a basic question? When someone makes a mistake, do you focus on understanding what happened or on assigning blame? Your reaction to the first few mistakes you observe sets the norm for everything that follows.

Stage 3: Contributor safety

People feel safe to contribute their full capabilities — bringing ideas, challenging the approach, and taking ownership. This is where teams move from executing orders to generating value together.

Manager signal: Do people speak up in meetings, or do they wait to see what you think first? If your team consistently agrees with your initial position, that is a warning sign.

Stage 4: Challenger safety

People feel safe to challenge the status quo — to question decisions, raise concerns about direction, and say "I think there is a better way" without fear of consequence. This is the highest and rarest form of psychological safety.

Manager signal: Have you been genuinely challenged by someone on your team in the last month? If not, either your direction has been flawless, or your team does not feel safe to push back.

How to build psychological safety at work as a manager

Model vulnerability first

Psychological safety at work cannot be mandated. It has to be demonstrated. The fastest way to build it is to be visibly vulnerable yourself: admit when you don't know the answer, acknowledge when you were wrong, share a mistake and what you learned from it.

When the most senior person in the room is willing to be uncertain, it signals to everyone else that uncertainty is allowed.

Respond to bad news as if it is valuable

The way you react when someone brings you a problem sets the entire norm for your team. If you visibly stress, shoot the messenger, or go quiet when something goes wrong, people will stop bringing you problems early — when they are still fixable.

The response to practise: thank them for raising it, ask what they need, and focus on what happens next rather than who is to blame.

Ask more than you assert

In a meeting, a manager who talks most tends to close down discussion. A manager who asks questions tends to open it up. Genuine curiosity — "What are we missing here?" "What would you do differently?" "Is there anything that could go wrong that we haven't talked about?" — signals that different views are not just tolerated but actively sought.

Separate brainstorming from evaluation

When teams conflate idea generation with judgment, they produce fewer ideas. People self-censor before they speak. Create explicit moments of "no evaluation yet" — where the only goal is volume of ideas. Evaluation comes later.

Address exclusion and dismissal immediately

If someone is interrupted, ignored, or subtly mocked in a meeting, say something. Not aggressively, but calmly and directly: "I want to hear the rest of that thought" or "I don't think we've fully explored that idea yet." Silence in the face of dismissal is endorsement.

Use retrospectives as learning rituals

Regular retrospectives — especially ones where the manager participates as a peer rather than a judge — are one of the most reliable ways to build psychological safety over time. Frame them explicitly as "what can we all learn from what happened," not "who did what wrong."

What psychological safety at work is not

Psychological safety at work is frequently misunderstood. It is not the absence of accountability. Standards still exist. The difference is that when something goes wrong, the first question is "what can we learn?" not "who is to blame?"

Not enforced positivity. A culture where only positive emotions are acceptable is not psychologically safe — it just looks that way from the outside.

Not consensus. Psychological safety enables honest disagreement. It should produce more challenge and debate. If your team agrees on everything, ask whether that is genuine alignment or suppressed doubt.

How Lead-well supports psychological safety at work

Lead-well's Intervention Builder helps managers think through specific situations where psychological safety at work has broken down: a team member who has gone quiet, a team that only gives positive updates, a dynamic where one person dominates and others disappear.

The weekly reflection prompts include questions about psychological safety at work — team energy and communication quality — so you are thinking about this consistently as part of your leadership practice, not only when it becomes a crisis.

10 things managers can do this week to build psychological safety

1. In your next team meeting, ask a question before making a statement — every time you assert first, you reduce space
2. When someone brings you bad news, thank them out loud — "I'm glad you told me" changes the norm
3. In a 1-on-1, ask: "Is there anything you've been hesitant to bring up?" — the question signals safety
4. If someone is interrupted in a meeting, slow down: "Let's hear the rest of that"
5. Share a mistake you made and what you learned from it — vulnerability models what you want
6. Ask the quietest person in the room what they think — by name, directly, without pressure
7. After a project goes wrong, run a blameless retrospective — focus on process, not people
8. Stop asking "any questions?" — it closes down; instead try "what's unclear?" or "what are we missing?"
9. Explicitly separate brainstorm time from evaluation time in your next planning session
10. Check: does everyone on your team have a moment each week where their voice clearly lands? If not, that's the signal.

For more on the team dynamics that make this possible, see our guide on how to handle conflict in your team — psychological safety and healthy conflict go hand in hand.

Frequently asked questions