“Never shoot the messenger” is what’s proclaimed, but it’s all too rare in business when delivering bad news to executives.

Here’s another all-too-common situation. IT teams who are in frequent firefighting mode and unsure when, who, what, and how to communicate SEV 1 (Critical) issues to executives.

“Bad news” may be about an outage, a security issue, or another operational crisis. But it can also be an initiative that’s missing targets, a personal issue with an employee, a major problem impacting a customer, a sales effort that’s gone south, a pricing increase impacting the budget, a disparaging social media post that’s gone viral, and other things that go wrong.

Communicating bad news is a leadership responsibility

In Digital Trailblazer, I share several “bad news” stories and how I managed through them. At StarCIO, we have an Advisory to help IT teams develop a communications strategy.

Communication is an incredibly important leadership skill. It elevates your credibility with executives who judge your performance. It helps develop trust. But it can also derail careers when Digital Trailblazers are all action and use no or poorly selected words when communicating with executives.

“Bad news doesn’t erode credibility, but delaying or softening it does,” says Vikram Bhandari, chief technology and innovation officer at Riveron. “Treat it as a signal, not a setback. Share the facts, quantify the impact, own whether it was a control failure or a flawed assumption, and lay out the containment plan and corrective action to protect the investment. That’s how you turn a problem into trust.”

There are two sides to communication – what you say and what people hear. But the important starting point is to define who you are communicating with, what their tolerance is around negative news, and what they need to hear.  

“In highly technical organizations, the biggest risk isn’t that something goes wrong; it’s that leadership hears about it too late or without the right context,” says Nathan Mason, VP of strategic growth at BQP. “When a system outage, security incident, or delivery delay occurs, executives need a clear explanation of what failed in the system, how it affects the mission or the business, and what the recovery path looks like.”

Communicate the impact, come prepared with data and a plan

When considering what to communicate, focus on the impact, not on what broke and why. Be prepared to answer questions about the technical issues and have the appropriate data on hand. State your high-level plan. Avoid jargon.

“When delivering bad news to the C-suite, ditch the technical excuses and lead with the material impact on P&L and risk,” says Miles Ward, CTO of AI in Solution Lines at Insight. “Executives don’t want a post-mortem while the fire is still burning; they need a partner who can translate a system outage into a recovery path that preserves organizational velocity. The goal isn’t just to report the failure, but to demonstrate the operational maturity required to contain the crisis’s blast radius, ensuring a single outage doesn’t become a recurring tax on the business.”

Plan for swings in AI and digital transformation initiatives

One reason we transitioned from waterfall project management to agile methodologies, including agile planning and change management, is that transformational initiatives always involve unknowns and risks. Transformational initiatives are also not one-time deliverables, so the product manager and delivery leader overseeing the program must have a communication plan for positive outcomes, status updates, and when there is bad news.

“Teams that treat digital transformation as an organizational competency build the muscle to surface problems early, communicate them clearly, and adapt quickly,” says Mason of BQP. “The organizations that struggle are usually the ones where information moves slowly, and by the time leadership sees the issue, the real opportunity to fix it has already passed.”

StarCIO Bad News Communications Playbook

We covered culture transformation and communicating bad news to executives at a Coffee With Digital Trailblazers. I asked an AI for help converting the speakers’ best practices into the following bad news communications playbook.

Before you speak

• Know your executive: level of detail, preferred format, and cadence. 
• Assess business impact: brand, revenue, customers, operations, legal. 
• Decide your objective: inform, ask for help, or seek a decision. 
• Gather facts: what you know, what you don’t know, and when you’ll know more.
• Define leadership: who is leading triage and will provide detailed updates

How to show up

• Stay calm and grounded: no “sky is falling” tone. 
• Focus on solutions and forward motion, not blame. 
• Assume positive intent and avoid drama or theatrics. 
• Use simple language; avoid jargon and technical fog. 
• Respect everyone’s time: be brief, then invite questions.

How to deliver the message

• Lead with the headline: what happened in one clear sentence. 
• Give context: scope, who/what is affected, and for how long. 
• State impact: why this matters now (brand, money, risk, timing). 
• Be transparent: no spin, no hiding, no surprises later. 
• Provide updates: Say what you don’t know and when you’ll provide an update.

Set triage team protocols

• Communicate: Current status and trend: getting worse, stable, or improving. 
• Prioritize and track: Immediate actions in progress and owners. 
• Plan: 2–3 options or next steps with pros/cons. 
• Capture: Specific asks of the executive (decisions, approvals, support). 
• Set expectations: Specify a timeline for the next update.

Communicating the post-mortem

• Send a short written recap: facts, impact, and decisions. 
• Confirm next steps; accountabilities, owners, and dates. 
• Capture lessons learned and improvement actions.
• Review communication and decide what went well, what needs improvement
• Thank people who surfaced the bad news early.

Download the Bad News Communication Playbook