Psychological Safety at Work: What It Actually Means and Why It's an HR Issue

Key Takeaways

• Psychological safety is not about comfort, niceness, or lowering standards. Harvard's Amy Edmondson, who coined the term, defines it as a shared belief that the team is safe for interpersonal risk-taking.

• Google's Project Aristotle, which studied more than 180 of its own teams, identified psychological safety as the single most important factor distinguishing high-performing teams from the rest.

• Psychologically safe teams report more errors, not fewer. That is a feature, not a flaw. They surface problems instead of hiding them.

• Psychological safety is built or eroded primarily at the team level, through manager behaviour, which makes it a direct HR and people-strategy concern rather than a vague cultural aspiration.

• The phrase has become a workplace buzzword, which has made it easy to talk about and hard to actually build. The gap between saying the words and doing the work is where most organizations get stuck.

  
  

A Term That Got Popular Faster Than It Got Understood

Few workplace concepts have traveled as far, as fast, as psychological safety. It shows up in leadership decks, job postings, values statements, and LinkedIn posts. And somewhere along that journey, it lost most of its meaning.

For a lot of people, the phrase has come to mean something like "a workplace where everyone is nice to each other" or "a place where nobody gets criticized." Both of those readings are wrong, and the second one is actively harmful. Psychological safety is not about avoiding hard conversations. It is about making hard conversations possible.

This matters because the gap between the popular version of the concept and the actual research-backed version is where organizations waste effort. They invest in surface-level initiatives, soften their feedback, avoid difficult truths in the name of being supportive, and then wonder why performance does not improve and why their best people still leave. They have mistaken comfort for safety. The two are not the same, and confusing them comes at a real cost.

What Psychological Safety Actually Means

The concept comes from Amy Edmondson, a professor at Harvard Business School, who formally defined team psychological safety in a 1999 study as a shared belief held by members of a team that the team is safe for interpersonal risk-taking.

That definition is precise, and every word is doing work. It is a shared belief, meaning it lives at the level of the team, not the individual. It is about interpersonal risk, the small but constant risks people take when they raise a concern, admit a mistake, ask a question that might seem obvious, or challenge a decision made by someone more senior. And it is about whether the team is safe for those risks, meaning whether people can take them without fear of being embarrassed, punished, or seen as incompetent.

Edmondson herself has been clear about what psychological safety is not. It is not about coziness. It is about candor. As she puts it, psychological safety means being able to do your job without fear of humiliation or punishment. It is the freedom to say the hard thing without risking your standing on the team.

This is the part the buzzword version misses entirely. Psychological safety does not lower the bar. It raises it. When people feel safe to surface problems, challenge weak ideas, and admit when something is not working, the team makes better decisions and holds higher standards. The discomfort does not disappear. It just becomes productive instead of suppressed.

The Counterintuitive Finding That Started It All

Edmondson's original research produced a result she did not expect, and it remains one of the most instructive findings in the entire field.

She was studying medical teams in hospitals, looking at the relationship between team effectiveness and the rate of errors. Her hypothesis was reasonable: better teams would make fewer mistakes. The data showed the opposite. The higher-performing teams reported more errors, not fewer.

For a moment that looked like a contradiction. Then the explanation became clear. The better teams were not making more mistakes. They were reporting more of them. On those teams, people felt safe enough to admit when something had gone wrong, which meant problems got surfaced, discussed, and fixed. On the lower-performing teams, mistakes were hidden out of fear, which meant they festered, repeated, and compounded.

That distinction sits at the heart of why psychological safety matters so much. An organization where people hide problems is not a healthy one, even if it looks calm on the surface. The silence is not the absence of problems. It is the absence of the safety required to name them.

Why Google's Research Made This Impossible to Ignore

For years, psychological safety lived mostly in academic and healthcare circles. What brought it into the mainstream of business was Google.

Around 2012, Google launched an internal research effort called Project Aristotle, designed to answer a deceptively simple question: what makes some teams perform far better than others? The People Operations team studied more than 180 Google teams, ran over 35 statistical models, and analyzed hundreds of variables, from individual intelligence to team composition to how often colleagues socialized outside work.

