Why psychological safety isn’t a ‘nice to have’

Psychological safety has a strange reputation in projects. Most people agree it matters. They’ll nod when it comes up. Some will say it’s something they value. But then it often gets parked as a cultural ‘nice-to-have’ – something that sits alongside wellbeing initiatives rather than alongside risk management, assurance or decision making. In my experience, that’s a mistake.

The projects I’ve seen struggle rarely fail because people don’t care or don’t know what they’re doing. They struggle because the environment makes it harder to say the uncomfortable things early enough – the doubts, the risks, that gut feeling that something isn’t quite right.

Your team wants to be honest

This isn’t because people are dishonest. It’s because they’re careful about what they say and to whom. People learn quickly what feels safe to say in a project and what doesn’t. They learn which questions are welcomed, which earn awkward silences, which concerns get explored and which get brushed off with a ‘Let’s take that offline’.

Over time, teams’ behaviour shifts. Language softens. Concerns are held back until there’s more certainty, or more cover. What starts as caution slowly becomes habit. Silence doesn’t mean alignment. It usually means risk.

No one wants a watermelon

By the time information reaches a report, it has already travelled through layers of judgement and self-censorship. If challenge doesn’t feel safe lower down, what surfaces at the top is only part of the picture. That’s how projects end up looking green on the outside while quietly turning red underneath, often surprising the very people who are meant to have oversight.

This is the watermelon effect. It is often described as a reporting problem when it isn’t. Most reporting frameworks do exactly what they were designed to do. The issue is upstream. Psychological safety determines what information moves early, what gets delayed and what never makes it into the room at all.

That’s why I struggle when psychological safety is framed as a soft skill. In practice, it has very real consequences. It affects decision quality, how early risks surface and whether governance genuinely helps teams navigate complexity or simply reassures people that things are under control.

Don’t make honesty selective

I’ve sat in many meetings where everyone knew the risks and no one named them – not because people didn’t care, but because raising them felt political or personal. In those environments, reassurance feels safer than doubt. Silence starts to look like professionalism until it doesn’t, and the consequences become unavoidable. As projects become more visible and more pressured, tolerance for challenge can quietly fall.

Leaders may want openness, but everyday reactions send powerful signals. People watch what happens when bad news is raised, and they adjust accordingly. Over time, honesty becomes selective, not because people disengage, but because they’re trying to survive.

You need control with candour

The usual response is to add more control – more checkpoints, more reporting – all with good intent. But control without candour doesn’t improve outcomes; it just produces cleaner paperwork. What kills projects isn’t bad news – it’s late news. This matters particularly for project or programme management office and assurance roles. We rely on early signals to support good decisions. If those signals are filtered, even strong governance becomes reactive, rather than preventative. By the time action is taken, options are already limited.

Psychological safety is core delivery infrastructure

Psychological safety cuts through that. It allows uncertainty to be voiced while it’s still useful. It makes challenge normal rather than awkward. It turns escalation into responsible action, not personal failure. Teams that feel safe don’t lower standards – they raise them, addressing issues earlier and learning while delivery is still live. So maybe the question isn’t whether teams feel comfortable. Comfort isn’t the goal. A better question is whether it’s safe to say, ‘I’m not convinced’, before it’s too late.

Psychological safety isn’t a nice extra. It’s core delivery infrastructure. Until we start treating it that way, we’ll keep being surprised by outcomes that, deep down, people saw coming.

Listen to James Evans’ interview with the APM Podcast on how to get psychological safety right, and look out for the new APM Learning module on psychological safety, set for release in April 2026. Find out more at APM Learning.