Library→Third Way: Continual Learning→Psychological Safety
Psychological Safety
The foundation of learning teams. Amy Edmondson's research, Google's Project Aristotle, and the Westrum culture model — why feeling safe to speak up predicts team performance.
Video Lesson
A video lesson for this topic is in development. The library articles and mission exercises cover the same material in the meantime.
What is psychological safety?
Amy Edmondson defines psychological safety as "a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes." It is a shared belief held by members of a team — not a personality trait and not the same as being comfortable or conflict-free.
Psychological safety is specifically about interpersonal risk. Will my colleagues think I'm incompetent if I admit I don't understand? Will I be blamed if I report a near-miss? Will my concern about the deadline be dismissed? When the answer to these questions is "probably yes," people stop speaking up — and problems accumulate silently.
Psychological safety does not mean everyone agrees, or that the team never has conflict. It means team members feel safe enough to engage in the productive conflict that leads to good decisions.
Google Project Aristotle
In 2012, Google launched Project Aristotle: a multi-year study of 180 teams to answer the question "What makes a Google team effective?" The researchers expected to find that the best teams were composed of the most talented individuals.
They did not. The composition of the team — who was on it — was less predictive of performance than how the team worked together. The single strongest predictor of team effectiveness was psychological safety.
Psychological safety
Can we take risks on this team without feeling insecure or embarrassed?
Dependability
Can we count on each other to do high quality work on time?
Structure and clarity
Are goals, roles, and execution plans clear?
Meaning
Are we working on something that is personally important?
Impact
Do we fundamentally believe that the work we're doing matters?
Psychological safety in DevOps
In DevOps, psychological safety manifests in specific and measurable ways. DORA's research identifies it as a key predictor of software delivery performance — not because it feels good, but because it enables the specific behaviors that drive improvement.
Reporting near-misses
Without safety
Engineers notice a problem about to happen and say nothing, fearing blame for raising it.
With safety
Engineers surface potential problems early, allowing the team to prevent incidents.
Honest incident reviews
Without safety
The post-mortem timeline omits the engineer's role. Root causes stay buried.
With safety
The full sequence of events is documented. Contributing factors are found and fixed.
Questioning decisions
Without safety
Engineers implement decisions they believe are wrong rather than risk conflict.
With safety
Disagreements surface in planning, not in production incidents.
Admitting skill gaps
Without safety
Engineers make guesses rather than ask questions, fearing they will look incompetent.
With safety
Knowledge gaps are surfaced and addressed through pairing, documentation, or training.
Westrum organizational culture model
Ron Westrum, a sociologist who studied organizational safety in high-risk industries (aviation, healthcare, nuclear), developed a model describing how organizations handle information. DORA adopted Westrum's model and found it to be a key predictor of software delivery performance.
Pathological
·Power-oriented
·Information hoarded
·Messengers shot
·Failure leads to scapegoating
·Novelty crushed
Bureaucratic
·Rule-oriented
·Information neglected
·Messengers tolerated
·Failure leads to justice
·Novelty causes problems
Generative
·Performance-oriented
·Information actively sought
·Messengers trained
·Failure leads to inquiry
·Novelty implemented
Generative organizations — those where information flows freely and failures lead to inquiry rather than blame — outperform bureaucratic and pathological ones on every DORA metric. The culture model is not soft: it predicts deployment frequency, change failure rate, and MTTR.
How to build psychological safety
Psychological safety is created primarily by leader behavior. Amy Edmondson identifies three things leaders do to create it:
Frame work as a learning problem
Explicitly acknowledge uncertainty. "We've never done this before and will need everyone's best thinking." This gives people permission to not know the answer and to ask questions.
Acknowledge your own fallibility
Leaders who admit mistakes signal that it is safe for others to admit mistakes. "I was wrong about that" is one of the most powerful sentences a manager can say.
Model curiosity and ask genuine questions
Ask questions you don't know the answer to. Respond to bad news with curiosity rather than alarm. Reward speaking up, not just the content of what was said.
Further reading
The Fearless Organization — Amy Edmondson
The definitive book on psychological safety in organizations. Research, case studies, and practical guidance for leaders.
Google Project Aristotle
re:Work.withgoogle.com. The full research summary. What Google found about what makes teams effective — and the primacy of psychological safety.
DevOps Handbook — Chapter 27
Create a Learning-Oriented Culture with Blameless Post-Mortems. The Westrum culture model and its link to delivery performance.
Accelerate — Chapter 11
Leaders and Managers. The DORA research on how management practices and organizational culture predict software delivery performance.