Somewhere along the way, "psychological safety" got translated as "be nice." Don't push back in meetings. Soften every piece of feedback until it's unrecognizable. Avoid disagreement because disagreement feels unsafe.
This is almost exactly backwards.
When Google's Project Aristotle studied what made their best teams work, psychological safety came out as the single biggest factor. But look closely at what the research actually measured: it was the belief that you can take interpersonal risks — ask a naive question, admit a mistake, challenge the consensus — without being punished or humiliated.
Psychological safety isn't the absence of conflict. It's the absence of fear about what conflict will cost you.
The Nice-Team Trap
Teams that confuse safety with niceness develop a distinctive pathology: artificial harmony. Meetings are pleasant and aligned. Then the real conversation happens afterwards — in direct messages, in hallways, in the parking lot. Decisions get re-litigated in private because they were never honestly debated in public.
Here's the test: the most psychologically safe teams argue more in the room, not less. They argue better, too — about ideas rather than people, with the assumption that everyone at the table is competent and well-intentioned.
A quick diagnostic: In your last five team meetings, how many times did someone openly disagree with the most senior person in the room? If the answer is zero, you don't have harmony. You have silence.
Amy Edmondson — the researcher behind the concept — on what psychological safety actually means.
What Actually Builds Safety
1. Leaders go first
Safety is built by what leaders model, not what they announce. Say "I was wrong about that" in front of your team. Ask a question you suspect is basic. Share a half-formed idea and invite people to tear it apart. Every act of visible fallibility lowers the cost of fallibility for everyone else.
2. Respond well to bad news — every single time
Your team is constantly running an experiment on you: what happens when someone brings this person a problem? If the answer is ever shooting the messenger, the experiment ends and the information stops flowing. You won't know it stopped. That's the dangerous part.
3. Separate the idea from the person
High-performing teams develop rituals that depersonalize debate: red-team exercises, pre-mortems, assigned devil's advocates. When challenging an idea is somebody's explicit job, challenging ideas stops feeling like an attack.
4. Keep standards high
This is the part the "be nice" crowd misses. Psychological safety without high standards produces a comfort zone, not a learning zone. The goal is the combination: a team where expectations are demanding and it's safe to struggle visibly while meeting them. Safety isn't a substitute for accountability — it's what makes real accountability possible.
The Payoff
Teams with genuine psychological safety surface problems earlier, learn from failures faster, and make better decisions because dissent reaches the table before the decision is final.
None of that comes from being nice. It comes from being honest in an environment built to survive honesty.
Build that environment. The niceness can take care of itself.