How good strategic decisions create unbearable burdens

 This article is a companion piece to another article published here as well: "Cross-functional collaboration is hard. Here's why".

If you have ever felt overwhelmed by the volume of information your organization expects you to absorb, the pace at which it changes, and the difficulty of knowing what actually applies to your work — you are not struggling with a personal limitation. You are experiencing the predictable result of a structural problem that most organizations silently acknowledge, treat as inevitable, and haven't found a way to address systemically — in part because its consequences accumulate slowly and are difficult to measure until they become impossible to ignore.

Call it the complexity tax. 

Every time a company expands its product portfolio, shifts its strategic priorities, or updates how it does things, it generates demands — on people's attention, their memory, and their capacity to act — that have to land somewhere. Those demands touch every level of the organization, but they don't land equally. The people closest to implementation bear the full weight of what the entire cascade has produced.

The issue isn't the original strategic decision. It's that the cost of implementing it wasn't accounted for.

Information volume alone does not explain the complexity tax. Organizations have been grappling with volume for decades — better intranets, better knowledge management systems, better onboarding, and more recently, AI. Those tools help, and they aren't enough.

What makes this structurally different now is the combination of three things happening simultaneously:

• Volume has increased. 

• The rate at which information changes has increased. 

• And the coherence of those changes — the degree to which people can discern a pattern, anticipate what comes next, and build a stable mental model — has decreased. 

Any one of these is manageable. The compound effect is not.

High volume without rapid change means people have a lot to learn, but they can learn it once and rely on it. Rapid change with a coherent logic means the pace is demanding, but people can track the pattern and adapt. It is the loss of coherence that is the most corrosive variable — because it undermines the investment people make in learning. 

When people don't understand the rationale behind a change, when there is no reliable signal for when things will stabilize, and when the implications for their own work remain unclear, the rational response is to hold new information lightly, and possibly skeptically. Calling that 'resistance to change' mistakes a rational response for a character flaw. It is actually adaptation to an environment where what was true last month may not be true this month.

The real root cause is a systematic failure to account for how decisions transform as they are cascaded downward — not in a single leap, but gradually, layer by layer. Bad decisions at the top can certainly make things worse, but they are rarely the origin of it.

Consider how a strategic decision actually transforms as it moves through an organization. At the executive level it is clean — a direction, a bet, a priority, expressible in a single sentence regardless of how much thinking went into it. At every level below, that decision has to be interpreted, resourced, and translated into action, each layer resolving questions the level above left open and adding its own. By the time it reaches the people closest to implementation, the original one-line strategic intent has been translated, refined, and elaborated through multiple layers — each acting responsibly within its own scope — into a web of decisions, adjustments, edge cases, and unresolved tensions that may or may not still reflect what was originally intended.

A common organizational response to this challenge is to ask employees to be more agile, more resilient, more tolerant of ambiguity, and more comfortable with uncertainty. These are valuable skills, and worth developing. But they do not address the underlying cause. They make the burden more bearable without reducing it — treating a structural failure as an individual deficiency.

There are no easy structural solutions. But there are disciplines that help.

The first is distinguishing between what people need to know and what the organization feels compelled to share.

These are not the same thing. A great deal of information travels downstream not because employees need it to do their work, but because sharing creates the feeling of alignment without requiring the harder work of prioritization. Someone at a senior level has to take responsibility for that translation: not cascading raw complexity downward, but deciding what people actually need in order to navigate from where they stand.

The second is investing in orientation rather than information transfer. Employees do not need to know every update.

They need a stable enough mental model to know where they are when things change — a reliable sense of direction that doesn't collapse every time an update arrives. And they need enough context to exercise judgment when the instructions run out. The difference is between giving someone a directory and giving someone a map. The directory lists everything; the map tells you where you are.

The third is treating pace as a leadership choice.

Not every change needs to happen as fast as it does. Organizations often move faster than market conditions actually require, because internal momentum has its own logic — each level responding to the urgency of the level above it, the whole system accelerating without anyone choosing acceleration. Slowing down is not always possible. But accounting for the cumulative cognitive cost of the pace you set — for the people who bear it — is always possible, and rarely done.

The fourth is ensuring that decisions travel with their original context — not just the context each layer has received, but the strategic intent that gives the decision its meaning.

When context is filtered and reframed at every level to fit local reality, what reaches the people closest to implementation may be accurate at each step and still be far from what was originally intended. Preserving that original intent across the cascade requires deliberate and sustained effort at every level, not just at the point where the decision is first communicated.

That effort extends horizontally as well as vertically. As decisions move down they also move across functions, each of which interprets and implements the directive through its own lens. Functions need to align around a shared understanding of what they are collectively trying to achieve, how their work connects, and how conflicts will be resolved — before implementation begins. Both are addressable — but only if they are treated as leadership responsibilities rather than communication problems.

The structural conditions that make cross-functional collaboration possible — or impossible — are addressed in a companion article: "Cross-functional collaboration keeps failing. Here's why."

The complexity tax will not go away. The conditions that generate it — competitive pressure, the need to adapt, the genuine desire to improve — are not going away either. But it can be recognized and, to some degree, managed. That begins with a shift in how leaders think about the cost of a decision. The cost is not only what it takes to make it. It includes what it takes to implement it.