Bad news early is useful.
Bad news late is expensive.
We want people to raise issues while there is still time to act.
Why this matters
The cost of a problem grows the longer it stays hidden. A schedule slip caught in week one is a conversation; the same slip caught in week eight is a crisis. A budget overrun named at 20% is a correction; named at 80% it is a board conversation.
But people only raise issues early when they believe the response will not punish them. The phrase “tell the truth early” is not a demand on the speaker. It is a commitment from the listener. What a leader does in the first sentence of a hard conversation determines whether the next one happens at all.
What it looks like in practice
A frontline contributor notices a vendor performance issue that has been quietly degrading for three weeks. They have not raised it because they expected the response would be “why didn’t you catch this sooner.” They open the Issue Escalation Note and write:
- The issue.
- The impact (what gets worse if we do not act, and how fast).
- The options they see.
- Their recommendation.
- What they need.
They send it to their manager. The manager opens with the Session 4 Good response:
“Thank you for raising this now. What is the impact? What are our options? What do you recommend?”
That exchange does two things: it solves the immediate problem faster than waiting would have, and it teaches every person within earshot that early bad news is welcomed here.
What it looks like when violated
The most damaging failure is not ignoring bad news. Most leaders do not do that. The damaging failure is the first sentence response that signals retaliation:
- “Why did you let this happen?”
- “Why didn’t anyone catch this sooner?”
- “Whose fault is this?”
The information is still received, but the speaker silently decides not to raise the next one. Two months later the company has a “surprise” that was actually a known signal three people chose not to share.
A second, quieter failure: a leader receives the news well in the moment but later, in private, expresses frustration about who brought it. That story always travels. The frontline person who brought the first issue stops bringing the next one.
How to apply it this week
- Notice your first sentence when someone brings you something hard this week. If it begins with “why,” rewrite it in your head before you finish.
- When you receive an early flag, send a one-line follow-up: thanks for raising this. In writing. So it travels.
- If you are the person with the hard truth: use the Issue Escalation Note pattern. It gives the receiver a structure that makes the good response easier.