Develop Leaders Who Can Hear Bad News and Act on It

Treat early warning as a leadership capability

As year-end reviews and 2027 planning converge, executives face a practical test. Can their leaders surface a deteriorating assumption while there is still time to change the plan? Or will the business learn about it after spending the money, promising the delivery date or losing the customer?

A leader can present confidently, manage a large budget and still make it costly for others to raise concerns. The cost may be public criticism, repeated demands for more proof or exclusion from the next discussion. None requires an explicit instruction to stay quiet.

Leadership development should therefore examine what happens when someone challenges a leader’s preferred explanation. This is not a communication exercise. It affects the time available to protect cash, redirect investment and recover delivery.

Amy Edmondson’s research linked team psychological safety with learning behavior.^[1] The practical implication is specific: people need to be able to report uncertainty and mistakes without interpersonal punishment. That does not remove performance standards. It makes problems available for scrutiny sooner.

Practice the first response, not just the presentation

Most senior leaders have substantial practice defending a plan. Give them equally serious practice receiving evidence that the plan may be wrong.

Use a live business issue with real consequences. A delayed launch. A weak renewal pipeline. A cost reduction that depends on service levels holding steady. Ask a colleague to present credible evidence against the current forecast.

Observe the leader’s first response. Do they investigate the issue or question the messenger’s competence? Do they separate what is known from what is inferred? Can they state what evidence would change their view?

A useful rehearsal has four steps:

• Establish the facts. What changed, when did it change and how reliable is the evidence?
• Identify the exposure. Which customer promise, cash assumption or operating dependency is now at risk?
• Set a decision point. What must be decided now, and what can wait for additional evidence?
• Close the loop. Who will act, by when, and who needs to hear the result?

The observer should describe behavior, not assign a personality label. “You asked who was responsible before asking about customer exposure” is useful feedback. “You are defensive” is less actionable.

Ibarra and Scoular describe coaching as helping people develop through inquiry rather than simply supplying answers.^[2] Apply that discipline here. The executive sponsor should help the leader examine their response, then repeat the exercise with a harder case.

Keep accountability separate from blame

Inviting bad news is not an agreement to excuse poor execution. Leaders still need to distinguish among a flawed assumption, a reasonable experiment, an avoidable error and a failure to meet an agreed obligation.

Edmondson’s work on learning from failure makes this distinction central: different failures require different responses, and treating them all alike obstructs learning.^[3]

For development purposes, require the leader to run two separate conversations. First, contain the business exposure. Second, examine how the problem arose and what accountability follows. Mixing the two too early can turn an urgent operating discussion into a defense of individual reputations.

Consider a sales leader who reports that a major deal will slip. The immediate questions concern cash timing, delivery capacity and the credibility of the revised forecast. The later review should examine whether warning signs were missed, assumptions were weak or known information was withheld. Early disclosure should not erase responsibility. Nor should responsibility make early disclosure irrational.

Escalation also needs boundaries. Define which issues a leader should resolve locally and which require executive attention. Use business consequences: a material change in cash expectations, a customer obligation at risk or a dependency another function cannot absorb. Do not turn every uncertainty into a meeting with the CEO.

Build the practice into year-end reviews

This week, ask each executive to bring one case in which someone delivered unwelcome information. Review the sequence, not the polished retrospective. What was reported? How did the executive respond? What decision followed? When did the person who raised the issue hear back?

Choose one behavior to practice during the next month. Examples include asking for contrary evidence before approving a forecast, acknowledging an unresolved concern in the decision record or telling a team what changed because of its warning.

Do not judge progress by the number of issues escalated. More reports may reflect greater candor, worsening execution or both. Look for clearer evidence, appropriate ownership and decisions made while options remain open.

The test is not whether leaders say they welcome bad news. It is whether their behavior helps the business act on it in time.