Psychological Safety

The Key Condition for Building High-Performing Teams

1. Overview: A Shared Belief That the Team Can Speak Up and Experiment Freely Without Interpersonal Risk

    flowchart LR
    A["A culture of silence<br/>Perceived risk in speaking up<br/>Ideas suppressed<br/>Mistakes hidden"] --"Building<br/>psychological safety"--> B["Free expression<br/>Experimentation/mistakes allowed<br/>Candid feedback"] --"Accelerated<br/>learning and innovation"--> C["High-performing team<br/>A culture of organizational learning"]

    style A fill:#FFEBEE,stroke:#D32F2F,color:#000
    style B fill:#E3F2FD,stroke:#1976D2,color:#000
    style C fill:#E8F5E9,stroke:#388E3C,color:#000

Definition: A concept introduced by Professor Amy Edmondson (Harvard Business School): the shared belief among team members that they can ask questions, propose ideas, raise concerns, and admit mistakes without interpersonal risk. Google’s Project Aristotle research identified it as the single most important factor in high-performing teams.

Characteristics: (A high-standard, safe environment) Psychological safety is not comfort — the goal is a safe environment within high standards, not low standards or low accountability. (Leadership impact) Leadership behavior has the greatest influence on a team’s level of psychological safety. (Project Aristotle) In Google’s Project Aristotle, psychological safety ranked #1 among the 5 factors that determine team effectiveness (followed by dependability, structure & clarity, meaning, and impact).

2. Core Components of Psychological Safety

A. The Four Stages of Psychological Safety (Timothy Clark’s Model)

    flowchart LR
    S1["Stage 1<br/>Inclusion Safety<br/>Inclusion Safety<br/>Accepted for<br/>who you are"]
    S2["Stage 2<br/>Learner Safety<br/>Learner Safety<br/>Questions, mistakes,<br/>experimentation allowed"]
    S3["Stage 3<br/>Contributor Safety<br/>Contributor Safety<br/>Recognized for<br/>ability and value added"]
    S4["Stage 4<br/>Challenger Safety<br/>Challenger Safety<br/>Free to question the<br/>status quo, propose change"]

    S1 --> S2 --> S3 --> S4

    style S1 fill:#E3F2FD,stroke:#1976D2,color:#000
    style S2 fill:#FFF3E0,stroke:#F57C00,color:#000
    style S3 fill:#F3E5F5,stroke:#7B1FA2,color:#000
    style S4 fill:#1E3A5F,stroke:#1E3A5F,color:#fff

Stage	Core Question	What a Team Member Feels	Leader Behavior
1. Inclusion Safety	“Do I belong here?”	Treated equally regardless of race, age, gender	Respect individuals, embrace diversity, express belonging
2. Learner Safety	“Is it safe to ask questions or make mistakes?”	Can ask what they don’t know without ridicule	Welcome questions, frame mistakes as learning opportunities
3. Contributor Safety	“Are my opinions and abilities recognized?”	Not dismissed when offering ideas	Recognize contribution, grant autonomy, delegate authority
4. Challenger Safety	“Is it safe to question the status quo?”	Can push back on leaders/processes	Actively welcome dissent, encourage critical thinking

B. Leadership Practices for Building High-Performing Teams

    flowchart TD
    subgraph R1["　"]
        direction LR
        L1["Modeling vulnerability<br/>The leader admits what they<br/>don't know first<br/>Openly shares mistakes"]
        L2["Curiosity-driven questions<br/>Inquiry, not judgment —<br/>Why did you think that?<br/>What are you concerned about?"]
    end
    subgraph R2["　"]
        direction LR
        L3["Blameless postmortems<br/>Focus root-cause analysis<br/>on systems, not people"]
        L4["Welcoming dissent<br/>Assign a devil's-advocate role,<br/>actively solicit<br/>different viewpoints"]
    end

    style L1 fill:#E3F2FD,stroke:#1976D2,color:#000
    style L2 fill:#F3E5F5,stroke:#7B1FA2,color:#000
    style L3 fill:#FFF3E0,stroke:#F57C00,color:#000
    style L4 fill:#E8F5E9,stroke:#388E3C,color:#000
    style R1 fill:none,stroke:none
    style R2 fill:none,stroke:none

Leader Behaviors That Undermine vs. Promote Psychological Safety

Category	Undermining Behavior	Promoting Behavior
Response to mistakes	Public reprimand, humiliation, assigning blame	Blameless analysis, reframing as a learning opportunity
Response to opinions	Immediate rebuttal, dismissal, ignoring	“That’s an interesting point, tell me more”
Running meetings	Leader speaks first, silence goes unaddressed	Lowest-rank speaks first, gather anonymous input
Handling failure	Stigmatizing failure, blocking promotion	Share what was learned from failure, encourage experimentation
Sharing information	Hoarding information, withholding what’s needed	Transparently share context/background, honor the right to know

Psychological Safety Assessment Survey (Summary of Edmondson’s 7 Items)

Item	Low → High Scale (1-7)
In this team, it’s safe to take a risk	1 ————————————— 7
It’s easy for team members to raise problems	1 ————————————— 7
My unique skills and talents are valued in this team	1 ————————————— 7
No one on this team would hold a mistake against me	1 ————————————— 7
No one on this team would reject people for being different	1 ————————————— 7

3. Expected Benefits and Practical Application of Psychological Safety

Category	Key Expected Benefit	Practical Application
Accelerated innovation	More creative problem-solving from freely proposed ideas	Run a judgment-free idea-collection session in sprint retros
Early warning	Risks and problems are surfaced immediately instead of hidden	Run postmortems without blame to establish a culture that prevents recurring incidents
Learning organization	Converting mistakes into a learning asset that builds organizational capability	Share failure cases as “lessons learned” in the team knowledge base
Talent retention	Teams with high psychological safety see lower turnover and higher engagement	Run a quarterly psychological-safety survey and act on the results

Dunbar's Number Dreyfus Model