Psychological safety is one of the most misread ideas in engineering leadership. Some managers hear it as permission to avoid hard conversations. Others treat it as a line in the values deck with nothing behind it. Both readings make it sound soft.
The term comes from Amy Edmondson, who defined it in a 1999 study of work teams as a shared belief that the team is safe for interpersonal risk-taking. The risks in question are the ordinary, uncomfortable things good engineering depends on: saying you're stuck, telling a senior engineer their design has a hole in it, admitting the date won't hold. On a team where those are safe, problems surface while they're still cheap to fix. Where they aren't, people stay quiet and the problems surface in production.
Safety and standards are separate axes
Edmondson's later book, The Fearless Organization (2018), sets out a grid with psychological safety on one axis and performance standards on the other.
- Low safety, low standards: apathy. People turn up and do the minimum.
- Low safety, high standards: anxiety. People are pushed hard and afraid to say when something is wrong, so failures stay hidden until they can't be.
- High safety, low standards: comfort. Pleasant, and not much gets built.
- High safety, high standards: the learning zone, where teams do their best work.
The useful claim is that the two axes are independent. Managers often treat them as a trade, as if raising one must lower the other. Ease the bar to make people comfortable and you land in the comfort zone. Tighten it at the cost of candour and you get a team that has stopped telling you things. The job is to raise both.
Built in small moments
A team doesn't become safe because its manager said so at an all-hands. People learn what is safe from how you react when someone takes a risk, and those moments are small and easy to miss.
Say Tom, a mid-level engineer, admits in Tuesday's standup that he doesn't understand how the billing service retries failed payments. A raised eyebrow tells the room that not knowing is embarrassing. "Fair question. Ana wrote most of that; can you two pair on it this afternoon?" tells them it's normal. When someone ships a bug, asking how it got past review invites a better process, and asking how they let it happen invites hiding. When a junior engineer challenges your design in a review, engage with the argument in front of everyone, whether they turn out to be wrong or right.
People watch these reactions closely. One public put-down teaches the whole team to keep its head down, and it takes many ordinary, decent responses to undo it.
High standards are a form of respect
Lowering the bar for someone tells them you don't think they can clear it. Kim Scott's Radical Candor (2017) describes the combination that works as caring personally while challenging directly. Her name for the failure on the soft side, ruinous empathy, fits a lot of well-meant management.
In practice that means feedback that is honest and specific, sending back work you know the person can improve, and saying in advance what good looks like. None of it costs safety, provided the person can tell you're holding them to the standard because you think they can meet it. Safety suffers when the standard was never stated and the criticism arrives anyway, because then it feels personal.
Coaching instead of rescuing
The other half of culture work is developing judgment in other people. Managers who were strong engineers have a particular instinct to rescue: someone struggles, and the manager supplies the answer. It feels helpful and it's quick. Done often enough, it teaches the team to wait for you.
Coaching means asking before telling ("what options have you looked at?") and letting someone reach a sound decision by a slower route than yours. Watching that is uncomfortable, and it's the price of a team that grows more capable than its manager. There are limits. In an incident, with someone brand new to a task, or when a wrong call lands on customers, direct, and say that's what you're doing so it stays the exception.
Where this sits in the standard
Culture & Coaching is one of the five domains of the EMA Competency Framework. The CC-1 unit of the Body of Knowledge covers psychological safety and productive conflict, including Edmondson's work and Google's internal study of team effectiveness. CC-2 covers when to coach and when to direct.