Shooting the Messenger: A Self-Defeating Practice in Project Management

The Last Person Standing

I watched a director kill his own transformation program in fifteen minutes. Not through bad planning or budget cuts. Through shooting the messenger.

The project manager walked into the steering committee meeting with facts. Three major vendors were two weeks behind schedule. The ERP integration had uncovered data quality issues that would add 40 hours of cleanup work per department. Budget was still on track, but timeline needed adjustment.

Instead of addressing the issues, the director attacked the messenger. “Why didn’t you catch this earlier?” “This is unacceptable project management.” “I’m tired of hearing problems instead of solutions.”

Six weeks later, the project manager resigned. Two months after that, the program collapsed under the weight of all the problems that were never properly addressed.

Why We Shoot the Messenger

The psychology is simple. Bad news triggers our fight-or-flight response. When someone delivers unwelcome information, our brain wants to eliminate the source of discomfort. The messenger becomes the problem.

But here’s what I’ve learned after managing dozens of complex implementations: the messenger isn’t creating your problems. They’re revealing problems that already exist.

In one manufacturing transformation, we discovered that 60% of their “standard” processes had never been documented. The operations manager’s first instinct was to blame our discovery process. “We’ve been running fine without documentation,” he said.

The real issue? Their tribal knowledge was walking out the door with retiring employees. Three critical processes were already broken because only one person knew how to handle exceptions.

The Hidden Costs of Shooting the Messenger

When you attack the bearer of bad news, you don’t just damage one relationship. You send a message to everyone watching: “Don’t bring me problems.”

We see this pattern repeatedly in failing projects. Teams stop reporting risks. Status meetings become theater where everyone pretends things are fine. Real issues get buried until they explode.

In one retail client, the IT team knew their inventory system couldn’t handle Black Friday traffic three months in advance. But the CTO had a habit of “killing the messenger” whenever technical teams raised concerns about aggressive timelines.

Nobody spoke up. The system crashed on the biggest sales day of the year. Revenue loss: $2.3 million. All because the organization trained people not to deliver uncomfortable truths.

Building Systems That Welcome Truth

The best project environments we work in have one thing in common: they reward truth-telling, even when the truth is inconvenient.

Here’s what that looks like in practice:

• Separate the message from the messenger. When someone reports a problem, address the issue first. Thank the messenger second. Never attack the person bringing information.
• Ask “What do you need?” before asking “Why did this happen?” Focus on moving forward, not assigning blame for past decisions.
• Make risk reporting a requirement. We build red/yellow/green status into every project template. Teams must report what’s not working, not just what is.
• Respond to problems with resources, not rhetoric. When someone identifies a blocker, the response should be budget, time, or people—not lectures about commitment.

One manufacturing client transformed their culture by implementing “No Surprise Fridays.” Every project manager had to report one potential problem before the weekend, even if they weren’t sure it would materialize.

Six months in, their on-time delivery rate jumped from 73% to 94%. Why? Because they were solving problems while they were still small.

The Messenger as Early Warning System

Think of your project managers and team leads as your organizational radar system. They’re scanning the horizon for obstacles, dependencies, and risks that could derail your initiatives.

When they bring you bad news, they’re doing their job. The question isn’t whether you like the message. The question is: what are you going to do about it?

In our experience, organizations that embrace uncomfortable truths deliver projects 30% faster than those that suppress bad news. They also have 50% lower staff turnover in project roles, because people don’t burn out trying to perform miracles instead of managing realities.

Your choice is simple: shoot the messenger and stay blind to approaching problems, or build a culture where truth travels fast and solutions follow close behind.

Need help building project delivery systems that welcome reality? We specialize in creating environments where problems get solved, not hidden. Book a call at strategypeeps.com/contact and let’s talk about what’s really happening in your organization.