Psychological Safety

What is Psychological Safety?

Psychological safety is the belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. It was identified by Harvard professor Amy Edmondson as the single most important factor in high-performing teams.

Google's Project Aristotle (2016) confirmed this in a five-year study of 180 teams: psychological safety was the number one predictor of team effectiveness — more important than individual talent, clarity of roles, or the right mix of personalities.

The Westrum Culture Model

Sociologist Ron Westrum described three organisational culture types that predict how information flows — and how teams respond to failure. The DevOps Research and Assessment (DORA) program confirmed that Westrum's generative culture predicts elite software delivery performance.

4 Stages of Safety

Timothy Clark's model identifies four progressive stages of psychological safety that teams move through.

The 7-Question Survey

Amy Edmondson's validated psychological safety survey. Respondents rate each statement on a 1–7 Likert scale (Strongly Disagree → Strongly Agree). Run anonymously, quarterly.

Psychological Safety Scale (Edmondson, 1999)
Note: items 2, 6, 7 are reverse-scored

1. "If you make a mistake on this team, it is often held against you." (R)
2. "Members of this team are able to bring up problems and tough issues."
3. "People on this team sometimes reject others for being different." (R)
4. "It is safe to take a risk on this team."
5. "It is difficult to ask other members of this team for help." (R)
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 utilised."

Scoring:
Reverse items (R): 8 minus the score given.
Team score = mean of all items across all respondents.
<4.5 → significant issues requiring action
4.5–5.5 → moderate; room for improvement
>5.5 → healthy (not complacent — check for Stage 4 safety)

Observable Signals

High psychological safety — observable behaviours:
✓ People admit mistakes openly; bring bad news early
✓ Junior team members challenge senior decisions in meetings
✓ Retrospectives surface real issues, not safe platitudes
✓ People ask "dumb" questions without apology
✓ Disagreement is direct and heard; no passive-aggressive undercurrent
✓ Post-mortems are blame-free; root cause is the focus
✓ People advocate for ideas without requiring approval first

Low psychological safety — warning signals:
⚠ Silence in meetings; questions only asked privately
⚠ "Everything is fine" in retros despite clearly visible problems
⚠ Errors discovered late; nobody flagged early signs
⚠ Ideas attributed upward; people don't take credit for their work
⚠ High attrition in high-performers; low performers stay
⚠ "That's above my pay grade" as a deflection
⚠ Meeting-after-the-meeting is where real opinions surface

Leader Behaviours

Psychological safety is primarily set by leader behaviour — not by team-building activities or stated values. These are the specific, observable behaviours that build it.

Team Practices

Retrospective practices that build safety:
→ Anonymous pre-work before discussion (equalises voice)
→ Separate data gathering from interpretation ("What happened?"
   before "Why did it happen?")
→ "What I appreciated about this sprint..." as a warm-up
→ Rotate facilitation (reduces dominance by one voice)
→ What's said in the retro stays in the retro (make it explicit)

Meeting practices:
→ Call on quiet voices: "We haven't heard from [name] yet"
→ "Yes, and..." before redirecting
→ Last-person-to-speak rule: senior-most person speaks last
→ Share meeting agenda in advance; give people time to prepare

Hiring and onboarding:
→ Share norms explicitly: "Here, we say 'I don't know' freely"
→ New hire 30-day check-in: "Has anything surprised or confused you?"
→ Celebrate new joiners' challenges to existing practices

Blameless Culture

Blameless post-mortem format (for incidents and failures):
1. Timeline — what happened, in order, factually
2. Contributing factors — what system conditions made this possible?
3. Human factors — where did human judgement fail or succeed?
   (describe actions, not intent)
4. What went well — what prevented the situation from being worse?
5. Action items — what will we change in systems, process, or tooling?

Rules:
→ No names in the written post-mortem (except action owners)
→ "How could we have prevented this?" not "Who caused this?"
→ Published openly; accessible to the whole team
→ Actions tracked to completion

Blameless ≠ accountability-free:
Individuals are still responsible for their actions and their commitments.
Blameless means: we assume good intent, we look for systemic causes,
and we do not punish honest mistakes that surfaced an important truth.

Anti-Patterns

Psychological Safety Cheat Sheet

Definition
The belief that one will not be punished for speaking up
with ideas, questions, concerns, or mistakes.

Why it matters
→ #1 predictor of team effectiveness (Google Project Aristotle)
→ Generative culture predicts elite DORA metrics (DORA research)
→ Without it: hidden problems, slow learning, false consensus

Westrum cultures
Pathological  → power-oriented; information hidden; failure punished
Bureaucratic  → rule-oriented; failure leads to blame
Generative    → performance-oriented; failure leads to inquiry

4 Stages of safety (Clark)
1. Inclusion → 2. Learner → 3. Contributor → 4. Challenger

Measuring (Edmondson survey, 1–7 scale)
<4.5 → significant issues · 4.5–5.5 → moderate · >5.5 → healthy

Leader behaviours that build safety
→ Model vulnerability (admit your own mistakes openly)
→ Ask questions; listen to the answers
→ Reward candour publicly; thank people who surface problems
→ Protect dissenters; respond to bad news with curiosity
→ Follow through on every concern raised

Blameless postmortems
→ No names in written document
→ System causes, not human blame
→ Published openly; actions tracked