Skip to content
Delivering Bad News Upward: A Plain-Language System for Founders and COOs

Delivering Bad News Upward: A Plain-Language System for Founders and COOs

Yaroslav Maxymovych· with AI assistance11/16/202652 views6 min read

TL;DR

  • •Deliver unwelcome news early, in writing, and without adjectives.
  • •Separate what happened from what you are doing about it, and state the decision you need from the owner.
  • •Never send bad news for the first time in a live meeting — give the owner time to read and respond.

When something goes wrong in a 30-500 person company, the instinct is to soften it. Founders and CEOs learn quickly that softened bad news arrives late, and late bad news costs money.

This article is a plain-language system for delivering unwelcome news upward. It is written for COOs, heads of department, and team leads who report to an owner — and for founders who want their teams to stop hiding problems until they become crises.

Definition: unwelcome news

Unwelcome news is any status update where the fact differs from the plan in a way that costs time, money, or customer trust — a missed deadline, a budget overrun, a lost deal, or a blocked project.

Definition: spin

Spin is language that obscures the gap between plan and fact: "we are exploring options," "timeline is fluid," or "minor delay expected." It protects the messenger, not the business.

How to structure unwelcome news upward

What is the right order for bad news?

Lead with the fact, then the impact, then the recovery, then the ask. Owners do not need a narrative arc. They need to know what changed, what it costs, and what decision is waiting on their desk.

How to write the fact line

State what happened, when, and who is affected. Use past tense. Avoid words like "unfortunately," "challenging," or "unexpected."

Good: "The Q3 vendor integration slipped four days. The external API returned authentication errors starting Tuesday."

Bad: "We are facing some headwinds with the vendor integration and are actively working through a few technical complexities."

What belongs in the impact section

Quantify only what you know. If you do not know the cost yet, say so. Guessing damages credibility faster than the bad news itself.

What to include in the recovery paragraph

Describe the specific next step, who owns it, and when you will report back. If you do not have a fix yet, say that you are diagnosing and will update by a specific time.

Tool tip (AiAdvisoryBoard.me):

Bad news surfaces faster when you have a stable Plan → Fact → Gap rhythm. If your status updates already show planned work versus actual work, unwelcome news is just a highlighted gap — not a surprise. See how the 7-day diagnostic maps your team's real plan/fact gaps.

Tool tip (AiAdvisoryBoard.me): https://aiadvisoryboard.me/?lang=en

What decision do you need from the owner?

End every unwelcome update with one explicit ask: approve a budget exception, extend a deadline, reassign a resource, or confirm the recovery plan. If you do not need a decision, label the update "for awareness only."

Good vs bad: unwelcome news examples

Example 1: Missed client deadline

Good:

"The website migration for Acme Corp is two days behind plan. The DNS cutover did not complete on schedule because the client's IT team has not provided zone access. Impact: go-live moves from Thursday to Monday at earliest. I need you to decide whether we email the client today or wait until Monday with a confirmed date."

Bad:

"We are working through some final migration details with Acme and expect to wrap up shortly. The timeline remains fluid as we coordinate with their side."

Example 2: Budget overrun

Good:

"Q3 marketing spend is 18 percent over plan. Two unplanned campaign tests drove the variance. I am pausing all new spend until Friday and will bring you a revised forecast by end of week."

Bad:

"Marketing is seeing some investment pressure this quarter as we test new channels. We are reviewing the numbers and will adjust accordingly."

Micro-case (what changes after 7–14 days)

A COO at a 120-person logistics company started sending Friday status notes with a single "red" line for anything off plan. In week two, she flagged that a warehouse software rollout was stuck because the vendor had not signed the SOW. The owner saw it Friday morning, called the vendor that afternoon, and unblocked the contract by Monday. Before the new habit, that delay would have surfaced in the monthly ops review — two weeks later.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

FAQ

Should I deliver bad news in person or in writing?

Start in writing. A written update lets the owner process the information before reacting, and it creates a record. Follow up with a call or meeting only if the owner asks for one.

How often should I send unwelcome updates?

As soon as you know. Waiting for the weekly cadence turns a fixable problem into a crisis. Regular status updates are for rhythm; unwelcome news is for immediacy.

What if I do not have all the facts yet?

Say what you know, say what you do not know, and commit to a time when you will have more. Silence while you investigate is worse than an incomplete update.

How do I stop my team from softening bad news before it reaches me?

Make it safe to report gaps early. If the first unwelcome update from a team lead is met with anger, the next one will be delayed or rewritten.

Conclusion

Unwelcome news does not get better with age. The goal is not to deliver it perfectly — it is to deliver it early enough that the owner can still do something about it.

Start tomorrow: pick the one thing on your plate that is off plan, write it in three sentences using the fact-impact-recovery-ask format, and send it before the end of the day.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works. https://aiadvisoryboard.me/?lang=en

Read with AI

Open this article in your assistant — it will summarize it and help apply it to your company.

Show the prompt

Read the article https://aiadvisoryboard.me/blog/deliver-bad-news-upward-plain-language-system.md and summarize the key points. Then ask me about my company (industry, team size, what takes the most time) and explain which ideas from the article apply to us and where to start.

More on this topic
Team Status Updates: Short Formats That Actually Work (With Examples) →

The pillar guide for "Status Updates" linking every article in this cluster.

Yaroslav Maxymovych
Author
Yaroslav Maxymovych
Founder & CEO, AI Advisory Board

Implements AI agents in companies and teaches founders and their teams to work with them — through courses and corporate programs.

This article was prepared with AI assistance, based on Yaroslav Maxymovych's methodology and materials. Spotted an inaccuracy — let us know via the form below.

For teams

A template is good. A system where the report writes itself is better

A 10-minute daily ritual for every employee: plan + fact + blockers. Implemented in 1 day. Teams that write down their plans hit their goals 42% more often.

10 minutes a day
Implemented in 1 day
+42% goal achievement
See how it worksIt's the product page, not a checkout — a 2-minute look
Newsletter

AI adoption resources — one email

Leave your email to receive a welcome email with blog resources. There is no regular newsletter at present

No spam. Unsubscribe anytime.