A VP of engineering at a midsize software company once described a pattern he had noticed in every all-hands meeting with the executive team. The moment the CEO started talking, people stopped asking questions. Not because the CEO was overbearing or closed off. The CEO was confident in a way that felt conclusive. Every concern had already been addressed. The plan was clear. He described it years later as the organizational equivalent of a room where someone had already cleaned up: nothing seemed to need doing, so nobody did anything. He told me this about eighteen months before the company's flagship product missed a full category shift that had been visible to half the product team for two years. The information existed, but never made it into the right room.

The Signal That Produced the Leader

At every level below the C-suite, one behavior gets rewarded more consistently than almost any other: appearing to already have the answer. Preparation, crisp delivery, no visible uncertainty in areas where you should know. The people who deliver that signal most convincingly tend to advance. Over a decade or more, they learn that looking like they know is a measurable career asset, and they get better at it.

The problem this creates at the top is more ordinary than most leadership frameworks suggest. It does not show up as arrogance and rarely looks like a behavior problem. What happens is that the signal a senior executive sends when projecting certainty in a room tells the organization which conversations are worth having. Certainty at the top does not say "we can handle what comes." It says the leader has already accounted for what is coming. The layer below adjusts accordingly. Surfacing a problem that contradicts the leader's read is not just politically risky. It is socially awkward in a deeply ordinary way. The person speaking ends up implying the leader is wrong. Most people calculate whether the problem is worth that friction. Most of the time, they decide it is not. The problem sits there and ages.

Projecting certainty is a behavior optimized for external credibility. Boards respond to it. Investors use it as a proxy for sound judgment. Applied internally, it sends a different kind of signal about which conversations are welcome and which ones will cost the person having them. Organizations read that signal accurately. What gets adjusted is the honesty of what travels upward.

Why the Behaviors Do Not Change at the Top

Harvard Business Review published research in April 2026 documenting this dynamic directly. Leaders who project authority through decisiveness, who have answers ready for every question, who jump in to improve ideas as they surface in meetings, were consistently rated lower on decision quality by the people working closest to them. The finding was not about competence. Those behaviors changed the quality of information flowing to them, and that changed the quality of what they decided.

What makes this durable as a problem is that the external criteria for senior leadership still reward these behaviors. Boards prefer confidence. Investors read visible doubt as risk. The evaluation mechanisms that exist for senior executives largely measure outcomes and stakeholder perception, not information quality or the organizational conditions for honesty. So senior leaders are being evaluated externally by one set of criteria and undermining themselves internally by meeting those criteria every day in the rooms that matter most.

What a Different Kind of Room Looks Like

In practice, the clearest version of a high-information culture at the senior level is a leader who opens a review by asking what she does not know yet, rather than orienting the room around a framework she has already settled on. When a forecast gets missed, whether the executive responds with curiosity or with an explanation prepared before the meeting tells the organization whether the problem was worth mentioning sooner. That response is worth considerably more than any quarterly goal as a signal about what the room is for.

None of this is a large behavioral change. The structural effect is disproportionate to the size of the shift, because what changes is the calculation happening one and two levels below. If people in your organization have evidence that you receive inconvenient information without managing the messenger, they will bring you more of it. The picture you make decisions from becomes more complete. Problems surface smaller and earlier. The gap between what is actually happening and what the leadership team believes is happening narrows over time instead of widening.

The people with the most accurate read on operational reality in any large organization are almost always the ones closest to where things are failing. Whether that picture makes it to the top has little to do with whether those people can get access to the senior leader. What decides it is whether they believe the senior leader actually wants to hear it. Most of them are watching for that signal constantly. The question is what they see when they watch.

The Development That Does Not Happen

Most organizations never explicitly ask incoming C-suite leaders to unlearn the behaviors that produced them. The promotion is the signal that what they did worked. The development infrastructure that shaped them for a decade below the C-suite reinforced exactly those behaviors. The leadership development that happens at the senior level, when it happens at all, tends to focus on external stakeholder management, board dynamics, or strategic thinking. It almost never addresses the specific mechanism by which projected internal certainty closes the rooms a senior leader most needs to keep open.

The reason this lives at the cultural level is that the organization built the leader. It rewarded those behaviors across hundreds of small moments over years and now treats them as evidence it chose correctly. Somewhere in the layers below, someone who knows something important is running the calculation about whether saying it out loud is worth what it costs. Whatever they decide, the organization taught them how to make that decision.

When was the last time something genuinely surprised you, in a way that made you wonder how long it had been sitting somewhere before it reached you? That gap tends to be the most honest thing in the building.

If this landed somewhere specific, I am at zac@zacparkercoaching.com or you can find me at zacparkercoaching.com.

Chapter 10 of Agile Sucks! (When You Do It Wrong) covers the operational version of this argument. Five civilian contractors cut hostile incidents in a combat zone from over 800 per month to under 50 in twelve months. That result required leaders who stopped performing certainty and built structures where ground-level intelligence could travel upward without being filtered. How they did it is the argument the book is built around. You can find it at https://a.co/d/bdUxZLw.