Companies spend real money making offices look like places people want to be. Foosball tables. Standing desks. Cold brew on tap. Dogs in the office. The works.
Then they're confused when their best engineers quit.
None of it is culture. Not one bit of it.
Culture is what happens when a junior developer stands up in a planning meeting and says, "I think we're building the wrong thing." Culture is whether the developer gets thanked for the honesty... or quietly removed from the distribution list for the next planning meeting.
This is the whole test.
The Question Reveals Everything
Lee Woollsey, who has spent years studying how organisations learn and perform, put it bluntly: culture isn't the ping pong table. It's whether you say "this process is dumb" and still get promoted.
I grew up in the US Army, where the stakes of silence are far higher than missing a sprint deadline. But the mechanism is the same. In units where soldiers felt safe flagging problems up the chain, those problems got fixed before they became crises. In units where people stayed quiet to avoid trouble, trouble had a way of finding everyone.
I've seen tech teams repeat the same pattern. The outcome is different. The dynamic is identical.
I've also worked in places where you said it and got shot. Where the unspoken rule was: surface problems and become the problem. Where people learned to smile, nod, and vent on Slack to their trusted inner circle.
Those organisations didn't fail because they lacked ping pong tables. They failed because they trained their best people to be silent. And silence is expensive.
What the Research Found
In 2015, Google ran an internal study called Project Aristotle to figure out why some teams crushed it and others didn't. They looked at everything: individual talent, experience, complementary skills. None of it reliably predicted team performance.
The number one factor? Psychological safety. Teams where people felt safe taking interpersonal risks... disagreeing, asking questions, admitting they didn't know something... consistently outperformed teams packed with brilliant people who were afraid to speak.
This built on work Amy Edmondson had done at Harvard Business School since 1999. One of her most counterintuitive findings: high-performing medical teams reported more errors than lower-performing ones. Not because they made more mistakes... because they felt safe enough to report them. The weaker teams were hiding their failures.
Think about it in a software context. Your team isn't making fewer mistakes. You're making the same mistakes. The question is whether you find out in sprint review or in production.
The APA's 2024 Work in America survey found 89% of workers in toxic workplaces also reported lower psychological safety. Workers with higher psychological safety reported greater satisfaction across every metric measured: manager relationships, coworker relationships, growth opportunities, and inclusion policies.
And data from HR Daily Advisor in early 2026 is sharp: only 36% of HR representatives say employees in their organisations feel safe expressing criticism. Yet MIT Sloan research shows teams building psychological safety skills see 25% revenue increases. And workers with low psychological safety are 2.15 times more likely to be actively looking for another job.
You're burning people out and chasing them off. The ping pong table isn't helping.
The Silence Tax
Here's how silence compounds.
An engineer spots a flaw in the architecture during planning. She's seen what happens when people push back... the last person who did got labeled "difficult." So she says nothing.
Three months later, the architectural flaw is in production and it takes six weeks to fix. The postmortem is full of "we should have caught this earlier." Nobody says the obvious: the team built a system punishing early warning.
A product manager notices a key feature nobody wants keeps getting prioritized because it's the CTO's pet project. He raises it once in a one-on-one and gets told to "trust the vision." He stops raising it. The feature ships. Nobody uses it.
The thing about the silence tax is you never see the invoice. You see the churn. You see the mediocre retrospectives. You see the features nobody wanted. You never connect those dots back to the meeting three months ago where someone kept their mouth shut.
Research on the cost of silence shows when employees stay quiet, organisations miss critical feedback preventing costly mistakes. When people feel unheard long enough, they stop trying... or they leave.
What Psychological Safety Is Not
Psychological safety doesn't mean everyone feels comfortable all the time. It doesn't mean no accountability. It doesn't mean your team sits around validating each other's ideas.
Edmondson is clear on this: it's about taking interpersonal risks without fear of punishment. You disagree, you admit a mistake, you ask the obvious question. And you don't lose your job or your reputation for doing it.
This is different from feeling happy. Some of the most psychologically safe environments I've been in were also the most demanding. The difference is the challenge came through honest feedback... not through fear of saying the wrong thing.
What It Takes to Build It
Psychological safety doesn't come from a wellness Wednesday email or a Slack channel called #good-vibes. It comes from leaders who do two specific things consistently.
First, they model the behavior they want. They say "I was wrong about it" in public. They ask "what am I missing?" in meetings and wait for an honest answer. They say "I don't know" without qualifying for five minutes first. When the leader is visibly human, it gives everyone else permission to be.
Second, they respond to honesty without punishing it. This is harder than it sounds. Honest feedback is uncomfortable. Someone tells you the process is broken. Your first instinct is defensive. You want to explain why it's not broken. The leaders building psychological safety resist this instinct and ask a follow-up question instead.
At Step It Up HR, the pattern is consistent: leaders who reward honest feedback get more of it. Not because people suddenly become braver, but because the risk calculus changes. Speaking up used to cost something. Now it doesn't.
Start Here
If you want to build psychological safety in your team, three things work consistently.
Ask "what am I missing?" at the start of every major decision. Not as a formality. Ask it and wait. Let the silence sit for five seconds. People will fill it. At first they'll say "nothing" or offer something small. Keep asking. Over months, they'll learn you genuinely want to hear.
Thank the bearer of bad news. Every time someone brings you a problem, your response sets the next person's expectations. "Thanks for flagging this, let's fix it" builds safety. "Why didn't you tell me sooner?" destroys it. Pick your response deliberately.
Admit a mistake publicly. Not as self-flagellation. As permission-granting. Say "I got this wrong, here's what I'd do differently" in a team meeting. Watch what happens. People start doing the same. Not immediately, but over months.
None of this requires a budget. None of it requires HR approval. It requires deciding safety is your job, not someone else's.
The Perks Illusion
The reason ping pong tables persist is they're visible. You photograph them for your careers page. They say "we're fun, we're modern, we care."
Psychological safety is invisible. You build it in the moment after someone tells you something you don't want to hear, and you thank them for it. You build it in the meeting where the most junior person asks the most obvious question... and instead of the room going quiet, someone says "great question."
A 2026 report put it directly: the perks era is over. Employees don't want table tennis at 3pm. They want to feel seen, trusted, and useful.
High-trust cultures outperform their peers by over 40% in innovation. Not because they hired smarter people. Because they stopped punishing the smart ones they already had.
The Test
Forget the ping pong table. Ask yourself this:
What's the last piece of bad news someone brought you... something you genuinely didn't know? Not a problem you'd already spotted. Something your team knew and you didn't, and they were brave enough to bring forward.
If you're struggling to think of an example, silence is your data.
The teams winning aren't the ones with the best perks. They're the ones where someone says "this is broken" on a Thursday afternoon, and by Friday morning, it's been addressed... and the person who raised it is quietly glad they did.
Build it. The ping pong table is optional.