Leadership & Teams

Psychological Safety and Team Performance

Marin Niehues16 January 202511 min read

Manager in a conversation at a desk

Psychological safety raises team performance because employees raise mistakes and doubts early and the organization corrects course faster as a result. Harvard researcher Amy Edmondson established the concept at team level in 1999 and made it measurable. It describes a team's shared belief that interpersonal risks can be taken without fear of negative consequences. From a delivery perspective this is a question of early warning: a problem that first appears in the status report has usually become expensive already.

What is psychological safety in a team?

Psychological safety is a team's shared belief that objections, and admitting mistakes, carry no penalty for the person concerned. It is a property of the team rather than a personality trait, and it differs from harmony: a psychologically safe team argues on substance, and often.

The term itself comes from organizational research in the 1960s. Edgar Schein and Warren Bennis described it in 1965 as a precondition for people to accept change. William Kahn applied it in 1990 to the engagement of individuals at work. Edmondson lifted the concept to team level in 1999 and developed a scale to measure it.

In daily work, psychological safety shows in concrete situations. A developer reports in the daily stand-up that she misunderstood an interface, and the team adjusts the plan the same day. A new colleague asks in his second week why an approval step exists, and the answer leads to the step being dropped. A project lead sets the status to amber as soon as he doubts a deadline instead of waiting for certainty. In each case, information reaches the point of decision sooner.

What the research shows

Research shows a stable link between psychological safety, learning behavior and team performance. Edmondson studied 51 work teams in a manufacturing company and found that teams with higher psychological safety showed more learning behavior: they asked questions and sought feedback, and they discussed mistakes openly. This learning behavior in turn was associated with team performance.

An earlier study by Edmondson on hospital wards had produced a result that is surprising at first: the better-led wards reported more errors. Edmondson interpreted the difference as a matter of willingness to report. Where mistakes can be reported without consequences for the person, they become visible, and only then can the organization learn from them.

A meta-analysis of more than 130 independent samples confirmed in 2017 the link with performance and engagement across industries and countries. In corporate practice the concept became known through an internal study by Google on team effectiveness, published in 2015. Psychological safety emerged there as the most important of five dynamics of effective teams, ahead of dependability, structure and clarity, meaning and impact.

Edmondson's four zones

In her 2018 book “The Fearless Organization”, Edmondson places teams in a matrix with two axes: the level of performance standards and the level of psychological safety. This produces four zones, and only one of them delivers good results over time.

For the executive team, the anxiety zone is the most expensive. From the outside it looks like performance, because standards are high and the team appears busy. The costs arise out of sight, as late escalation and as rework after decisions that nobody challenged.

Timothy Clark's four stages

A second widely used model comes from Timothy R. Clark and describes psychological safety as a sequence of four stages. The first is inclusion safety, the second learner safety, the freedom to learn and make mistakes. At the third stage, contributor safety, team members dare to contribute independently; at the fourth, challenger safety, they openly question the status quo and their superiors. The model is useful for diagnosis because it shows at which stage a team stalls. Teams stuck at stage three deliver reliably but raise no objections to weak decisions.

Why psychological safety is a delivery issue

Psychological safety shortens the path that information takes to a decision, and it works at three points.

First, it shortens the time to escalation. A typical pattern: a team member realizes a delivery date cannot be met and waits two weeks, hoping to catch up and unwilling to own the delay alone. The status report stays green. Correction begins only when the delay can no longer be hidden, and by then it costs more.

Second, it improves decisions. Dissent before a decision is cheaper than resistance during implementation. In teams where objections go unspoken in the meeting, they reappear later as delay or quiet workarounds.

Third, it lowers the barrier to asking for help. Anyone who recognizes after an hour that a task is unclear and asks saves the project days. Anyone who stays silent to appear competent consumes capacity in the wrong place.

How do you measure psychological safety?

You measure psychological safety with a short, anonymous survey based on Edmondson's scale and complement it with observation in daily work. The scale comprises seven statements that team members rate from strongly disagree to strongly agree. Three of them are negatively worded and reverse-scored.

Four checkpoint questions are enough for observation:

  • Handling mistakes: are deviations reported before someone else finds them?
  • Dissent: who disagrees in decision meetings, and how does the leader respond?
  • Help: how quickly do team members ask for support, and how is the request received?
  • Review: are failures analyzed without searching for culprits?

