The cost of silence: Why psychological safety is the missing ingredient in project success

Psychological safety in project teams when delivery is on track

Psychological safety is easy to claim when things are going well. It’s when they’re not that it really matters.

When delivery is on track, most teams would say they have it. Conversations are open, people challenge ideas, risks get raised early and it feels like a healthy environment. And to be fair, in those moments, it probably is.

But that’s also the easy version.

How delivery pressure erodes psychological safety in projects

The real test comes when things start to slip. Deadlines move, pressure builds and attention shifts quickly to outcomes. Nobody announces that anything has changed, but the atmosphere does and you can usually feel it before you can explain it.

People become more careful with what they say. Updates sound more considered, more polished. Problems don’t go away, but they get managed more quietly. Not because anyone is trying to hide anything, but because it no longer feels as straightforward to say things out loud.

That’s where the cost starts to build. You’re no longer dealing with reality in its raw form, but a version that’s been softened slightly. Decisions start getting made on that version instead. That’s how teams prioritise the wrong work, miss critical dependencies and make decisions that feel right in the moment but create bigger problems later.

When leadership pressure silences early warning signs

I’ve seen this play out in a team that, on paper, had done everything right. They had a clear team charter, regular sentiment checks and structured reviews focused on psychological safety. It wasn’t just talk; it was built into how they operated.

And for a while, it worked.

Then a piece of scope was missed. Delivery slipped, triggering a client escalation that quickly became visible at board level. The pressure ramped up, and almost overnight the tone shifted.

No one tore up the charter. No one said things were changing. But conversations became tighter. Updates more defensive. People started thinking about how things would land before they said them, rather than just saying them.

Everything that had been put in place was still technically there, but the behaviour had changed, and that was enough.

Projects rarely go from green to red in a single step. They drift into amber, but without the full picture being visible. A risk is mentioned but not pushed. An issue is acknowledged but softened. A concern is raised, but it doesn’t quite land.

If people don’t feel comfortable speaking up, those early warning signs don’t come through clearly. Amber doesn’t stay amber for long. It accelerates, and by the time the full reality is understood, the project is already in red. By the time the full picture is visible, recovery is more expensive, more disruptive and far less certain.

This doesn’t usually come from bad intent. Most leaders, when things go off track, are trying to regain control. They ask more direct questions, push for clearer answers and want to understand what’s happening.

But the tone shifts. There’s less patience, more urgency and sometimes stronger reactions than people expect. Teams pick up on that quickly. Before long, people start filtering what they say - and once that happens you’ve already lost visibility.

The intention is to get closer to the truth, but the effect is the opposite.

Leadership behaviours that protect psychological safety under pressure

The leaders who manage this well don’t lower expectations or avoid difficult conversations. If anything, they lean into them. The difference is consistency, especially when things aren’t going well. They don’t jump straight to judgement or create an environment where raising an issue feels like a risk.

Instead, they make it clear, through how they respond, that surfacing problems early is part of doing the job properly. Because of that, they hear about issues sooner - when there are still options.

Leaders don’t need to overhaul everything to improve psychological safety under pressure. But they do need to be deliberate in how they respond.

A few behaviours make a tangible difference:

• Reward early honesty: Treat early risk identification as strong delivery. The earlier something is raised, the more options you have.
• Separate the issue from the person: Address the problem without assigning blame. Accountability comes later, understanding comes first.
• Ask open questions before conclusions: Start with “What are we missing?” or “What’s changed?” before moving to challenge.
• Make uncertainty explicit: Good teams are clear on what they don’t know. Hidden uncertainty is where risk grows.
• Respond predictably to bad news: Your reaction sets the standard. If people see blame or frustration, they will filter what you hear next time.
• Stay consistent under pressure: If your behaviour changes when delivery slips, people will stop speaking up exactly when you need them to.

None of this is complicated, but it is easy to lose when pressure builds. It requires self-awareness and discipline, particularly when instinct pushes you in a different direction.

That’s the difference. Psychological safety isn’t something you demonstrate when everything is running smoothly, it’s something that either holds or disappears when it isn’t.

And if it only shows up in the good weeks, it probably wasn’t there in the first place. 

 

You may also be interested in:

• Why psychological safety isn’t a ‘nice to have’
• APM Learning module: Psychological safety in project teams
• Visit our bookshop: How to Manage Project Politics