How to tell your board bad news before it becomes a surprise
Tell the board what is confirmed, what remains uncertain, and what decision you recommend before uncertainty turns into a surprise. Bad news does not need a finished explanation before it can be reported. It needs an accurate account of the result, its current implications, and the work still required.
Team psychological safety is a shared belief that the team permits interpersonal risk taking. Amy Edmondson defines the construct in her 1999 paper, Psychological Safety and Learning Behavior in Work Teams. Her study links psychological safety with learning behavior in work teams.
Applying that concept to CEO-board communication requires care. The study does not establish that a particular board script will prevent blame or protect a CEO’s position. It does suggest a useful distinction: a forum can permit candid questions while still holding people responsible for performance.
Report the result before completing the explanation
Suppose an implementation milestone has been missed. The delay is confirmed. Its effect on customer revenue is still being assessed. Waiting for the commercial analysis can leave directors unaware of a result management already knows.
Report those facts separately. State the missed milestone and its date. Explain what the company currently knows about consequences. Label estimates and identify the next evidence that could change them.
A report can be prompt and provisional. “We have confirmed the delay; we have not yet confirmed the revenue effect” gives directors a clearer account than a polished story that blurs both.
Use the company’s agreed reporting process, governing documents, and legal advice to determine timing, recipients, and required disclosure. This article does not set legal reporting thresholds or authorize selective disclosure.
The stakeholder-expectations map helps identify what the board needs to oversee and what management must supply.
The slide moved later in the evening
In a composite scene, a CEO edits the board deck at home. A confirmed missed result moves toward the appendix because the explanation is incomplete. The CEO tells a partner that the presentation is almost finished, then spends another hour finding a less alarming chart.
The work has shifted from clarifying the result to controlling the first reaction. That can be hard to recognize when the CEO also has legitimate concerns about incomplete information.
Check the first substantive slide against the known result. If directors must work through several favorable updates before discovering a material problem, ask whether the order serves their oversight needs.
The private cost is not evidence of wrongdoing or a clinical condition. It is a concrete sign that presentation choices are consuming attention without resolving the underlying uncertainty.
Prepare a board facts-options-recommendation brief
The board facts-options-recommendation brief is a proposed structure for reporting an adverse development. It gives directors a stable distinction between evidence, choices, management’s judgment, and requested board action.
Use the structure within the reporting and meeting procedures your company requires. A short brief can accompany a fuller evidence pack. It should not replace formal notices or specialist advice.
1. State the confirmed result and comparison
Put the adverse fact in the opening paragraph. Identify the period, agreed target or commitment, actual result, and source of verification. Use the same definitions as the board’s previous reporting where possible.
If a measure changed, explain the change before comparing periods. Do not make the result look better by switching definitions without showing the effect.
Attach the evidence directors need to inspect the claim. For a missed milestone, include the approved baseline and current delivery status. Distinguish a management estimate from a customer-confirmed event.
2. Bound the uncertainty and its consequences
List the important questions that remain open. For each, name the evidence being sought, the person obtaining it, and the date of the next update.
Separate confirmed consequences from plausible scenarios. If the revenue effect depends on customer acceptance, explain that dependency. Do not present the most favorable scenario as the expected outcome without support.
Communicating uncertainty honestly helps maintain this distinction in spoken answers as well as slides. A director’s request for precision does not create information the company does not possess.
3. Present feasible options and their trade-offs
Show what management can do now and which choices require board authority. Include the relevant operational, financial, customer, and timing effects. Identify any option still awaiting feasibility or legal review.
Avoid presenting an obviously unacceptable alternative merely to make your preference look inevitable. Directors need to understand the real choices, including the cost of waiting.
For the implementation delay, feasible options might involve a revised sequence, additional approved resources, or a narrower interim delivery. These are hypothetical possibilities. The delivery team must establish which, if any, fit the actual obligations and capacity.
4. Give your recommendation and its conditions
Explain which option management recommends and why. Identify the evidence that supports it, the assumptions it requires, and the development that would cause you to reconsider.
Accept responsibility for management decisions you own. Do not convert uncertainty about cause into uncertainty about who will lead the response.
Then state the requested board action precisely. A request for approval, a request for advice, and an update provided for oversight are different. If authority is unclear, resolve it with the chair and counsel rather than allowing the meeting to improvise new decision rights.
5. Commit to a useful next report
Set the next update according to the problem’s pace and the board’s requirements. Name the information it will contain, including what happens if an important answer is still unavailable.
Record questions raised and decisions made through the proper governance process. Assign follow-up work without treating every director’s suggestion as a separate instruction to management.
At the next update, show what changed from the previous account. Explain a revised estimate or recommendation directly. Directors should not need to compare several decks to discover that a central assumption has failed.
An opening for a confirmed delay
A hypothetical CEO could begin:
“The implementation milestone scheduled for this week was missed. Delivery has confirmed the incomplete work. We are checking the customer and revenue consequences, which remain uncertain. Management recommends the revised sequence in this brief, subject to the capacity check tomorrow. Today we need the board’s decision on the resource request.”
This wording is usable only when those statements match the evidence and authority. Replace the hypothetical dates and actions with the company’s confirmed facts.
The opening does not promise that directors will react calmly. It gives them a clear account they can question. If a director asks for the final commercial effect, answer with what is known and the specific work needed to establish the rest.
A defensive reply would repeat the team effort without answering the result. An overconfident reply would supply a number that has not been established. Neither helps the board assess the recommendation.
Handle a question you cannot answer yet
If a director asks whether another customer faces the same problem, avoid answering from memory alone. Explain which accounts have been checked and which remain unassessed. Give an owner and timing for that review.
If the question reveals a missing line of investigation, add it to the work plan. You do not need to defend an incomplete brief as though it covered every possibility. You do need to ensure that the newly identified exposure receives attention and returns through the agreed reporting channel.
Recognize the limits of your own causal account
Ross and Sicoly’s 1979 experiments examine egocentric biases in recall and responsibility attribution. Their findings provide a reason to check your account of who contributed to the result.
They do not show that this CEO is biased or that another person’s explanation is correct. The practical implication is to compare records and obtain relevant accounts before assigning causes.
Ask the responsible team to distinguish the plan, actual events, decisions, and constraints. Include evidence that challenges management’s preferred explanation. If the investigation remains open, report that status rather than filling the gap with a character judgment.
Preserve accountability while the cause is investigated. Management can own the response now and revise its causal account when better evidence arrives.
Clarify how directors should participate
The APA’s 2018 role-ambiguity entry describes uncertainty about expected behavior in a position. That distinction matters when directors move from oversight questions into direct operational instructions.
A bad result can expose unclear boundaries. Who approves emergency spending? Who communicates with the customer? Who can direct staff? Resolve these questions through the company’s actual authority structure.
The chair-CEO relationship guide addresses the working channel for these conversations. Ask the chair to help organize oversight and follow-up within the applicable rules, without filtering out legitimate director questions.
If the board begins directing individual tasks, use the board-micromanagement boundaries guide to clarify the operating issue. Do not use that label to avoid an appropriate request for evidence or accountability.
Review whether the board received usable information
After the meeting, inspect the decision record and follow-up requests. Did directors understand the confirmed result? Did they distinguish the uncertainty? Was the requested action decided by the appropriate body?
Check management’s delivery of the promised update. A candid first presentation loses practical value if the next report disappears when the news remains uncomfortable.
Ask whether the reporting format concealed a developing issue in earlier periods. A milestone shown as green despite missing dependencies may need a different status rule. Fix the source of the reporting problem rather than adding reassuring language to the next deck.
Also examine how management responds to staff who bring adverse facts forward. A CEO cannot credibly invite early disclosure to the board while penalizing employees for supplying inconvenient information internally.
The working standard is a board that can see the result, question the account, and exercise its authority. Your role is to give it that opportunity before the problem arrives through another channel.
Sources
-
Edmondson (1999): Psychological Safety and Learning Behavior in Work Teams. The team-level construct informs the distinction between candid reporting and freedom from performance accountability in a board discussion.
-
Ross and Sicoly (1979): Egocentric Biases in Availability and Attribution. The experiments support checking management’s recollection of contributions before presenting a causal account of the adverse result.
-
APA Dictionary of Psychology: role ambiguity. The 2018 definition helps distinguish uncertain oversight and management expectations when the board considers the response.