What Psychological Safety Actually Means for Engineering Teams
I’ll be honest – when I hear “psychological safety” come up in a meeting, my first instinct is to brace myself for buzzword bingo. It gets thrown into decks and retrospective guides and manager training programs so often that it starts to sound like wallpaper.
But here’s the thing. I’ve also lived what happens when it’s missing. And it’s not abstract at all.
The team where I learned to say nothing
Mid-point in my career I worked on a team where the engineering manager and the director were close friends. Like, actually close – the kind where they’d grab coffee, chat in the hallway, pop into each other’s offices. Which sounds fine, until things that got shared in those conversations started showing up in one-on-ones and performance reviews.
It didn’t take long to figure out what was happening. And once I figured it out, I did what any rational person would do: I stopped sharing anything real with either of them.
Not because I was trying to be difficult. Because I had learned, pretty quickly, that being honest came with a cost.
That’s psychological safety – or the absence of it. Not a dramatic blowup or an obvious toxic culture. Just a quiet, rational decision by a smart person to keep their mouth shut. Repeated across a whole team, across months and months, until the manager genuinely has no idea what’s actually happening.
And the thing is – it showed up everywhere. In planning meetings where nobody questioned the timeline. In retrospectives where the real problems didn’t make it onto the board. In one-on-ones where everything was “pretty good, pretty busy.” In code reviews that got approved without real scrutiny because nobody wanted to be the one to slow things down.
The work suffered. The team suffered. And from the outside, things looked fine.
So what does it actually mean?
Here’s the definition I keep coming back to: psychological safety is the belief that you won’t be punished or humiliated for speaking up – with ideas, questions, concerns, or mistakes.
That’s it. It’s not about being nice to each other. It’s not about avoiding hard conversations. It’s about whether people on your team believe it is safe to tell the truth.
Google’s Project Aristotle studied hundreds of teams over several years trying to figure out what made them effective. They looked at everything – individual talent, team composition, management style. The single biggest predictor of team performance wasn’t any of those things. It was psychological safety.
Teams where people felt safe to speak up shipped better software, handled incidents better, and kept their people longer. Teams without it looked fine on the surface right up until they didn’t.
This isn’t buzzword bingo. It’s one of the most well-researched predictors of team performance we have. And most engineering teams have no systematic way to measure it.
What low psychological safety actually looks like day to day
It’s rarely obvious. It shows up in small moments.
The engineer who starts to raise a concern in planning and then says “never mind, it’s probably fine.” The PR that gets approved in twenty minutes with no comments because nobody wants to push back on the tech lead. The postmortem that’s two paragraphs long because people aren’t comfortable writing down what actually happened. The one-on-one where everything is “pretty good” every single week.
And here’s the one I’ve seen most often: concerns surface late. The first time a leader hears about a problem is in the postmortem, or worse, in an exit interview. It wasn’t a sudden problem. It was a problem someone decided not to surface – because surfacing problems on that team didn’t feel safe.
Why it shows up in your delivery data
This is the part most leaders miss. Psychological safety isn’t just a people metric. It’s a delivery metric.
When engineers don’t feel safe raising concerns, concerns don’t get raised. PRs sit in review longer because nobody wants to be the one to flag a problem. Tickets stay blocked because escalating feels risky. Estimates get sandbagged because nobody feels safe giving an honest number.
Every one of those things shows up in your cycle time, your PR review lag, your milestone slippage. The delivery data is telling you something is wrong. What it can’t tell you is whether the slowdown is a process problem or a safety problem.
That’s a big part of why we built CrewPulse the way we did. The anonymous check-ins aren’t just a privacy feature – they’re a psychological safety feature. Engineers answer honestly when they know their responses are summarized into themes, not surfaced verbatim to their manager. When someone flags that they feel blocked or that priorities are unclear, that signal gets to the right person without anyone having to put their name on it.
The delivery signals tell you what’s slipping. The team health signals tell you why. When both are trending in the wrong direction at the same time, you’re usually not looking at a process problem.
A few things that actually help
Psychological safety isn’t built at an offsite. It’s built in small moments, over time.
Model honesty yourself. Admit when you don’t know something. Share a mistake you made. Ask for feedback on a real decision and genuinely engage with what you hear. Leaders set the ceiling for how much honesty is acceptable on their team.
Pay attention to what happens when someone speaks up. The moment someone raises a concern and gets dismissed, interrupted, or visibly ignored – everyone in the room learns something. Make sure what they’re learning is the right thing.
Create low-stakes ways for people to be honest. Anonymous check-ins, pulse surveys, skip-levels – anything that gives people a way to signal how they’re actually doing without having to publicly raise their hand. The goal isn’t to replace direct conversation. It’s to make sure you have enough signal to know when one is needed.
Follow through on what you hear. Nothing kills psychological safety faster than a leader who asks for honest input and then does nothing with it. If something gets raised and nothing changes, say why. Silence reads as “this didn’t matter.”
The bottom line
I spent a year on that team – and I couldn’t get out fast enough. But it shaped how I think about leadership more than almost anything else.
Psychological safety isn’t a buzzword. It’s the condition under which honest information flows in your team. And honest information is what lets you catch problems early, make good decisions, and keep your best people from quietly deciding to go somewhere else.
The quiet in the room isn’t always agreement. Sometimes it’s just people who’ve learned it’s safer to stay quiet.
CrewPulse combines anonymous team health check-ins with delivery signals from GitHub and Jira, so engineering leaders can see what’s slipping and why. Get early access here.