What if a company’s survival depended on its ability to listen to… bad news? The question sounds counterintuitive. We tend to imagine that an organization thrives because it piles up good news: rising numbers, satisfied customers, projects delivered on time. And yet one of the most influential leaders in the history of tech argued the exact opposite. For Bill Gates, the former CEO of Microsoft, his most important job was neither setting the strategy nor recruiting the best talent: it was making sure that problems and bad news were never ignored.
This idea, which sounds like a provocation, actually sits at the very heart of Lean thinking. It radically shifts an organization’s relationship to error, to signaling, and to continuous improvement. And it has very concrete implications for how you lead a technical team.
An ignored problem is a lost opportunity
Bill Gates’ reasoning fits in a single sentence: a problem that goes unreported is a missed opportunity for the company to improve itself and its product. Every bug raised, every friction a customer describes, every malfunction observed in the field is a valuable piece of information. It’s a signal that points, for free, to a place where the product or the organization can get better.
Conversely, a problem that stays silent doesn’t disappear: it keeps existing, simply out of sight. It degrades the user experience, erodes trust, and often ends up resurfacing later in a form that’s more expensive to fix. According to Gates, the stakes are anything but trivial: a company’s ability to surface and address its problems directly determines its survival in the medium and long term. An organization that doesn’t learn from its failures condemns itself to repeating them, while its competitors capitalize on theirs.
Three principles for surfacing problems
Encouraging bad news can’t simply be decreed. It requires building, over time, an environment where reporting a problem is seen as a useful act, not as taking a risk. Bill Gates identified three pillars.
Thank the person who reports, never blame them
The first reaction to a reported problem is decisive. By itself, it determines whether the person, and everyone watching the scene, will do it again in the future, or stay quiet. That’s why you must thank, encourage, and reward whoever raised the problem.
At this stage, it’s essential not to hunt for someone to blame and to stay supportive. The goal isn’t to name a culprit, but to learn from the situation. It’s also worth keeping in mind that at the root of a problem there is almost always a human being who wasn’t set up to succeed: a lack of training, a poorly designed tool, an ambiguous process, an unsustainable workload. Blaming that person means treating the symptom while ignoring the cause, and it’s a guaranteed way to make sure no one dares to raise their hand next time.
Give teams the means to solve
Surfacing a problem is pointless if the organization doesn’t give itself the means to address it. The second principle is to allow teams to analyze the problem, experiment, and find solutions on their own.
This implies a deep shift in posture: every employee should be trained and encouraged to become a driver of problem solving, at their own level. Solving problems shouldn’t be the preserve of a handful of experts or of the hierarchy, but a skill spread throughout the entire organization. It’s most often the role of leaders and team coaches to lead the way: training continuously on these practices, supporting the first experiments, and above all demonstrating concretely the value they produce. A manager who solves problems in place of their team deprives it of the chance to learn; a manager who equips it to solve them makes it lastingly stronger.
Welcome problems positively
The third principle is the most disorienting: you have to welcome problems positively. As counterintuitive as it may seem, having problems is good news. It means the organization can see, that it’s connected to the reality of the field, and that it holds the raw material for its own improvement.
The real alarm signal is the opposite: silence. You should start to worry when no problem is being reported anymore, not because they’ve disappeared, but because they’ve become invisible, smothered by fear, indifference, or habit. Taiichi Ohno, the architect of the Toyota Production System, summed it up in a phrase that has become famous:
Having no problems is the biggest problem of all.
An organization with no apparent problems isn’t a healthy organization: more often than not, it’s an organization that has stopped looking.
A culture, more than a method
What Bill Gates describes maps exactly onto the logic of Lean: making problems visible so they can be solved, rather than hiding them to preserve an illusion of control. But this philosophy doesn’t boil down to a toolbox or a ritual added to the calendar. It’s first and foremost a culture, one that’s built in the consistency between what you say and how you react, day after day.
The test is simple: the next time a member of your team comes to report a problem (a production incident, technical debt that’s slowing things down, an unhappy customer), watch your first reaction. Do you instinctively look for someone to blame, or do you thank the person for giving you, ahead of time, the chance to improve? It’s in that moment, and not in the speeches, that an organization’s real ability to learn from its mistakes is decided.