What is psychological safety at work?

What is psychological safety at work?

Performance & metrics Updated October 2026

Psychological safety is a team's shared belief that people can ask questions, admit mistakes and disagree without being punished or embarrassed. Amy Edmondson defined it in 1999, Google's Project Aristotle made it famous, and in hierarchical Indian teams its absence usually shows up as silence and late surprises.

Psychological safety is a shared belief within a team that it is safe to take interpersonal risks: to ask a basic question, admit a mistake, flag a problem or disagree with the boss without being embarrassed or punished. It is a property of a team, not of a whole company, which is why two teams under the same organisational culture can feel completely different.

Where the idea comes from

Amy Edmondson of Harvard Business School defined team psychological safety in a 1999 paper in Administrative Science Quarterly, based on a study of 51 work teams at a manufacturing company. Her finding was that safety went with learning behaviour: teams that felt safe sought feedback, discussed errors and experimented, and that learning was linked to performance. An earlier strand of her research on hospital teams had found that better-led units reported more errors, likely because people felt able to report them, not because they made more.

The idea reached a mass audience through Google’s Project Aristotle, an internal study of 180 Google teams. Google’s researchers listed five dynamics of effective teams (psychological safety, dependability, structure and clarity, meaning, and impact) and found psychological safety mattered most; the New York Times covered the findings in February 2016. Keep the limit in mind: it was one company studying its own staff, not peer-reviewed research.

It is also not the same as being nice or lowering standards. Edmondson’s own framing is that high standards plus high safety produce learning; high standards with low safety produce anxiety and hidden problems.

What it looks like in Indian teams

Hierarchy and deference to seniority run deep in many Indian workplaces, so silence is the default, not a sign that all is well. Typical tells:

  • A delivery team in a GCC says “yes, doable” to every client ask, and the slipped deadline surfaces only at the status review.
  • A shift supervisor in a plant does not report a near-miss because the last person who did was blamed.
  • In a skip-level meeting, juniors only raise issues once their manager has left the room.

The fixes are behavioural and sit with the team lead: ask for dissent by name (“Ravi, what would make this fail?”), respond to bad news with a question rather than blame, run blameless post-incident reviews, and admit your own mistakes first.

Frequently asked questions

How do we measure it?

Edmondson’s seven-item team survey is widely used, with statements such as whether mistakes are held against you. Run it by team, not company-wide, alongside a short pulse survey, and compare teams rather than chasing one score.

Is psychological safety the same as engagement?

No. Engagement is an individual’s commitment to the work; psychological safety is a team’s shared belief about speaking up. A highly engaged person can still keep quiet in a team where speaking up gets punished.

Does it protect people from accountability?

No. Missed targets and misconduct still have consequences through continuous feedback and, where needed, formal action. What changes is that honest reporting of a problem is not itself punished.

Where silence comes from fear of a specific manager, the formal routes are the grievance redressal process and a whistleblower policy.

← All HR glossary terms