Psychological safety

Psychological safety (Amy Edmondson's term) is the shared belief that you can take interpersonal risks — ask a "dumb" question, admit a mistake, challenge a plan — without being punished or humiliated. It is not "being nice" and it is not low standards. High-performing teams pair safety with high accountability: people speak up and own outcomes.

You do not need a manager title to move this. Daily behavior teaches the team whether honesty is rewarded.

The big idea

A lab where people hide broken equipment until the inspection is unsafe. A lab where people flag a crack immediately, and still own the repair, is safe and strict. Engineering is the same: silence until production is the expensive path.

The analogy breaks if "safety" is used to dodge hard feedback. Safety is the condition that makes hard feedback usable. Harshness without safety just trains people to hide.

Walking through it

Contribute without a title:

• Thank people for bad news early. "Thanks for flagging the risk" teaches that silence is riskier than honesty.
• Leave space in meetings. Ask the quiet person after the loud debate, or collect async comments before deciding.
• Credit accurately. Name who did the work in demos and docs. Misattribution destroys safety faster than harsh code review.
• Avoid sneer culture. Sarcasm about "obvious" questions trains juniors to hide confusion until production.
• Inclusive defaults. Share notes, record when possible, avoid exclusory slang as a status test, and schedule across time zones with fairness.

Safety is how code review stays educational instead of adversarial, and how disagreement stays about the work.

Edmondson's usual leader behaviors, useful even if you are not the manager: set the frame ("we will miss things"), invite input specifically, and respond productively when someone takes a risk — including when the news is inconvenient.

Common mistakes

• Safety as niceness. Avoiding a hard review so nobody feels bad. Accountability is the other half.
• Sneer at questions. You trained the next incident to stay hidden.
• Stolen credit. The demo names you; the work was theirs. People stop bringing you the work.

Check yourself

1. A junior flags a launch risk in the last meeting. What do you say first?

Thank them for the flag, then examine the risk. That teaches early bad news is welcome.

2. How is psychological safety different from low standards?

Safety is permission to speak and miss in the open. High-performing teams still own outcomes; they do not hide misses to look competent.

Key takeaways

• Safety plus accountability: people speak up and still own results.
• Thank early bad news, credit accurately, and leave space for the quiet person.
• Sneer culture and misattribution teach people to hide until production.

Further learning

Amy Edmondson on what psychological safety is (and is not):

Back to the map: collaboration and disagreement.