The result surprised them. Who was on the team mattered far less than how the team worked together. And of all the dynamics they measured, one stood out as the most important by a clear margin: psychological safety. The teams where people felt safe to take interpersonal risks consistently outperformed those where they did not.

Project Aristotle identified five factors that drove team effectiveness, in order of importance: psychological safety, dependability, structure and clarity, meaning, and impact. Psychological safety was the foundation the others rested on. A team can have clear goals and meaningful work, but if people do not feel safe to speak honestly, those advantages get undermined.

It is worth being measured about what this study proves. Project Aristotle was observational, which means it identified strong associations rather than airtight causation, and Google's workforce is not representative of every organization. But its findings line up with decades of independent research, including Edmondson's, and with frameworks like Lencioni's work on team dysfunction, which places trust at the foundation of everything else. The weight of evidence points consistently in the same direction.

Why This Is an HR Issue, Not Just a Leadership Nicety

Here is where psychological safety stops being an abstract idea and becomes a concrete people-strategy concern.

Psychological safety is built or destroyed primarily at the team level, through the daily behaviour of managers. It is not created by a values statement, a company-wide email, or an annual engagement survey. It is created in how a manager responds when someone admits a mistake, raises a concern, or disagrees in a meeting. One dismissive reaction, one moment of public criticism, one instance of shooting the messenger, and the safety on that team takes a step backward. People learn very quickly what is actually safe to say and what is not, regardless of what the official culture claims.

That makes psychological safety a direct extension of manager capability, which is one of the most important variables in any organization's people strategy. A manager who knows how to invite input, respond well to bad news, admit their own mistakes, and separate the problem from the person builds safety almost automatically. A manager who reacts defensively, plays favourites, or punishes candor destroys it just as quickly, often without realizing they are doing it.

This is precisely why psychological safety belongs in the HR domain. The behaviours that create it can be taught. The conditions that support it can be built into how an organization hires, onboards, trains, and evaluates its managers. And the absence of it can be measured, if an organization knows what to look for. Left to chance, psychological safety varies wildly from team to team within the same company. Built deliberately, it becomes a consistent feature of how the organization operates.

The Connection to Retention and Performance

Psychological safety is not a soft outcome that sits separate from the metrics organizations actually track. It feeds directly into them.

On the retention side, the link is straightforward. People leave environments where they feel unheard, where raising concerns is futile or risky, where mistakes are punished rather than learned from, and where speaking honestly carries a cost. They stay in environments where they feel their voice matters and their contribution is valued. Psychological safety is a significant part of what determines which kind of environment a team actually is, beneath whatever the official culture says.

On the performance side, the connection runs through innovation, problem-solving, and quality. Teams that feel safe surface issues earlier, when they are cheaper and easier to fix. They share information more freely. They challenge weak assumptions before those assumptions turn into expensive mistakes. They take the kind of calculated risks that innovation requires. Teams that lack safety do none of these things reliably, because the personal cost of speaking up feels higher than the organizational cost of staying silent. That silence is expensive, and it rarely shows up as a line item.

For organizations in competitive Alberta sectors, where retaining skilled people and adapting quickly both matter enormously, psychological safety is not a wellness initiative. It is a performance and retention factor that happens to be invisible until it is missing.

The "Psychological Safety Washing" Problem

A real risk has emerged as the concept has become popular: organizations adopting the language of psychological safety without doing any of the actual work.

It is easy to put the phrase in a values statement. It is easy for a leader to say "my door is always open" or "there are no bad ideas here." It is much harder to respond well in the actual moment when an employee delivers unwelcome news, challenges a decision, or admits a costly mistake. That moment, repeated over time, is where psychological safety is really determined. The words are free. The behaviour is the work.

Employees see through the gap immediately. A team told that it is safe to speak up, whose members then watch a colleague get punished for doing exactly that, becomes less safe than a team that never made the claim at all, because now the official message and the lived reality are openly in conflict. Stated safety that is not backed by real behaviour does not just fail to help. It actively erodes trust.

