Psychological Safety
5 min read · 4 principles · apply it by lunch
Good morning. The highest-performing teams share one thing. It’s not talent.
Does your team tell you bad news fast — or do they wait until you find out yourself?
In 2012, Google ran Project Aristotle — a two-year study of 180 internal teams to find what made great teams great. They expected it to be about talent: the right mix of specialists, the sharpest individuals, the highest performers. It wasn’t. The single biggest differentiator was psychological safety — the shared belief that the team is safe for interpersonal risk-taking. Amy Edmondson, the Harvard professor whose 1999 paper defined it for teams, building on Edgar Schein and Warren Bennis (1965) and William Kahn (1990), defines it precisely: not comfort, not harmony, not the absence of conflict. It’s the belief that you won’t be punished for speaking up, admitting ignorance, challenging a decision, or flagging a mistake. Teams with high psychological safety make more errors in the data — because they report them. They move faster, learn faster, and recover faster. Teams without it make the same errors but hide them until the damage is done.
Psychological Safety is Day 6 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee