Engineering Culture Starts with Psychological Safety

I have managed teams that were technically brilliant but underperformed. I have also managed teams with average talent that consistently exceeded expectations. The difference was never skill. It was always culture. And culture starts with psychological safety.

What Psychological Safety Actually Means

It does not mean being nice. It does not mean avoiding conflict. It means creating an environment where team members can raise concerns, admit mistakes, and challenge ideas without fear of punishment or embarrassment.

Google's Project Aristotle studied 180 teams and found that psychological safety was the single strongest predictor of team effectiveness. Not expertise, not process, not tools. Safety.

How I Build It

Three practices that have worked for me across multiple teams.

First, I normalize failure publicly. When something goes wrong in production, my first question is never "who did this." It is "what can we learn from this." I run blameless postmortems and hold myself to the same standard. When I make a wrong call — and I do, regularly — I own it in front of the team.

Second, I create explicit space for dissent. In every planning session, I ask "what could go wrong with this plan" before we commit. I call on quieter team members by name. Silence is not agreement — it is often suppressed disagreement.

Third, I protect the team from organizational pressure. When leadership pushes for unrealistic deadlines, I push back. My team needs to know that I will not sacrifice their well-being for optics. That trust takes months to build and seconds to destroy.

The Results

Teams with high psychological safety ship better code. They catch defects earlier because people are not afraid to say "I think this design has a flaw." They onboard faster because newcomers feel safe asking questions. They retain talent because people stay where they feel valued.

If you are a PM or engineering leader and you are not actively cultivating psychological safety, you are leaving performance on the table. It is not a soft skill. It is a delivery multiplier.