Reward the Bad-News Messenger
Surface problems early by making disclosure safer than concealment
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 98%
This framework treats problem visibility as a cultural incentive system. The familiar rule not to bring a problem without a solution sounds constructive, but it implicitly tells employees to hide important issues whenever they cannot solve them alone. Because people naturally avoid being associated with failure, leaders must make accurate early disclosure professionally safer and more rewarding than silence. Establish clear escalation thresholds, thank the messenger, separate reporting from blame, and bring collective resources to unresolved problems. Leaders should still expect facts, follow-through, and responsible investigation, but they should not condition awareness on a finished answer. Measuring detection delays and examining late surprises reveals whether the culture genuinely supports bad news. Faster visibility increases the time available to contain damage and develop a solution.
Origin
Extracted from Masters in Business through Ben Horowitz’s explanation of why healthy companies discuss problems freely and openly.
Core principles
- 01Problems become more expensive when leaders learn about them late
- 02Requiring a solution can suppress disclosure of unsolved problems
- 03Employees avoid bad news when association with failure carries a penalty
- 04Leaders must reward early, accurate escalation
- 05Open discussion accelerates collective problem solving
How to run it
- 1
Remove the Solution Gate
Tell employees they may escalate material problems even when they do not yet know the answer.
Pro tip Ask for known facts, uncertainty, impact, and the next investigative action.
Watch out Do not replace the solution gate with an expectation-free complaint channel.
- 2
Define Early-Warning Triggers
Specify which customer, financial, legal, security, personnel, or operational signals require immediate disclosure.
Pro tip Use examples from previous late surprises to make thresholds concrete.
Watch out Ambiguous thresholds encourage employees to wait for certainty.
- 3
Reward Accurate Disclosure
Thank and protect employees who surface credible problems early, especially when the information is uncomfortable.
Pro tip Praise early escalation publicly while handling sensitive details privately.
Watch out Token praise will not work if the messenger is later penalized.
- 4
Separate Message From Blame
Assess responsibility independently from the act of reporting so employees do not equate disclosure with self-incrimination.
Pro tip Begin incident discussions with containment and facts before accountability.
Watch out Avoid promising immunity for misconduct or deliberate concealment.
- 5
Mobilize Collective Help
Assign expertise and decision authority to investigate and solve the surfaced problem quickly.
Pro tip Give the messenger a role in the response without forcing them to solve everything alone.
Watch out Repeated escalation without visible action teaches employees that reporting is pointless.
- 6
Audit Detection Delays
Review major incidents to determine when the problem first became knowable and when leadership actually learned about it.
Pro tip Track the delay as a cultural health indicator.
Watch out Do not focus solely on the final technical failure and ignore reporting behavior.
In the wild
A customer-success manager notices repeated failures but cannot identify the engineering cause. Instead of waiting to propose a complete fix, the manager reports the evidence, potential customer impact, uncertainty, and next diagnostic step. Leadership assembles the right technical and commercial owners before the issue becomes a broad outage or renewal crisis.
→ The company gains time to contain the risk and solve it collaboratively.
Common mistakes
Demanding Answers Before Disclosure
Employees who cannot solve a problem independently will delay or suppress information that leadership needs.
Punishing the Messenger
Blaming employees for surfacing uncomfortable facts teaches the entire organization to conceal future problems.
Ignoring Reported Problems
If escalation produces no visible response, employees learn that the personal risk of disclosure has no corresponding benefit.
Is it for you?
Best for
It is best for organizations where surprises reach leaders late or employees routinely soften and conceal negative information.
Not ideal for
It is not ideal for excusing careless escalation that lacks facts, ownership, or reasonable investigative effort.
From the transcript
“don't bring me a problem unless you have the solution.”
“the faster you know it, the better it is.”
“there has to be some kind of like reward in the culture for doing that.”
From the episode
Ben Horowitz Discusses Culture and Success
Ben Horowitz