I sat in a retrospective a few years back. The team had shipped a release which fell over in production for eleven hours. Eleven hours. Customers screaming, support drowning, three engineers awake all night.
The retro lasted twenty-two minutes. Everyone agreed the monitoring needed work. Everyone agreed we should add more tests. Nobody said the thing they all knew, which was this: the release went out because a director had promised a date to a customer and refused to move it.
I know they knew, because four of them told me separately over the following week.
The team scored 4.1 out of 5 on psychological safety.
Your safety score measures your comfort, not theirs
Here is what I think most leaders get wrong. They treat psychological safety as a program. Run a survey, get a number, put the number on a slide, move on.
Perceptyx benchmark data puts the average at 73% positive perceptions of psychological safety. Sounds fine. Then look at who is answering. Executives score 87%. Managers score 77%. Individual contributors score 69%. An eighteen point gap between the people who set the culture and the people who live in it.
Read it again. The higher you sit, the safer you feel. So the person most confident about the team speaking freely is the person the team is least likely to speak freely in front of.
Roughly one in three employees hold no positive perception of psychological safety at all. And a 2025 MyPerfectResume survey of 1,000 US employees found 74% adjust their communication at work to avoid conflict.
Three quarters of your people edit themselves before they speak to you.
Safety is the outcome. Honesty is the input.
Ruth Wooderson said something I keep coming back to: you want psychological safety, start with emotional honesty.
She is right, and the ordering matters. Safety is not something you install. It is what people feel after watching what happens to the first person who tells the truth. You do not declare it into existence. You earn it, one uncomfortable moment at a time.
Emotional honesty means naming the real thing in the room. Not oversharing. Not trauma-dumping on your team. Naming the state of play, including your part in it.
"I pushed the date because I did not want another awkward call with the customer, and you paid for it with your weekend."
One sentence like this does more for safety than a year of anonymous surveys. It tells the room three things: the truth is sayable here, seniority gives you no protection from being wrong, and the person with power went first.
Why engineering teams pay double for silence
In most functions, silence costs you a bad decision. In software, silence compounds.
The engineer who never says "this design will not scale" ships the design. The design becomes the foundation. The foundation becomes eighteen months of workarounds. The workarounds become the reason your delivery slowed down, which becomes the reason someone hires a consultant to explain why your delivery slowed down.
DORA has measured this for over a decade. Their research on generative organizational culture found psychological safety predicts three separate outcomes: software delivery performance, organizational performance, and productivity. Not one. Three.
The 2024 DORA report adds a finding which should sting. Unstable organizational priorities cause meaningful drops in productivity and big increases in burnout, and the effect resists mitigation. Strong leadership does not fix it. Good documentation does not fix it. The instability itself is the damage.
Which is a research-shaped way of saying: if your team is unable to tell you the roadmap keeps moving, the roadmap keeps moving.
Four things which look like safety and are not
I see the same substitutes everywhere. They share one feature: they cost the leader nothing.
"My door is always open"
Your open door puts the entire risk on the person walking through it. They have to decide the problem is big enough to justify the walk, and they have to be seen walking. You have outsourced the hard part.
The anonymous survey
Anonymity is what you use when honesty is dangerous. Running one is not evidence of safety. It is evidence you already know direct conversation would fail. Fine as a thermometer. Useless as a cure.
Skip-levels
Good idea, usually wasted. Most skip-levels are a senior leader asking "how's it going?" to someone doing rapid mental arithmetic about whether their answer gets back to their manager. Without first demonstrating what happens to bad news, you are collecting fiction.
The perks
The ping pong table, the wellbeing app, the mental health awareness week. None of it changes what happens when someone disagrees with you in front of six people. One moment like this sets the culture more than your entire benefits budget.
My own research found 99.5% of survey respondents said they have had one or more types of bad boss. Almost everyone walks into your team carrying evidence about speaking up getting punished. You are not starting from neutral. You are starting from behind, and the burden of proof is yours.
What emotional honesty looks like on Monday
None of this needs a budget. It needs you to go first, repeatedly, in public.
Say the uncomfortable thing about yourself before you ask for it. Start your next retro by naming one decision you got wrong last sprint, and the cost. Do not soften it with "we". Use "I".
React well in the moment. Someone will disagree with you in front of others this month. Everything turns on it. Thank them by name, on the spot, and say what you are going to do differently. Everyone watching updates their model of you in real time.
Ask questions with a real answer. "Any concerns?" gets you silence. "What is the most likely way this goes wrong?" gets you a list. "Where do you think I am wrong here?" gets you gold, if you are able to take it.
Close the loop out loud. Silence after feedback teaches people it went nowhere. When someone raises something, say what happened to it, even when the answer is "I heard you, we are doing it anyway, here is why".
Watch what happens to your messengers. Ron Westrum's model, the one DORA validated, draws the line right here. Pathological organizations shoot the messenger. Bureaucratic ones ignore them. Generative ones train them. Look at the last three people who brought you bad news. What happened to them? Your team already knows the answer.
The uncomfortable bit
Emotional honesty is harder than psychological safety, because you have nobody to delegate it to. You do not buy it as a platform. HR does not run it for you.
It requires you to be wrong in front of people who report to you, on purpose, more than once. It requires you to hear something which stings and respond with curiosity instead of defence, while everyone watches to see which one you pick.
Most leaders will not do it. Which is exactly why the ones who do get teams who tell them about the eleven-hour outage before it happens, rather than three weeks after, one quiet conversation at a time.
You do not have a safety problem. You have an honesty problem, and it starts with you.
So here is the question I would sit with. When was the last time you said something true and costly to your own team... and what did it cost you?