Good strategy. Unbearable burdens
This edition examines what happens to a strategic decision as it travels through an organization: why it accumulates complexity at every layer, loses coherence along the way, and arrives at implementation as something heavier and less recognizable than what was originally decided.
How strategy accumulates complexity and loses coherence as it cascades through the organization
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 fail to address systemically. Its consequences accumulate slowly, remaining 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, memory, and capacity to act. Those demands don't simply travel downward — they accumulate. At each layer of the organization, the original decision gets interpreted, adapted, and added to. What begins as a clear and simple strategic intent progressively becomes more complex and loses coherence as it moves through the cascade. And the full weight of everything the cascade has produced lands most heavily on the people closest to implementation.
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 or 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 root cause
The root cause is the failure to account for how decisions transform as they cascade downward, layer by layer. Bad decisions at the top can certainly make things worse, but they are rarely the main culprit.
Consider how a strategic decision actually transforms as it moves through an organization. At the executive level, it is simple: a direction, a bet, a priority easily expressed in a single sentence regardless of how much thinking went into it. At every level below, that decision must be interpreted, resourced, and translated into action, with each layer resolving questions the level above left open while adding its own. As these rolling waves of implementation cascade downward, that crisp one-line strategic intent has been elaborated through multiple layers — each acting responsibly within its own scope — into a dense web of adjustments, edge cases, and unresolved tensions that may no longer resemble what was originally intended.
This is where coherence degrades. Each layer's interpretation is locally rational — it makes sense given what that layer knows, what constraints it operates under, and what decisions it has authority to make. But local rationality does not preserve global coherence. What looks like a reasonable adaptation at one level compounds with equally reasonable adaptations at the next, until the cumulative effect is a strategy that has quietly become something different from what was decided. No single layer made an error. The cascade itself produced the distortion.
Complexity accumulates through the same mechanism. Each layer doesn't simply pass the strategic decision downward — it adds to it. It generates new sub-decisions, new priorities, new constraints, new exceptions. The people closest to implementation are not receiving a simplified version of the original strategic intent. They are receiving the full weight of every interpretive layer above them, compressed into directives that may feel arbitrary, contradictory, or disconnected from any strategic logic they can discern. The original decision was simple. What reaches them is not.
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, by treating a structural failure as an individual deficiency.
No easy structural solutions. But disciplines that help.
Focus on what people need to know
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.
Invest 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.
Treat 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 seldom done.
Ensure that decisions travel with their original context
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 strategic intent across the cascade is essential because it's what gives the decision its meaning. Doing this 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.
Establish an ongoing upward feedback loop
The strategy cascade is almost always treated as a one-way street, flowing from executive intent down to frontline execution. However, complexity multiplies precisely because there is no systematic mechanism for reality to travel back up the chain. When a crisp, one-line strategic directive is elaborated across multiple layers into a dense web of adjustments, the people closest to implementation need a structured, psychologically safe channel to push back. Without a formal upward loop — where teams can explicitly signal, "This adaptation requires 400 hours of compliance work that directly conflicts with our primary objective" — executives remain insulated from the actual cognitive cost of their choices. A resilient strategy cannot just be a downward broadcast; it must be an ongoing, bidirectional conversation.
Align incentives and accountability
We frequently ask leaders to act responsibly within their scope, yet we fail to notice that their implicit incentives drive the very complexity we criticize. Middle and senior managers are rarely evaluated on how effectively they shield their teams from cognitive overload or how strictly they prioritize incoming directives. Instead, corporate performance indicators almost exclusively reward visible output, project checkmarks, and a superficial display of "agility". Expecting leaders to slow down or curate information out of sheer goodwill is wishful thinking. As long as we only reward managers for pushing out more work and hitting fast deadlines, a company will naturally keep moving faster and getting more chaotic. If we want leaders to slow down and simplify things, we have to change their bonuses and job descriptions to reward them for doing so.
Set up practical governance filters
To give these disciplines operational teeth, organizations need practical governance filters that introduce deliberate friction into the rollout process. One way to do this is having a "Complexity Budget" whereby leaders cannot introduce a new strategic priority, change a process, or launch a new project without first canceling or pausing an old one. Another way is to create "Gatekeepers" — internal editors whose only job is to block unnecessary corporate updates and simplify complicated instructions before they are deployed.
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.
Alexander Spradling, PhD, is an organizational consultant and executive coach based in Austin, Texas. He writes Why Organizations Misbehave.