9:12 AM.
An engineer notices a problem.
It is still small. Nothing critical has happened yet. But there is a risk: if the initial assumption is correct, the project timeline may slip.
He does not escalate it.
First, he wants to verify it.
11:40 AM.
The problem is confirmed.
The engineer informs his manager.
The response is reasonable:
— Let’s not escalate this yet. We may be able to solve it ourselves.
3:25 PM.
They cannot.
Two more colleagues are brought in. There is another possible solution. They need a few hours to test it.
The customer is not informed yet.
6:10 PM.
The alternative does not work either.
Someone suggests informing the director.
— It’s already the end of the day. Let’s wait until morning. The supplier may respond overnight.
At this point, the company has not necessarily lost money.
It has lost something potentially more valuable:
the time during which it still had choices.
Day Two. 10:15 AM.
The supplier responds.
The news is not good.
It is now clear that the issue is more serious than originally expected.
The information moves one level higher.
The questions begin:
— Who already knows?
— Has the customer been informed?
— How serious is this?
— Do we have an alternative?
— When will we know the full impact?
The team decides to collect all the facts first.
Nobody wants to approach the CEO with incomplete information.
That also sounds professional.
4:30 PM.
The CEO finally learns about the problem.
And asks one question:
“When did we first realize this might happen?”
The answer:
“Yesterday morning.”
And suddenly, we are looking at a completely different problem.
Not a technical problem.
Not a supplier problem.
Not even a project problem.
It is a problem with the speed at which bad news travels through an organization.
We Measure Almost Everything — Except How Fast the Truth Reaches Us
Modern companies measure an extraordinary number of things.
Revenue.
Margin.
Conversion.
SLA.
Uptime.
Lead time.
Customer satisfaction.
Project completion.
Incident volume.
Support response time.
But there is one metric you will rarely find on a corporate dashboard:
Time to Bad News.
Let’s call it TBN.
TBN is the time between the moment someone inside an organization first realizes that a significant problem may exist and the moment that information reaches the person who has the authority to make the necessary decision.
If an engineer identifies a risk at 9:12 AM and the CEO hears about it at 4:30 PM the following day, the company’s TBN is more than a day.
And sometimes those hours cost more than the original mistake.
Because the problem may initially have several possible solutions.
But every lost window of time closes one of them.
Why Do Smart Employees Delay Bad News?
Usually, it is not because they want to harm the company.
Quite the opposite.
The first instinct is often:
“Let me try to solve it first.”
That is a natural professional reaction.
Nobody wants to approach management carrying nothing but a problem.
We are often taught:
Don’t bring me a problem. Bring me a solution.
It sounds excellent.
But this management philosophy has a dangerous side effect.
If employees believe they are only allowed to report a problem once they have found a solution, management may learn about critical risks far too late.
Sometimes a leader does not need the answer yet.
The leader needs early information.
Because at another level of the organization, options may exist that the employee simply cannot see.
A priority can be changed.
A customer can be called.
A vendor can be escalated.
An architecture can be modified.
Alternative stock can be reserved.
A budget can be redirected.
Another specialist can be involved.
A conversation can happen at a level inaccessible to the employee.
But all of these options have one dependency in common:
time.
Bad News Has an Expiration Date
Consider a simple example.
Today, you learn that critical equipment may not arrive on time.
You have four alternatives.
Three days later, perhaps you have three.
A week later, one.
The day before the contractual deadline, you may have none.
The information itself has not changed.
Its value has.
On Monday, it was information that could drive a decision.
By Friday, it may have become an explanation for why a decision is no longer possible.
That distinction matters.
A good management system should deliver a problem while the information can still change the outcome.
Not when all that remains is explaining the consequences.
So Why Does Information Get Stuck?
Because organizations develop invisible filters.
An employee filters information before giving it to a manager.
The manager filters it before passing it to a director.
The director filters it before taking it to the CEO.
Every level wants to understand the situation first.
Every level wants to demonstrate control.
Every level hopes the problem will disappear before the next escalation.
And something strange happens.
The higher someone sits in an organization, the more processed their reality can become.
The engineer sees:
“We have a problem.”
The manager reports:
“We have an issue, but the team is working on it.”
The director says:
“There is a certain risk, but the situation is under control.”
By the time it reaches the CEO:
“There is a minor matter currently being addressed.”
Same problem.
Four organizational layers.
Completely different temperature.
Red Slowly Becomes Yellow
This is one of the most dangerous effects of corporate communication.
Nobody necessarily lies.
Each person simply softens the message slightly.
A “problem” becomes a “challenge.”
A “delay” becomes a “potential timeline adjustment.”
A “critical risk” becomes “an item requiring attention.”
And:
“We don’t know how to solve this.”
becomes:
“The team is currently evaluating several options.”
Each change seems harmless on its own.
Together, they can give the decision-maker a fundamentally different picture of reality.
An Open-Door Policy Is Not Enough
Many leaders say:
“My door is always open.”
That does not necessarily mean bad news reaches them quickly.
The real question is not whether the door is open.
The question is what happens to the person after they walk through it.
Consider two scenarios.
In the first, an employee reports a serious problem and the leader immediately asks:
— How did this happen?
— Who is responsible?
— How could you allow this?
— Why didn’t you think about this earlier?
Next time, that employee will not be thinking about rapid escalation.
They will be thinking about self-protection.
In the second scenario, the leader’s first question is:
“What can we still change if we act now?”
The difference is enormous.
The first question investigates the past.
The second protects the future.
Accountability still matters.
But it can be addressed after the damage has been contained.
Psychological Safety Is Not Corporate Softness
The term psychological safety is sometimes misunderstood.
It can sound like an environment where nobody should be criticized and everyone should always feel comfortable.
That is not the point.
Operationally, psychological safety is the ability to say:
“We have a problem.”
“I made a mistake.”
“I’m not sure.”
“This deadline is unrealistic.”
“I disagree.”
“I think this project is moving in the wrong direction.”
— before proving it becomes too expensive.
This is not primarily about comfort.
It is risk-management infrastructure.
There Is Another Dangerous Phrase: “Don’t Bother Management With Small Problems”
Of course, a CEO should not receive an alert for every technical incident.
If everything is escalated upward, the organization will stop functioning.
The goal is not to create a culture of permanent alarm.
The goal is to establish clear escalation conditions.
For example, escalation may be required when a contractual deadline is at risk; when potential financial exposure exceeds an agreed threshold; when a strategic customer is affected; when cybersecurity, compliance, or reputation could be impacted; when solving the issue requires authority the current owner does not have; or when every passing hour reduces the number of available options.
That last condition deserves particular attention.
A problem can still be small while the speed at which it is developing already makes it important.
Try One Experiment at Your Next Management Meeting
Instead of asking:
“What problems do we have?”
ask:
“What are we trying to solve ourselves today that we may regret not escalating a week from now?”
The silence after that question may tell you more than another dashboard.
Then ask a second question:
“What bad news is hardest for you to tell me today?”
If a leader can hear the answer without immediately becoming defensive, they may learn more about the organization in ten minutes than from twenty KPIs.
AI Is About to Make This Problem Even More Interesting
We are entering an era in which information can move through organizations technically faster than ever.
AI can analyze thousands of messages.
Detect anomalies.
Identify deviations.
Predict delays.
Surface emerging risks.
Generate executive summaries almost instantly.
But there is a paradox.
A company can have AI that detects a problem in 30 seconds — and a culture that takes three days to tell management about it.
Technology can accelerate detection.
It cannot automatically repair organizational behavior.
That means the next competitive advantage may not simply be how quickly a company gets information.
It may be how quickly the organization is willing to accept uncomfortable information and act on it.
Perhaps Companies Need One More KPI
It does not necessarily belong on the official dashboard.
But leaders should occasionally ask:
What is our Time to Bad News?
Minutes?
Hours?
Days?
And perhaps more importantly:
What happens to that number as the company grows?
An organization of 20 people may transmit bad news almost instantly.
At 200 employees, layers appear.
At 2,000, processes.
At 20,000, committees, reports, governance structures and formal escalation paths.
Every new management layer can add control.
It can also add latency to the truth.
The Most Dangerous Company Is Not the One Where Mistakes Happen
Mistakes happen everywhere.
Projects are delayed.
Systems fail.
People make incorrect assumptions.
Forecasts turn out to be wrong.
Suppliers disappoint.
Markets change.
No technology and no management framework will create an organization where bad news never exists.
Organizational maturity is therefore not defined by the absence of problems.
It is defined by what happens when the first signs of a problem appear.
Who learns about it?
How quickly?
How accurately does the information travel?
Can someone say, “We don’t know”?
Can an employee escalate a risk without first proving that disaster is inevitable?
And when the decision finally reaches the right person, is there still enough time to change the outcome?
Let’s return to our engineer.
9:12 AM.
He sees the problem.
At that moment, the company has not lost anything yet.
It still has options.
That is when the real clock starts.
Not the clock measuring how long it takes to repair the technical issue.
Not the clock waiting for the supplier’s response.
Not the clock counting down to the next meeting.
The clock measuring how long it takes for the information to reach someone who can make the necessary decision.
And perhaps leaders should measure not only how quickly their companies solve problems.
But how quickly their companies are willing to admit that a problem exists.