Ƶ

Skip to content

When culture distorts reality: The organisational behaviours that undermine project clarity

Added to your CPD log

View or edit this activity in your CPD log.

Go to My CPD
Only Ƶ members have access to CPD features Become a member Already added to CPD log

View or edit this activity in your CPD log.

Go to My CPD
Added to your Saved Content Go to my Saved Content
project communication

I’ve been in environments where everything looked fine until it really wasn’t.

Early in my career, I worked as a 999 call-taker in the NHS. You learn quickly to listen properly — not just to what people are saying, but to what they’re not saying. Hesitation, gaps, things that do not quite add up. Those signals matter.

Years later, while sitting in project boards, I started noticing the same thing in a completely different setting. Status reports were neat. Risks were “under control”. Conversations were smooth, almost too smooth.

But something felt off.

Over time, I realised it wasn’t a reporting issue. It was something deeper. The system was not broken; it was behaving exactly as the culture allowed it to.

The illusion of clarity

Most organisations genuinely believe they have a clear view of their projects. We build dashboards, define governance, standardise reporting all because it gives us a sense of control.

But the reality is this; clarity is only as good as the environment it comes from.

If people do not feel able to speak honestly, the data becomes a performance. Not intentionally misleading, just filtered. Softened. Managed.

What you end up with looks like clarity, but it is not.

And in my experience, that distortion tends to come from a few very familiar cultural patterns.

The behaviours that quietly distort reality hero culture

This one is often celebrated, which is why it’s so easy to miss. The person who pulls it back at the last minute. The late-night fix. The recovery story everyone applauds.

But underneath that is a system where problems are not raised early because recognition sits at the end. Why flag an issue when you might be rewarded for fixing it later?

So things stay hidden longer than they should.

How your reaction to bad news shapes team honesty

I have seen this play out countless times. Someone raises a risk and the first response is: why was this not picked up earlier, who owns this? 

You can feel the shift straight away. 

After that, people get more careful. Updates become more polished. Language softens. Not because people are trying to mislead, but because they are protecting themselves.

And slowly, honesty becomes harder.

Project reporting that drives real decisions

Projects are naturally optimistic. We are trying to deliver something new, often under pressure, but there is a tipping point where optimism turns into distortion.

Deadlines become commitments rather than forecasts. Assumptions go unchallenged. People start reporting what they hope is true rather than what is actually happening.

It is not lying. It is hope creeping into the data.

Cut the green status. Start reporting what is real.

This often sits underneath everything else. In fast paced environments, challenge can feel like disruption.

Raising concerns feels like slowing things down. Asking difficult questions feels uncomfortable. So people stay aligned on the surface, even when they are unsure underneath. 

That is where silence really starts to build. 

On their own, each of these behaviours might not seem critical. Together, they create a system where reality is diluted before it ever reaches the people making decisions.

Why this matters more than we think

This is not just about getting reporting right. It goes much deeper.

When leaders are working from a distorted picture, decisions are made with false confidence. Risks are identified too late to act on. Teams disengage because they know the picture is not real. Delivery becomes reactive instead of controlled.

I have seen projects where the dashboard stayed green almost until the point of failure. Not because the issue appeared overnight, but because it had been sitting there quietly for weeks.

That is the real cost. Not just delay or overspend, but lost opportunity to act early when it actually mattered.

How to make challenge a normal part of project conversations

You do not fix this by adding more governance or tweaking templates. If anything, that often makes it worse. 

Instead, you have to look at what is happening underneath:

  • Where does bad news go in your organisation?
  • How early do issues genuinely surface?
  • Do people challenge openly, or only afterwards in smaller conversations?
  • What happens to the person who speaks up?

The answers to those questions will tell you far more than any report.

Cut the risk. Raise the issue. Keep the project moving.

This is where it becomes real. Culture is not changed through statements or posters. It’s shaped through behaviour, especially from leadership.

People watch what happens in the moments that matter.

If someone raises a concern and gets shut down, that message travels quickly. If someone speaks up and is supported, that travels as well.

Over time, those moments define what feels safe and what does not.

You cannot ask for transparency and then react badly when you get it.

Practical steps for project leaders

If you want clearer, more honest projects, a few shifts make a real difference.

Redefine what success looks like: Recognise people for raising issues early, not just delivering at the end. Make honesty part of what good looks like. 

Build challenge into the conversation: Do not wait for people to speak up. Ask directly. What are we missing. What could go wrong. Make challenge normal. 

Create space for real conversations: Formal reporting has its place, but it’s not where honesty thrives. Use one to ones and informal check ins to get a truer picture. 

Pay attention to your reactions: Your response to bad news matters more than the news itself. If the first reaction is frustration, people will think twice next time.

Go beyond the dashboard: Status reports only tell part of the story. Ask about assumptions, uncertainties and concerns. That is where real clarity sits. 

For me, this all comes back to something simple. In projects, the biggest risks are rarely the ones we do not know about. They are the ones that someone already sees but doesn’t feel able to say out loud. And until that changes, no amount of reporting will ever give us true clarity. 

 

You may also be interested in:

 

0dzԳٲ

Join the conversation!

Log in to post a comment, or create an account if you don't have one already.