Why I Stopped Sitting on Bad News
Issue 22 — June 17, 2026

THE DECISION
The product is delayed. The installation date will not hold. You have known for a day, maybe two. When do you tell the client?
I spent the early part of my career answering that question badly. I did not want to be the bearer of bad news. So I put it off. I waited for the problem to resolve itself. I waited for a better version of the truth to show up. It never did.
I eventually realized the decision was never about communication. It was about comfort. Specifically, whose comfort I was protecting.
"I eventually realized the decision was never about communication. It was about comfort. Specifically, whose comfort I was protecting."
WHAT'S REALLY GOING ON
When you sit on bad news, you are not managing the client's problem. You are managing your own discomfort. The delay does not change while you wait. The shipment is still late. The crew still cannot install on the promised date. The only thing that changes is the client's ability to respond.
Every day you hold the information, the client loses options. They could have moved the electrician. They could have reset expectations with their own stakeholders. They could have adjusted an opening date while adjusting was still cheap. Silence removes those options one at a time, without their knowledge.
There is a second problem underneath. Bad news rarely stays hidden. When the client finds out late and realizes you knew, the problem changes category. A project problem becomes a trust problem. Project problems get solved. Trust problems get remembered.
QUESTIONS I'D ASK
Before you pick up the phone, work through these.
Is the information confirmed?
What options does the client lose if I wait?
If I were the client, when would I want to know?
If the answer to the first question is no, you are not ready to communicate. You are ready to verify. That is the only acceptable reason to wait.
A project problem becomes a trust problem. Project problems get solved. Trust problems get remembered.
THE TRADEOFFS
Telling the client now costs you an uncomfortable conversation. You may absorb blame. You may face anger about a problem you did not cause and might still hope to fix quietly.
Telling the client later buys you comfort today. The price is compounding. The fix you hoped would arrive usually does not. Now you are delivering worse news, later, with fewer options on the table, and a new question hanging over the call: how long have you known?
There is also a cost to moving too fast. Delivering bad news that turns out to be wrong damages your credibility in the other direction. That is why the order matters. Verify first. Communicate immediately after. Speed without accuracy is just a different way of being unreliable.
WHAT I WOULD DO
Verify the information the same day you receive it. If it holds, contact the client the same day. A call, not an email. Bad news delivered in writing reads like hiding.
Lead with the facts. What happened, what it affects, what you know, what you do not know yet, and when you will update them. Then stop talking and let them respond.
If the problem is your mistake, say so in the first minute. Plainly. A clear admission survives. Spin does not. Admitting a mistake quickly cost me less, every single time, than explaining one slowly.
It took me years to learn this. The clients who heard bad news from me early are the ones who kept working with me for decades. Not because the news was good. Because they never had to wonder what I was not telling them.
ONE THING THIS WEEK
If you are holding a piece of bad news right now, a delay, a missed estimate, an error you caught, verify it today and deliver it tomorrow. Pay attention to how the client responds to hearing it early. That response is the case for doing it this way every time.
Decide well,
Chuck
Decided
Weekly AI guidance for business owners making operational decisions.