Survey twice a year and report only from five responses per team so that anonymity is preserved. The score becomes meaningful in comparison between teams with similar tasks and over time. It belongs next to delivery metrics so that the executive team sees links between team climate and on-time delivery.

What destroys psychological safety?

Psychological safety is destroyed fastest by a leader who responds to an honest report with public exposure or blame. A single such moment outweighs many friendly conversations, because the team reads it as the rule.

Four further patterns have a similar effect. The leader speaks first in decision meetings and thereby fixes the answer. Questions are treated as a sign of incompetence. Individual mistakes appear by name in reports to management. And promises of openness hold only as long as the news is pleasant. Anyone who wants to build psychological safety first checks which of these patterns occurs in their own area.

Five levers for leaders

Psychological safety arises in the behavior of the leader whom the team experiences every day. Five levers have the greatest effect:

  1. Name your own mistakes and knowledge gaps first. The team follows what the leader models.
  2. Reward reports of problems. Whoever reports a deviation early receives thanks and support before the question of cause is raised.
  3. Plan for objections. Decision meetings explicitly ask for counter-arguments, and the leader speaks last.
  4. Ask before judging. A review starts with “What have we learned?” and ends with concrete changes.
  5. Keep standards and accountability. Safety applies to raising problems; the team's goals remain unchanged.

These levers are part of building high-performing teams overall. Building takes repetition, because the team registers precisely how the leader responds to the first report of a mistake.

Niehues Consulting as a partner for teams that deliver

Psychological safety becomes effective when the organization builds it into its steering. Niehues Consulting works on this from a delivery perspective. Organization design creates roles and decision paths on which information takes the shortest route and dissent has a fixed place. Delivery management, as delivery manager, project manager or product owner, creates the routines in which deviations surface early, from reviews to escalation paths.

The approach follows the Niehues Delivery Model with the phases Understand, Build and Roll out. Three of its checkpoint questions matter for team climate and delivery. What is the baseline, and how do we measure success? Which roles, decision paths and interfaces does operation require? And which metric shows after 90 days that the change is landing? The article characteristics and metrics of a high-performing organization sets out the wider framework.

Founder Marin Niehues is a management consultant who builds organizations that deliver, in projects ranging from VC-funded scale-ups to DAX 40 corporations. The entry point is a free initial consultation of 30 minutes.

Frequently asked questions

What is psychological safety in a team?

Psychological safety is a team's shared belief that it is safe to admit mistakes and voice concerns openly. The team-level concept goes back to Amy Edmondson, who established it in 1999 in research on work teams; the term itself comes from organizational research in the 1960s.

How do you measure psychological safety?

It is measured with Edmondson's scale, seven statements rated in a short, anonymous survey. Leaders additionally observe how mistakes are reported and how dissent is handled in decision meetings. The trend over several measurements is what counts.

What are the seven questions in Edmondson's psychological safety survey?

The survey contains seven statements, for example “It is safe to take a risk on this team” and “It is difficult to ask other members of this team for help”. Three statements are negatively worded and reverse-scored. The full list is in the box above.

What are the four stages of psychological safety?

Timothy R. Clark distinguishes four stages: inclusion safety, learner safety, contributor safety and challenger safety. Each stage builds on the previous one. For decision quality the fourth stage counts, because only there are objections to superiors voiced openly.

What destroys psychological safety?

Public exposure and blame after an honest report have the strongest effect. Leaders who speak first in meetings and reports that pass mistakes upwards by name add to it. A single incident is enough, because the team reads it as the rule.

What are examples of psychological safety at work?

Typical examples are an employee who reports her own mistake in the daily stand-up, a new colleague who questions an existing rule, and a project lead who sets a deadline to amber early. In each case the information reaches the decision sooner. The team responds with solutions instead of blame.

How can a leader build psychological safety?

A leader builds psychological safety through repeated behavior: naming their own mistakes first and actively seeking counter-arguments. The effect shows after several months, because teams test the leader's response over time.

Does psychological safety lower performance standards?

Psychological safety does not lower performance standards. In Edmondson's model, the learning zone arises where high standards and high safety meet. Goals remain demanding, and the team raises obstacles earlier.

Let’s talk about your initiative.

In 30 minutes we clarify where your organization stands and which step will pay off most now.

Request a consultation

30 minutes · free · no obligation