The Brief

Welcome

Most leaders believe they protect their teams by absorbing difficulty. They shield, they filter, they delay the hard conversations in hopes of finding a better moment. This week examines what actually happens in organizations when leaders operate this way, and what becomes possible when they do the opposite.

Big Idea

A problem that one person avoids remains one person's problem. A problem that a leader avoids becomes the team's problem, often in a form that is larger, more entrenched, and harder to address than it would have been at the start. The calculus is different for a leader because the cost of avoidance does not stay contained. It compounds. Quietly. This is the compounding effect of leadership avoidance. The underperforming team member who is not confronted early becomes a drag on the entire group for months. The strategic misalignment that is not addressed in the first quarter becomes a crisis by the third. A culture of hiding bad news, once established, does not self-correct. It deepens until the gap between what the leader believes and what is happening on the ground becomes so wide that even a willing confrontation cannot close it without significant damage.

Research Nugget

Research on organizational silence shows that widespread withholding of employee input about problems compromises organizational decision-making and impedes change processes. The mechanism: problems do not disappear when unaddressed. They compound silently until they reach catastrophic scale. When organizational cultures punish the surfacing of problems, the information needed for effective leadership decisions is withheld. The result is that managers may not recognize emerging threats until they become crises.

Alan Mulally became CEO of Ford Motor Company in September 2006 when the company was losing $12B+ annually with junk-rated debt and bankruptcy openly discussed. The financial crisis was real, but the deepest problem was organizational. Ford's leadership culture had become so adversarial that surfacing bad news made you a target. Different divisions used different data to tell different stories. The company was failing while its own leadership team pretended everything was fine. Mulally, an outsider from Boeing, replaced the entire meeting structure with a weekly Business Plan Review where every senior executive reported status using a color-coded system: green (on track), yellow (at risk with plan), red (off track without solution). The rules were simple: no BlackBerrys, no side conversations, no blaming. If someone had a problem, the room's job was to help solve it, not exploit it. For weeks, every slide was green despite $12B losses. Then Mark Fields, president of Americas, coded a slide red. The Ford Edge had a suspension problem threatening the launch. Fields had changed the color knowing it might end his career. The room went silent. Mulally started clapping and asked one question: "Who can help?" An engineering executive immediately offered data on a similar issue. The problem was addressed. The launch was saved. The following week, more red and yellow slides appeared. Within months, the culture had shifted entirely. Problems were surfaced early, at manageable scale, by people who understood that identifying difficulty was a contribution to the team. Ford became the only one of the three major American automakers to avoid a government bailout during the 2008 financial crisis. By 2009, the company posted a $2.7B profit. What Mulally built was not a system for solving problems. It was a system for making problems visible before they became unsolvable.

Application

Build conditions for early confrontation:

Make honesty testable: The last person who delivered bad news: what actually happened to them? Were they sidelined? Overlooked for promotion? This is the real culture, not what the leader says.

Create forums for status: Regular venues where people report honestly. Business Plan Review format: all present, same format, no pre-meetings. Consistency matters.

Separate person from problem: Norm that says: surfacing a difficulty is a contribution to the team, not a reflection on the person who surfaces it.

Create proportional consequences: Consequences for hiding difficulty should be as visible and serious as consequences for causing it. If someone gets fired for missing a deadline but quietly sidelined for hiding bad news, you have told the room which one matters.

Build feedback loops: Watch what happens after someone surfaces bad news. If the person improves, promotes, and is seen as credible afterward, you are building a culture of visibility. If they disappear, you are building a culture of silence.

Reflection

What problem are you letting grow right now by not creating conditions for it to be surfaced?

Quick Hit

Speeches do not change culture. Systems do.

👉 Read the full essay: The Problem You Let Grow