← Work psychology

Learning requires speaking up

Psychological safety in teams

Make it possible to ask, challenge and admit mistakes while keeping standards and accountability clear.

Amy C. Edmondson · 1999 · Original editorial explanation
Psychological safety in teams — simplified model sketchInterpersonal safety · Questions & concerns · Team learning · Better-informed action. Editorial interpretation, after Amy C. Edmondson (1999).Interpersonal safety01Questions &concerns02Teamlearning03Better-informedaction04ADM HR · ORIGINAL INTERPRETATIONAmy C. Edmondson · 1999
Original simplified sketch after Amy C. Edmondson (1999). Read the explanation for assumptions and limitations. Download SVG ↗

The core idea

Edmondson describes team psychological safety as a shared belief about the safety of interpersonal risk-taking. Her 1999 study linked it with team learning behaviour. Asking for help, reporting an error or challenging an assumption can carry social risk. Psychological safety concerns that risk; it is not the same as friendliness, personal confidence, agreement or an absence of performance expectations.

Source and attribution [1]

Using it in practice

Observe what happens after someone raises an awkward issue. Leaders can acknowledge uncertainty, invite specific contributions and respond constructively. Separate learning about a mistake from decisions about responsibility. Close the loop after concerns are raised so speaking up has a visible purpose. Make reporting routes accessible to people with less status, including new starters and temporary workers.

An example, not a reported case

Worked example · illustrative

A project team says questions are welcome, but meetings reward rapid agreement. The lead begins by identifying an assumption they may have wrong, then invites each discipline to name a risk. A junior colleague highlights an implementation problem; the lead thanks them and assigns follow-up rather than defending the plan. The review tracks whether concerns lead to decisions, not just how many people speak.

What to watch for

A rising number of reported problems may indicate improved reporting rather than worsening performance. Do not use a single survey score to label or rank individual employees.

Define the behaviour you want to make possible

Choose a concrete action: asking for help, admitting uncertainty, reporting a near miss or challenging a proposal. Safety is easier to discuss when linked to an actual interpersonal risk. Ask what someone expects would happen if they took that risk in this team. Do not equate a friendly atmosphere with safety; colleagues can enjoy one another's company while avoiding difficult truths. Equally, candid disagreement can occur in a team where people feel respected.

Change the response to a difficult message

In an illustrative meeting, a junior colleague points out a flaw in a plan. The leader can thank them for raising it, ask for the evidence and explain how the issue will be examined. This does not require accepting the claim without scrutiny. It demonstrates that speaking up leads to a serious response rather than humiliation. Follow through after the meeting; a supportive phrase loses credibility if the person later loses opportunities for being inconvenient.

Pair openness with standards

Explain the expected standard and how errors, learning needs and deliberate misconduct are distinguished. Psychological safety does not mean every action is acceptable or that performance concerns cannot be addressed. Use fair, evidence-based processes and discuss problems without attacking identity. When an error occurs, ask what the system contributed and what the person could reasonably have done. Avoid promising a blanket absence of consequences that the organisation cannot honestly deliver.

Read the indicators carefully

More reported problems can indicate greater willingness to speak, worsening conditions or both. Combine reporting patterns with the quality of response, follow-up and employee accounts. Do not rank teams using a short survey alone or pressure staff to give positive scores. A useful review asks whether concerns are resolved and whether quieter or less powerful colleagues can participate. The goal is better learning and safer decisions, not an appearance of universal agreement.

Observe the response to an inconvenient contribution

The decisive evidence may be what happens after someone admits an error, asks a basic question or challenges a plan. Does the manager investigate respectfully, become defensive or later exclude the person? Ask employees for examples while protecting confidentiality. A friendly team can still be unsafe for disagreement, and a demanding team can be safe when challenge is welcomed and handled fairly. Do not equate comfort with psychological safety.

Combine openness with a clear standard

In an incident review, explain that the aim is to understand what happened and improve the system, while retaining accountability for deliberate or reckless conduct through appropriate processes. Invite alternative explanations and follow through on issues raised. Nabeel’s distinction between observable behaviour and outcomes helps avoid treating a survey score as the whole culture. Track whether concerns produce useful action and whether people can question senior views. More reported problems may initially indicate improved openness rather than deteriorating performance.

Take it into your next conversation

Three useful questions.

  1. What happened the last time someone challenged a plan?
  2. Whose voice is missing?
  3. Do concerns receive a response?

Related terms

Go to the evidence

Sources & attribution

[1] Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams. ↗

The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.

Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.

Published 2026-09-20 · Reviewed 2026-09-22. Editorial approach

Keep exploring

A little more context.

A historical lens on needs01

Maslow’s hierarchy of needs

A useful prompt for looking beyond pay—but not a universal staircase every employee must climb.

Abraham H. Maslow4 min
Conditions & the work itself02

Herzberg’s two-factor theory

Separate preventable dissatisfaction from the features of work that can create meaning, achievement and growth.

Frederick Herzberg, Bernard Mausner4 min
Autonomy · competence · relatedness03

Self-determination theory

Support the quality of motivation by making room for agency, mastery and connection.

Edward L. Deci4 min