What Doesn't Travel

There is something that happens to information as it moves up a hierarchy. It gets better.

Not more accurate. Better. The rough edges get smoothed. The uncertainties get resolved often by someone at the middle of the chain who cannot tolerate sending a message that says “we don't know.” The bad news gets softened, placed in context, accompanied by mitigation plans. The good news travels without caveats.

I call this altitude compression. By the time the picture reaches the executive, it has been filtered through multiple layers of interpretation, advocacy, and organizational self-preservation. What arrives is accurate in outline. But it is missing the texture: the specific friction points, the real blockers, the things everyone in the room on the ground floor knows and no one has said out loud to the person at the top.

The executive is then asked to make a decision.

What Gets Filtered

Understanding altitude compression requires understanding what each layer of the hierarchy actually does to information.

At the ground level, information is raw. A team knows that the deadline is impossible because the dependency from the other team has not materialized and probably won't. They know this specifically: which dependency, from which team, for which reason, and what the downstream effect will be if it does not arrive by when.

At the next level, this becomes: the team is flagging a risk on the timeline. The manager is working through it. We're monitoring.

At the next level: there's a dependency risk in Project X. The team is managing it.

At the executive level: we have some timeline risk in the portfolio that is being managed.

Four layers. One signal. What traveled: there is a risk. What did not travel: the specific nature of the risk, the reason it exists, whether the team managing it has the authority to address it, and whether “managing it” means anything actionable or just means watching the timeline slip.

Why the Hierarchy Compresses

Altitude compression is not primarily a function of dishonesty. It is a function of rational behavior inside a particular incentive system.

Most organizations punish bad news. Not explicitly: the leadership team would deny: this if asked. But implicitly: the person who brings the problem without the solution is seen as a problem. The person who surfaces uncertainty is seen as someone who cannot manage. The person who says “we don't know” is seen as someone who should know.

So the hierarchy learns to compress. Every level translates the difficult, uncertain, specific reality into something more manageable, more confident, more resolved-sounding than it actually is. Each individual compression is small and rational. The aggregate compression is profound.

The leader who has trained their organization to compress information has built a machine: that keeps them permanently surprised. Not because things go wrong suddenly, but because: the signal that things were going wrong was systematically filtered before it could reach them.

Knowledge and Authority Travel in Opposite Directions

There is a structural problem underneath altitude compression that makes it particularly difficult to solve: in most organizations, knowledge and authority travel in opposite directions.

The most specific, actionable knowledge about what is actually happening lives at the ground level: with the people doing the work, managing the dependencies, fielding the exceptions. The authority to act on that knowledge lives at the top.

This inversion is where execution dies. The person who knows what needs to happen cannot authorize it. The person who can authorize it does not know what needs to happen. Between them is a compression layer that makes the signal progressively less useful with each translation.

This is not a technology problem. It is not solved by better dashboards or more frequent reporting. It is solved by changing the decision architecture: moving authority closer to knowledge, and building the norms that allow unfiltered signal to travel upward safely.

The Three Things That Never Travel

Thirty years of diagnostic work inside organizations has produced a short, consistent list of the things that fail to travel up the hierarchy regardless of how well-intentioned the people involved are. Understanding each one is the beginning of being able to design against them.

Uncertainty. By the time a status report reaches a senior leader, uncertainty has been converted into confidence. Not because anyone lied: because the organizational norm punishes the admission of not knowing. People who deliver status with appropriate uncertainty are perceived as unprepared. People who deliver status with false confidence are perceived as competent. The norm selects for the latter. Leaders receive confident assessments of situations that are actually uncertain, and make decisions accordingly.

Contradiction. Most complex organizational situations contain genuine contradictions: facts that point in different directions, stakeholders with legitimately incompatible needs, tradeoffs that have no clean answer. As information travels upward, these contradictions get resolved: not because someone figured them out, but because the format of a status report, a briefing slide, or an executive summary does not accommodate them. The ambiguity gets edited out. The leader receives a clear picture of a situation that was never actually clear.

Context. The specific conditions that make a piece of information meaningful: the relationship history, the operational constraint, the political dynamic that explains why something is harder than it looks: rarely survive translation. A number without its context is not information. It is data. Leaders who receive data without context make decisions that seem rational given what they were told and are inexplicable to the people who live in the context they were not told.

None of these failures are fixed by better communication training or more rigorous reporting requirements. They are structural. They are fixed by structural interventions: changing the norms around what is safe to say upward, changing the formats that information travels in, and, most importantly, changing the behavior leaders demonstrate when they receive information that is uncertain, contradictory, or contextually complex.

What the Builder Does

The builder-leader does not wait for good information to arrive. They go get it.

They walk the site. Not to manage: to observe. They sit in the meeting where the real conversation happens, not the briefing that was prepared for them. They ask the question: that creates permission to answer honestly: “What are you not saying in the status report: that I should know?”

And then, this is the harder part, they respond to unfiltered information in a way that makes it worth bringing next time. They do not shoot the messenger. They do not immediately problem-solve in a way that makes the messenger feel responsible for the solution. They receive the information and they act on it in a way that demonstrates: bad news delivered early is more valuable here than good news delivered late.

The leader's reaction to unfiltered information determines whether it keeps arriving. That is the real altitude control.