This is why psychological safety cannot be delegated to a slogan. It has to be built into how managers are selected, trained, and held accountable, which brings it squarely back to HR infrastructure and people strategy.

What Building It Actually Requires

Creating genuine psychological safety is not complicated to understand, though it takes consistency to sustain. A few things matter most.

Managers have to model fallibility. When a leader admits their own mistakes and uncertainties openly, it signals to everyone else that doing so is safe. When a leader projects infallibility, it signals the opposite.

Reactions to bad news have to be handled with care. The single fastest way to destroy safety is to react badly the first time someone brings a problem forward. The single best way to build it is to respond to bad news with curiosity and appreciation rather than blame, even when the news is genuinely unwelcome.

Participation has to be actively invited, not just permitted. Project Aristotle found that equal conversational turn-taking was a hallmark of effective teams. People who are quieter, more junior, or culturally less inclined to speak up need to be deliberately brought into the conversation, not just left to volunteer.

And accountability has to coexist with safety, not compete with it. This is the part organizations most often get wrong. Safety without accountability becomes complacency. Accountability without safety becomes fear. The two are not opposites. High-performing teams hold both at once: high standards and the safety to be honest about whether those standards are being met.

These are learnable behaviours. They can be built into management training, reinforced through how managers are evaluated, and supported by HR infrastructure that treats people leadership as a skill rather than an assumption. That is the work. It is not glamorous, and it does not happen through a single initiative. But it is what separates organizations that actually have psychological safety from those that merely talk about it.

FAQ

Isn't psychological safety just another way of saying "be nice to employees"?

No, and this is the most common and most damaging misunderstanding. Niceness can actually work against psychological safety when it means avoiding hard truths to keep things comfortable. Real psychological safety is about candor, the ability to raise difficult issues, disagree, and admit mistakes without fear. It enables tough conversations rather than avoiding them. Edmondson is explicit that it is about candor, not coziness.

Does psychological safety mean lowering performance standards?

The opposite. Psychologically safe teams tend to hold higher standards because people can be honest about what is working and what is not. When mistakes can be surfaced and discussed openly, they get fixed and learned from rather than hidden and repeated. Accountability and safety reinforce each other. A team that feels safe but has no standards becomes complacent. A team with high standards but no safety becomes fearful and dishonest. High performance requires both.

How do you actually measure psychological safety?

It can be measured through validated survey instruments, many of them derived from Edmondson's research, that assess whether team members feel able to take interpersonal risks. Questions explore whether people feel safe admitting mistakes, raising concerns, and disagreeing. Importantly, psychological safety should be measured at the team level rather than the whole-organization level, because it varies significantly from manager to manager. An organization-wide average can hide teams that are struggling badly. Pulse surveys and skip-level conversations can supplement formal measurement.

Whose responsibility is psychological safety, leadership or HR?

Both, working together. Senior leadership sets the broader tone and signals whether candor is genuinely valued. But psychological safety is built day to day at the team level through manager behaviour, which is where HR plays its critical role: selecting, training, and supporting managers to build it, and measuring where it is present and where it is missing. It is not the job of any single function. It is a shared responsibility that requires real infrastructure to sustain.

We are a small organization. Is this relevant to us, or is it a big-company concern?

It is arguably more relevant for smaller organizations. In a small team, a single manager who shuts down candor can damage the culture of a significant portion of the workforce, and there is less organizational buffer to absorb the effect. Small organizations also depend heavily on every person contributing fully, which psychological safety directly enables. The concept scales down better than almost any other people-strategy idea, because so much of it comes down to how a handful of managers behave.

This post is for general informational purposes. For guidance on building people practices suited to your organization, consult a qualified HR professional.

Stoppler Hughes helps Alberta organizations build the manager capability and people infrastructure that turn ideas like psychological safety into how teams actually operate, not just what they say.

Learn more at stopplerhughes.com.