psychological-safety

name	psychological-safety
description	Use when building or assessing psychological safety on teams — covers Edmondson's research, leader behaviors, and diagnostic signals.

Psychological Safety

What It Is

Amy Edmondson's foundational research (1999, 2003, 2018): psychological safety is the shared belief that the team is safe for interpersonal risk-taking — admitting mistakes, asking questions, raising concerns, suggesting half-formed ideas.

It is not:

• Comfort
• Agreement or harmony
• Absence of conflict
• Lower performance standards
• Being protected from criticism

The research is unambiguous: high-safety teams disagree more, surface problems faster, learn faster, and make fewer fatal errors. Low-safety teams maintain pleasant surfaces while problems metastasize.

The Edmondson Matrix

	Low Standards	High Standards
Low Safety	Apathy zone	Anxiety zone (burnout, hidden mistakes)
High Safety	Comfort zone (atrophy)	Learning zone

Psychological safety + high standards = the learning zone. Either alone is insufficient.

Edmondson's 7-Item Scale

(Paraphrased; useful in surveys)

1. If you make a mistake on this team, it is not held against you
2. Members of this team are able to bring up problems and tough issues
3. People on this team sometimes accept others for being different
4. It is safe to take a risk on this team
5. It isn't difficult to ask other members of this team for help
6. No one on this team would deliberately act in a way that undermines my efforts
7. Working with members of this team, my unique skills and talents are valued and utilized

Leader Behaviors That Build Safety

Per Edmondson and subsequent practitioner work:

1. Frame work as a learning problem when uncertainty is high — not as an execution problem
2. Acknowledge your own fallibility: "I might be missing something — please push back"
3. Model curiosity: ask many questions, especially of the most junior person in the room
4. Respond to bad news with curiosity, not punishment: "What did we learn?" before "Whose fault is this?"
5. Reward the messenger: thank the person who surfaces problems, even uncomfortable ones
6. Specifically invite dissent: "Who has a different take?" works better than "Any objections?"
7. Call out bias toward looking good: name when the team is performing alignment instead of probing

Common Failure Modes

• Equating safety with niceness: then watering down standards
• Equating high standards with low safety: then watering down honesty
• Hiring "high-bar" people then punishing them for raising concerns
• Surveying for safety without changing behavior in response
• Treating safety as a culture poster rather than specific leader behaviors
• Performative humility ("I might be wrong about everything!") — signals weakness rather than openness
• Using "psychological safety" as code for "agree with me"

Diagnostics

Quick reads on team safety:

• Does the most junior person speak up in meetings?
• When the senior leader floats a half-baked idea, does anyone push back?
• When someone makes a mistake, is the first conversation about the mistake or about the person?
• What happens after a postmortem — does anything actually change?
• Do people report comfort disagreeing with their manager? (Survey item, with limits.)
• What's the gap between what people say in private vs. public?

A widening gap between private and public discourse is the leading indicator of low-safety culture.

Where to Engineer for Candor

• Engagement surveys (anonymity, action)
• Performance reviews (calibrated; appeals real)
• 1:1s and feedback (frequent, narrowly-scoped, low-stakes)
• Postmortems and retrospectives (blameless framing)
• Whistleblowing channels (multiple, non-retaliation, tracked)
• Layoffs and RIFs (honesty over reassurance)

Specific Tactics

In meetings

• Round-robin to invite the quietest voices
• "What are we missing?" before "What do you think?"
• Senior leader speaks last on important decisions
• Devil's advocate role (rotated)
• Time for silent reflection before discussion

In 1:1s

• Standing question: "What's something you've been hesitant to bring up?"
• Manager shares own failures and what was learned
• Direct invitation to push back

In retrospectives

• Blameless framing: focus on systems and decisions
• Senior leaders model "I was wrong" first
• Specific behaviors named, not character judgments

What This Rule Doesn't Say

Psychological safety is not:

• Lower the bar for performance
• Avoid conflict
• Make sure everyone feels good
• Protect feelings over honesty
• Hold back hard feedback

The research is precise: it's about interpersonal risk-taking. Performance and accountability standards stay high.

Cross-References

• psychological-safety rule
• feedback-frameworks skill
• culture-architect agent
• engagement-survey-design skill

Key References

• Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly.
• Edmondson, A. (2003). Speaking up in the operating room. Journal of Management Studies.
• Edmondson, A. (2018). The Fearless Organization.
• Google's Project Aristotle research (2015–2017).