Module Catalog →
Module Catalog →
Psychological safety is not about being nice. It's about giving candid feedback, openly admitting mistakes, and learning from each other.
Amy Edmondson did not set out to discover psychological safety. As a doctoral student in the mid-1990s, she studied medication errors in hospital teams, expecting to find that the best teams made the fewest mistakes. The data said the opposite: the better teams appeared to make more errors. The resolution of that puzzle became her life's work — the best teams didn't make more mistakes, they reported more, because they felt safe enough to do so.
Before academia, Edmondson worked as chief engineer for Buckminster Fuller, an apprenticeship in systems thinking she still credits. She has ranked #1 on the Thinkers50 global list of management thinkers (2021 and 2023), and her 2023 book Right Kind of Wrong won the Financial Times Business Book of the Year.
Her career traces a single arc: from how teams learn, to what makes learning possible (safety), to what learning is ultimately for — failing well in pursuit of the new.
Two things make the idea powerful. First, it is a team-level property — climates differ team to team inside the same company, which means leaders create it locally, every day. Second, it is the gateway condition for everything else Open Sky teaches: sensemaking, safe-to-fail experiments, and candid dialogue all require people willing to say what they actually see.
Google's Project Aristotle later tested dozens of variables across hundreds of teams and found psychological safety to be the single strongest predictor of team effectiveness — a large-scale confirmation of Edmondson's 1999 finding.
Four plates, one arc: from team learning to failing well.
Psychological safety is routinely misread as niceness or protection from discomfort. Edmondson pairs it with high standards: safety plus accountability creates the learning zone; safety without standards produces only comfort, and standards without safety produce anxiety and silence.
Silence is safe for the individual and costly for the organization: the benefit of voice is often delayed and collective, while its risk is immediate and personal. No one was ever fired for silence — which is exactly why leaders must actively invite voice rather than assume it.
Basic failures are preventable slips in known territory. Complex failures arise when multiple factors align in systems. Intelligent failures are the undesired results of thoughtful experiments in genuinely new territory — the only kind worth celebrating, and the engine of discovery.
Modern work rarely offers stable, bounded teams. Teaming is the dynamic skill of coordinating and learning with whoever the work requires — across disciplines, time zones, and organizations — with psychological safety as its precondition.
The leader's toolkit, from The Fearless Organization.
Frame the work as learning. Name the uncertainty and interdependence out loud: "We've never done this before; I need every observation." Framing sets whether errors are shameful or informative.
Acknowledge your own fallibility. "I may miss things — I need to hear from you" gives others permission to be imperfect and candid. Situational humility is the leader's entry fee.
Ask good questions — and mean them. Proactive inquiry ("What are you seeing? What's the other side of this?") converts an invitation to speak from theory into experience.
Respond productively. The moment someone brings bad news is the whole game. Appreciate first, destigmatize the failure, then address what must change. One punished messenger buys years of silence.
Distinguish failure types before reacting. Sanction sabotage and repeated basic failure if needed — but celebrate intelligent failure visibly, or no one will run the experiments your strategy depends on.
Where Edmondson's work lives inside Open Sky.