Psychological Safety: What Makes People Speak Up Is Not Kindness — It's Mechanism
Topic: Psychological Safety·4 Scenes
"Psychological safety is not about being nice." — Amy Edmondson
This week's thesis: Google's Project Aristotle studied 180 teams and found the #1 driver of team performance wasn't how smart the members were, but psychological safety—whether people dare to ask questions when unsure, admit mistakes, and disagree with the boss. But the term is badly misread: many managers treat it as "be nicer to everyone, don't criticize, keep the peace," and end up building a comfort zone where no one tells the truth. The opposite of psychological safety is not conflict—it's silence; and its twin is not low standards, but high ones. This week, four scenes: separating safety from "niceness / low bar," how a leader goes first by showing fallibility, how to engineer dissent instead of chanting "feel free to speak up," and how to see through "artificial harmony"—the most dangerous disguise of all.
SCENE 01
Safety ≠ Being Nice: It Pairs With High Standards, Not Against Them
Safety Is Not Softness — Pair It With High Standards
Clarify the conceptLearning ZoneHigh Standards
The Principle
Psychological safety is not lowering the bar, withholding criticism, or making everyone comfortable. It means "telling the truth won't get you punished"—which is exactly what lets you give feedback harder. Safety + high standards = Learning Zone; safety + low standards = a retirement home.
In Their Own Words
"Psychological safety is not a matter of relaxing standards, making people comfortable, being nice and agreeable, or giving unconditional praise. It is foremost about candor."— Amy Edmondson, The Fearless Organization, Ch.1
The Safety × Standards 2×2
Scene
Setup: Your team runs code review. A senior engineer leaves a blunt comment on a junior's PR. The junior comes to you and says "this makes me feel unsafe." You need to tell apart: is this breaking safety, or normal high-standard feedback?
✗ Treating safety as "can't be criticized"
To "protect safety," you privately tell the senior: "Go gentler on your comments from now on." —— You just swapped the standard for niceness. Code quality starts sliding, and the senior people learn to keep quiet too.
✓ Separate "standard on the work" from "attack on the person"
Look at the comment itself. "The null pointer isn't handled here; add a check, see X"—that's a high standard, and you protect it. To the junior: "Strict review is a sign of respect—it means people see you as someone who can grow. Safety isn't never being told you're wrong; it's not being humiliated for it, and it not changing how people see you. That comment targets the code, not you." Only when a comment becomes "You can't even do something this simple?"—personal, humiliating, public—do you step in, and fast.
Checklist: High Standard, or Unsafe?
Does the feedback target behavior/output, or the person (ability, character)?
Does it offer a path to improve, or only negation and public humiliation?
After it's raised, will this person's standing and trust in the team drop?
If a senior person made the same mistake, would we use the same tone?
Common Mistakes + A Note on Women Leaders
Downgrading safety into "nice-guy culture." No one criticizes—and the mediocre are most comfortable while the excellent are most frustrated.
Using "psychological safety" as a shield to dodge feedback. "I'm not saying it to protect their safety"—really you fear the hard conversation.
Doing half the job: pure pressure, or pure niceness. Both dimensions must be maxed out.
Female Leader's Note
Research shows marginalized groups have systematically lower psychological safety—the same challenge carries higher risk when voiced by women, minorities, or newcomers, and they're more likely to be interrupted or ignored. So "our team is super open" is often an illusion seen from the perspective of those who already feel safe. Don't ask "does everyone feel safe?"—ask, one-on-one, the person who speaks least.
This Week's Exercise + Question
Exercise: Honestly place your team in the 2×2. If you're in the "Comfort Zone," pick one thing you've been sitting on this week and give a real piece of feedback with a path to improve. Reflect: The last time you withheld feedback—was it to protect the other person's safety, or to spare yourself an awkward moment?
SCENE 02
You Go First: A Leader's Fallibility Is the Switch
Go First — Model Fallibility
Model itAdmit not knowingPower gap
The Principle
Safety is not declared, it's demonstrated. Reports are always watching: when the boss is wrong, do they own it; when they don't know, do they fake it? You admitting once "I was wrong / I don't know" beats a hundred rounds of "feel free to share opinions."
In Their Own Words
"To create psychological safety, leaders must demonstrate fallibility. Saying things like 'I may miss something — I need to hear from you' invites others to speak up."— Amy Edmondson, The Fearless Organization (Leader's Toolkit)
Scene
Setup: In an architecture review, the design you championed turns out to have a scalability problem you hadn't considered. The room watches how you react—this is a defining moment for the team's safety.
✗ Defensive / saving face
"There was no data to support that at the time—easy to say now." Or silently changing the subject. —— The signal the team receives: admitting limits is dangerous; even the boss won't own a mistake, so I certainly can't.
✓ Own it publicly, and turn it into a rule
"Good catch. I missed the scalability dimension—my design was wrong on that point. Thank you for raising it—precisely because someone dared to flag my blind spot in review, we didn't ship it to production." (Pause; set the rule) "From now on I want someone in every review whose job is to poke holes in the design. Whoever surfaces the problem gets credit, not blame."
Phrases for a Leader Who "Goes First"
Frame work as learning: "This is new territory, we'll all make mistakes—what matters is saying so fast."
Admit your limits: "I might miss things—I need you to watch my back."
Say what you don't know: "I don't understand this part—who can teach me?" (Most powerful from a senior leader.)
Thank the bearer of bad news: "Thanks for telling me early—the sooner I know, the more options we have."
Common Mistakes + A Note on Women Leaders
Saying, not doing. You "welcome disagreement," then shut down the first person who disagrees—no one opens their mouth again.
Performing vulnerability as branding. Reports can tell real ownership from "a little humility to seem relatable."
Backpedaling or deflecting right after. "I was wrong, but mostly because XX didn't give me the data"—the first half is wasted.
Female Leader's Note
There's a real asymmetry: when a man says "I don't know," it often reads as "candid"; when a woman says the same, it can read as "see, she isn't competent enough" (the likability-vs-competence double bind). A balanced move: tie the vulnerability to a clear next step—not "I'm not sure what to do either," but "I got this wrong; here's how we fix it." Admit fallibility while showing command, leaving no gap for the stereotype.
This Week's Exercise + Question
Exercise: In a meeting with reports present this week, say one genuine "I judged this wrong before" or "I don't understand this." Watch the next 5 minutes—does anyone speak up more freely as a result? Reflect: When did you last admit a mistake in front of the team? If you can't recall it, the team can't either—they're learning from you to stay quiet.
SCENE 03
Engineer Dissent: Not "Feel Free to Speak Up," but Mechanisms
Engineer Dissent — Mechanisms Over Invitations
Dissent mechanismsPre-mortemRed team
The Principle
"Raise issues anytime" is the most useless sentence—it leaves the full cost and risk of speaking on the employee. Safety isn't built by appeals, but by turning dissent into a mandatory step in the process: assign a contrarian, ask the most junior first, leave time for objection before deciding.
In Their Own Words
"Gentlemen, I take it we are all in complete agreement on the decision here. Then I propose we postpone further discussion until our next meeting to give ourselves time to develop disagreement and perhaps gain some understanding of what the decision is all about."— Alfred P. Sloan (General Motors), quoted in Peter Drucker, The Effective Executive, Ch.7
Scene
Setup: A review for an important technical decision. You've just finished presenting and the room nods: "sounds good," "agreed." You'll adjourn in ten minutes—and this "unanimous approval" is precisely the danger sign.
✗ Mistaking silence for consensus
"Well, no objections, so it's settled." —— You've misread "no one wants to bear the risk of objecting" as "the plan is perfect." The real hazards ferment afterward, by the water cooler.
✓ Force dissent with a mechanism
"Everyone agreeing actually makes me uneasy. Let's do a 5-minute pre-mortem: assume this plan failed completely six months from now—each of you write down the single most likely reason." (Or assign a role) "Li, this round you're the devil's advocate—your job is to find three ways this plan could collapse. It's an assigned task, not you being difficult." (Or reverse the order) "Let's start with the most junior; I'll go last."—so people don't anchor on the boss's view.
5 Mechanisms to Institutionalize Dissent (pick 1–2)
Pre-mortem: "Assume it already failed—why?" Disguise criticism as prediction; the barrier drops sharply.
Rotating devil's advocate: Assign one person to oppose—turning dissent from "personal offense" into "an assigned duty."
Most junior first: Speak bottom-up, boss last, to avoid power anchoring.
Anonymous input: Collect concerns on an anonymous form before deciding, bypassing the fear of speaking in person.
"What are we missing?": A fixed closing question—ten times better than "any questions?"
Common Mistakes + A Note on Women Leaders
Chanting slogans without mechanisms. "We're an open culture"—culture is the result; mechanism is the cause.
Going through the motions. You run a pre-mortem but follow up on none of the risks it surfaced—next time no one takes it seriously.
The boss declares first. One word from you sets the tone, and every later "dissent" is flattened by your power.
Female Leader's Note
"Open the floor" formats systematically favor the loud and the interrupters—often not women or introverts. Mechanizing is precisely a protection for marginalized voices: anonymous input, round-robin turns, and written pre-mortems replace "who dares grab the mic" with "everyone has a structured slot."
This Week's Exercise + Question
Exercise: At your next important decision meeting, run one pre-mortem or "most junior first." Afterward, count: of the risks the mechanism surfaced, how many would you never have heard otherwise? Reflect: Did your team's last "unanimously approved" decision later run into trouble? Did no one truly have concerns—or did no one dare voice them?
SCENE 04
See Through Artificial Harmony: No Conflict May Be the Worst Sign
Real Safety vs Artificial Harmony
Artificial harmonyDiagnose silenceLencioni
The Principle
A team that never argues is not high-trust—it's usually high-fear or already checked out. The product of safety is constructive conflict, not blanket harmony. Dead silence in meetings, complaints flooding the back channels afterward—that's "artificial harmony," the most dangerous disguise, because it looks like health.
In Their Own Words
"When team members do not openly debate and disagree about important ideas, they often turn to back-channel personal attacks, which are far nastier and more harmful than any heated argument over issues."— Patrick Lencioni, The Five Dysfunctions of a Team (Fear of Conflict)
Diagnose: Is Your "Harmony" Real Safety, or Fear in Disguise?
Scene
Setup: You take over a new team and within weeks notice retros are unusually "smooth"—everyone says "all good, no issues." But you hear that, privately, people have strong opinions about a certain process.
✗ Enjoying the "harmony"
"What a great team vibe—no infighting at all." —— You've mistaken fear/resignation for health, while the problem keeps rotting below the surface.
✓ Actively build a safe entry point for conflict
"I notice our retros are always smooth, but I don't believe a team that's truly pushing has zero friction. Let me change the question: not 'are there any issues,' but 'if you could change one process, which would it be?'—everyone must name one, including me." (The key is your reaction) "Thank you—that's exactly what I wanted to hear. The person who raised it pays no price; they did us a big favor."—use one real follow-through to turn "truth is safe" from slogan into evidence.
Checklist to Pry Open "Artificial Harmony"
Am I automatically taking "no one objected" as "everyone agreed"?
After someone risked the truth, was my first reaction to thank or to defend? (It decides whether anyone speaks next time.)
When was the team's last open, issue-focused argument? If you can't recall, that's the danger sign.
Common Mistakes + A Note on Women Leaders
Treating niceness as an achievement. "Our team never fights" is often a boast—really, no one is invested.
Reflexively defending against the first truth-teller. Once is enough to kill the whole mechanism.
Conflating constructive conflict with personal conflict and suppressing all of it. Encourage issue-focused argument; stop only personal attacks.
This Week's Exercise + Question
Exercise: In one meeting this week, replace "any questions?" with "each person name one thing we should change—starting with you, I'll go last." Force output; leave no seat for silence. Reflect: Is your team's "harmony" because people trust each other to withstand disagreement, or because no one thinks speaking up is useful or safe? The two look identical; the cost is worlds apart.
This Week's Exercise · Your Day 21 Action
This week, do one concrete thing—not reflection, not reading:
Pick one team meeting already on your calendar (a review, retro, or regular sync) and do two things:
(1) You go first with vulnerability—say one genuine "I judged X wrong earlier" or "I don't understand this part." (2) Replace "any questions?" with a forcing mechanism—a pre-mortem, or "most junior first, I'll go last."
Afterward, write two lines: Did anyone say something you'd never have heard otherwise? Was your first reaction to thank or to defend?—Your reaction decides whether anyone dares speak next week.
Going Deeper
Can psychological safety be abused into "I get to say anything and bear no consequence for being wrong"? Where's the line?
Safety protects "taking the risk to tell the truth in good faith"—not absolving responsibility or tolerating low-quality output. Edmondson stresses it pairs with high accountability: you can safely admit "I fell short," but you're still answerable for the result. The key distinction—it protects the right to speak, not freedom from the consequences of outcomes. Someone using "this makes me feel unsafe" to dodge legitimate feedback is abusing it.
Do East Asian workplace traditions—"face," deference to seniors, "harmony above all"—fundamentally conflict with psychological safety?
Not a conflict, but it demands a different play. In high-power-distance, face-conscious cultures, publicly opposing the boss is very costly, so "open the floor" is nearly doomed—which is exactly why this issue stresses mechanisms over appeals: anonymous input, written pre-mortems, private one-on-one solicitation all bypass the face risk of challenging authority in public. You can't change the culture, but process can pave a low-risk road for the truth.
In a big company, can a single tech lead manager build "local safety" inside their team within an overall unsafe environment? And how to measure it?
Yes, but with a ceiling and fragility. Within your team you can create a relatively safe microclimate through modeling, mechanisms, and kept promises—real for retention and output. But when the company has stack ranking, political blame, and constant layoffs, your local safety can be pierced any moment by a cross-org event. On measurement, don't rely on "employee satisfaction" (satisfaction may be the comfort-zone niceness); more behavioral signals are the speed of escalating bad news, how often juniors challenge seniors, and how many own mistakes in postmortems.