You've probably heard the term by now. Google made it famous in 2012 when their internal research — Project Aristotle — found that psychological safety was the single biggest predictor of high-performing teams. Since then, it's become one of those phrases that gets dropped in leadership meetings with a lot of nodding and very little follow-through.

So what does it actually mean? And more importantly, what does it look like in practice — not in a research paper, but on a Tuesday afternoon when someone disagrees with the direction your team is heading?

The definition people use (and why it's incomplete)

Most definitions of psychological safety sound something like this: a shared belief that the team is safe for interpersonal risk-taking.

That's accurate, but it's abstract enough to be almost useless. Risk-taking sounds like skydiving. What we're actually talking about is much quieter: whether someone on your team feels safe enough to say "I don't think this is working" without bracing for consequences.

It's the difference between a meeting where everyone nods along and a meeting where someone says the thing that actually needed to be said.

What psychological safety is not

This is where most organizations go wrong.

It's not niceness. A team can be extremely pleasant and have almost no psychological safety. If the norm is to keep things smooth, people learn quickly that honest feedback isn't actually welcome — regardless of what the values poster says.

It's not the absence of conflict. Psychologically safe teams argue. They disagree. They push back on each other's ideas. The difference is that the conflict is about the work, not about social survival.

It's not a workshop outcome. You can't build psychological safety in a day. You build it — or erode it — in thousands of small moments: how a leader responds when someone brings a problem, whether mistakes get examined or punished, whether the quietest person in the room is ever genuinely invited to speak.

The two things that actually build it

After ten years of working with teams, I've found that psychological safety consistently comes down to two things.

1. Predictability of response.People take interpersonal risks when they can reasonably predict how the other person will react. As a leader, this means your response to bad news, dissenting opinions, and honest mistakes matters more than almost anything else you do. If you react with defensiveness or blame — even once, even subtly — people update their model of what's safe to say around you. That update is hard to undo.

2. Explicit permission, repeatedly given.Psychological safety doesn't emerge from an open-door policy. It emerges when leaders actively and specifically invite honest input — and then visibly act on it. Not "my door is always open," but "I want to know what's not working, and here's what I did with the last thing someone told me."

A simple diagnostic

If you want to get a quick read on the psychological safety of your team, try this. In your next meeting, notice:

• Who speaks first?
• Who speaks most?
• Who never speaks at all?
• What happens when someone expresses doubt or pushes back?

You don't need a survey to start seeing the patterns. They're already happening. The question is whether you're looking.

The uncomfortable part

Psychological safety is ultimately a leadership problem, not a team problem. Teams don't create unsafe environments on their own — they respond to the cues that leaders set, often without realizing they're setting them.

Which means that building a psychologically safe team starts with a harder question than "how do we get people to speak up more?" It starts with: What am I doing that might be making it hard to?

That question is uncomfortable. It's also the only one worth asking.

-----

Designfulness works with leadership teams and organizations to build the conditions that make honest collaboration possible. If this resonated, [book a discovery call] or [subscribe to the newsletter] for more.