7 ways for CIOs to deliver bad news without losing trust

Insights from CIOs, consultants, and executive coaches show that effective CIOs don’t just report problems, they share information early, explain the issues clearly, and help executives decide what to do next. Here are seven ways CIOs can deliver bad news more effectively.

1. Build transparency early so bad news is never a surprise

Successful CIOs don’t wait until something goes wrong to talk to executives. They make a habit of being open from the beginning, so when problems come up, leaders will already understand the risks and what’s going on. Sumit Johar, CIO at cloud-based software company BlackLine, says this approach helps prevent tough conversations from turning into trust issues.

“You don’t want to be in a spot when you deliver bad news and everybody asks, ’How can this happen?’” he says. “We never had any conversations. What risks were taken and why weren’t we taken into confidence?”

So regular updates about risks, trade-offs, and decisions make all the difference.

“I’d say regular, transparent, and factual conversations about the statuses of these initiatives are essential, so if something goes wrong, you’ve already kept everybody prepared,” he says.

Keeping leaders updated helps move the focus away from blaming people and toward finding solutions so they can concentrate on what to do next.

2. Lead with the main issue immediately and clearly

Debbi McCullough, an executive communications coach, says CIOs need to get to the point quickly. “Keeping the bottom line on top feels essential and is a step many overlook,” she says. “If we bury the bottom line and take forever before reaching the point, we frustrate our CEOs and C-level leaders who want to know what’s going on from the opening sentence.”

She adds that in stressful situations, a CIO should keep their messages short and clear, and let executives ask questions if they want more detail.

Ghaleb El Masri, MD and partner at consultancy Adaptovate, agrees that these conversations need to be clear and well organized.

“The most effective way to deliver bad news is to make it decision-ready,” he says. “Executives can handle bad news but what they can’t afford is ambiguity. I use a simple sequence: what happened, what’s the business impact, what’s been done to contain it, and what decision is needed now.”

3. Translate technical problems into business impact

CIOs deal with complex technical issues, but executives also need to understand what those issues mean for the business. Patty Patria, CIO at Babson College, says leaders must frame problems in business terms.

“One of the most effective ways to deliver bad news to executives on a project or major operational issue is to be honest and transparent about the situation,” she says. “Clearly explain the root cause of the problem, and then present multiple alternatives for discussion on how to address the issue.”

She also emphasizes connecting issues to outcomes that matter to leadership, such as cost and timing.

“This approach not only builds trust but also encourages collaborative decision-making, ensuring that executives have a clear understanding of the situation and viable options moving forward,” she adds.

Eric Nitzberg, founder of Sierra Leadership, explains why this translation is essential.

“One of the biggest mistakes technical leaders make when presenting to the C-suite is using too much technical jargon,” he says. “Instead, translate ideas into plain, intelligent business language as if you’re presenting to intelligent high school students. You don’t talk down to them, but rather speak to them in their language, using words they can understand.”

4. Bring solutions and show ownership from the start

Executives don’t just want to hear about problems. They expect CIOs to take ownership and present a clear way to move forward. Sesh Tirumala, CIO of hardware manufacturer WD (formerly Western Digital), offers a different way for CIOs to handle these situations.

“Stop calling it bad news; there is no bad news,” he says. “There are problems, and problems can be solved. The most effective thing a CIO can do is walk in with the problem clearly defined and a path forward already in hand. Lead with the solution, not the situation.”

Tirumala adds that executives care more about action than explanation, and don’t need a play-by-play of what went wrong. “They need to know you see the issue, you own it, and you have a plan,” he says. “One sentence on the problem, three on what you’re doing about it.”

Patria adds a real-world example, explaining how her team handled delays on a particular ERP project.

“We were implementing a new product that had several product deficiencies, and although the product long term was the correct solution for the institution, its maturity presented multiple blockers to going live in the original timeframe,” she says. “So we presented detailed facts of each blocker, discussed how we would address them, and then provided the new timeline and increase to cost.”

With all the key stakeholders involved in the discussion, Patria says that everyone agreed to move forward with extending the project by six months.

5. Stick to the facts and avoid speculation

In high-pressure situations, CIOs may feel they need to explain why something happened before they know all the facts. This can lead to confusion and credibility issues later. Johar advises CIOs to focus on what they actually know.

“The most important aspect in delivering bad news is stick to the facts and make sure people understand what happened,” he says.

He also warns against jumping to conclusions too early.

“Sometimes you try to jump ahead and explain why something happened, and then after the investigation is complete, sometimes the whys change,” he adds. “Then it becomes a lot harder conversation to explain.”

Johar says CIOs should be clear about what they know and what they’re still figuring out, and let executives know when they’ll provide updates. This helps build trust and keeps things clear.

6. Stay neutral, avoid defensiveness, and keep emotions in check

Sharing bad news can bring out strong emotions, especially when a lot is on the line. But if emotions drive the message, it can hurt the conversation.

Johar says a common mistake CIOs make is becoming too defensive, focusing on explaining why something happened, or who’s to blame, instead of having the kind of clear, productive conversation that’s needed when delivering bad news. Nitzberg echoes this point, advising CIOs to stay objective.

“CIOs should avoid an overly detailed, negative, emotional, or blame-oriented narrative,” he says. “Neutrally share the facts at an altitude appropriate to inform the C-suite.”

McCullough also warns CIOs not to focus too much on their own feelings.

“Avoid being self-serving and lamenting on how horrible you feel,” she says. “Share that you’re devastated or disappointed if you must, but keep it short and make the focus on what happened, why, and how you and your team will work to make things better.”

7. Create a culture where people share bad news early

Even the best communication strategies won’t work if employees are afraid to speak up about problems. Company culture plays a big role in how people share bad news and how it’s received. Johar explains that clear and open workplace cultures help people communicate more effectively.

“Professional organizations actually invest a lot in building a culture that allows you to have difficult conversations, deliver bad news, and deal with bad news,” he says.

He adds that preparation is key in that, going through this kind of training informs exactly whom to speak to and about what.

El Masri highlights the consequences of poor culture in a company. “In organizations where leaders punish the messenger, bad news gets softened, delayed, and filtered at every layer,” he says. “But when early escalation is respected, issues surface while there’s still time to act.”

One thing people often miss is that a yes culture can be a liability. “When no one pushes back and problems get smoothed over to keep the peace, you lose the signal you need most,” Tirumala says. “What you actually want is a culture of feedback and clear decision-making, where people feel safe saying something isn’t working and where there’s a clear enough structure so problems get escalated and acted on, not just acknowledged.”