Psychological Safety: Create Teams Where People Speak Up

What It Measures

The Psychological Safety assessment evaluates the safety of your team environment using Amy Edmondson's framework:

Speaking Up Safety - Comfort expressing opinions and ideas
Risk-Taking Safety - Freedom to take interpersonal risks
Mistake Safety - How errors are treated
Inclusion Safety - Feeling valued and included

History & Research Foundation

Psychological Safety Research

Amy Edmondson (1999): Pioneered psychological safety research in teams
Google's Project Aristotle: Found psychological safety is #1 predictor of team effectiveness
Harvard Business School: Extensive research on learning organizations

Key Concepts

Definition: Shared belief that the team is safe for interpersonal risk-taking
Not "Being Nice": Safety for disagreement, not just comfort
Learning Environment: Foundation for innovation and improvement

Key Researchers

Amy Edmondson - Psychological safety originator
William Kahn - Original concept in organizations
Google People Analytics - Project Aristotle research

Scientific Validity

⭐⭐⭐⭐⭐ Extensively Validated

Psychological safety is one of the most researched team factors
Predicts learning behavior, innovation, and performance
Google's Project Aristotle confirmed importance across diverse teams

What Your Results Tell You

Safety Levels

High Safety

People speak up freely
Mistakes are learning opportunities
Ideas are welcomed regardless of source
Disagreement is productive
Innovation flourishes

Moderate Safety

Some topics are safe, others avoided
Depends on who's in the room
Calculated risk-taking
Surface-level collaboration
Limited innovation

Low Safety

People stay quiet to avoid risk
Mistakes are punished
Ideas are shot down
Conformity is rewarded
Problems stay hidden

Safety Dimensions

Voice Safety: Can you speak up without fear of punishment? Risk Safety: Can you try new things without career risk? Vulnerability Safety: Can you admit mistakes or ask for help? Inclusion Safety: Do you feel you belong and matter?

Use Cases

Team Assessment

Diagnose current safety level
Identify specific problem areas
Track improvement over time
Compare to organizational norms

Leadership Development

Leaders' critical role in creating safety
Identify leadership behaviors to change
Build awareness of impact
Create intentional safety practices

Performance Improvement

Understand barriers to innovation
Enable better problem-solving
Improve collaboration quality
Reduce hidden inefficiencies

Personal Career

Evaluate team before joining
Understand current difficulties
Decide when safety is unacceptable
Know what you need to thrive

Key Insights

Safety Enables Learning: Teams can't learn from mistakes they're afraid to admit. Safety is the foundation of improvement.

Safety + Accountability: High safety with low accountability is comfort; high accountability with low safety is anxiety. You need both.

Leader's Role Is Critical: Leader behavior sets the tone. One unsafe response can destroy months of safety-building.

Safety Is Not Comfort: Psychological safety means safe to disagree, challenge, and take risks—not safe from all discomfort.

Edmondson's 7 Questions (Team Climate Survey)

If you make a mistake on this team, it is often held against you. (R)
Members of this team are able to bring up problems and tough issues.
People on this team sometimes reject others for being different. (R)
It is safe to take a risk on this team.
It is difficult to ask other members of this team for help. (R)
No one on this team would deliberately act in a way that undermines my efforts.
Working with members of this team, my unique skills and talents are valued and utilized.

(R) = Reverse scored

Building Psychological Safety

Leader Behaviors

Model Vulnerability: Admit mistakes, ask for help
Invite Input: Actively ask for opinions
Respond Productively: Don't punish bad news
Frame as Learning: Position challenges as learning opportunities
Express Appreciation: Thank people for speaking up

Team Practices

Normalize asking questions
Celebrate productive failure
Separate criticism of ideas from criticism of people
Create structured opportunities for input
Debrief without blame

Individual Contribution

Speak up when safe to test boundaries
Support others who speak up
Admit mistakes to normalize vulnerability
Ask questions to encourage others

Red Flags for Low Safety

Ideas consistently come from the same people
Meetings are quiet, real talk happens in hallways
Bad news is delayed or hidden
Blame is common; learning is rare
People leave without explaining why
Conformity is rewarded over contribution

Practical Tips

Start with Self: Model the vulnerability you want to see
Small Steps: Build safety incrementally
Repair Quickly: When safety is broken, acknowledge and repair
Name It: Making safety explicit helps build it
Don't Tolerate Destroyers: One safety-destroying person can poison a team

When Safety Is Absent

If You're a Team Member

Assess carefully: Can it change?
Build safety in small ways
Find allies
Protect yourself
Consider exit if unchanged

If You're a Leader

Examine your own behavior first
Address safety-destroying individuals
Systematically rebuild trust
Measure progress
Persist—it takes time

Limitations

Self-assessment may not capture others' experience
Safety can vary by individual and situation
Structural issues may override interpersonal safety
Requires sustained effort to maintain

Complementary Tools

Team Dynamics - Broader team health assessment
Manager Effectiveness - Manager role in safety
Five Dysfunctions - Team dysfunction framework
Company Culture Match - Organizational culture assessment

Psychological Safety