The leadership team left aligned, energised, and clear on direction. Three months later, they're frustrated. Projects are running. People are busy. But something is off, the work doesn't quite connect to the decisions made in that room.

This is one of the most common patterns we see when working with mid-sized product companies. The problem isn't the strategy. It's what happens to it when you try to cascade strategy through an organisation. Somewhere between the boardroom and the people doing the work, something gets lost. The message travels, but it changes as it goes.

Something gets lost on the way down

Most leaders assume this is a communication problem. They run a town hall. They publish a strategy deck. They brief their direct reports and trust the message will carry. And it does carry, just not intact.

By the time the strategy reaches the teams actually building products, serving customers, or managing operations, it has been filtered through four or five layers of interpretation. Each manager has translated it through their own priorities, their own pressures, and their own understanding of what matters. The strategy hasn't been ignored. It's been rewritten, without anyone meaning to.

This is translation loss. And it's not a failure of communication, it's a failure of the system. Most organisations have no reliable way to check what version of the strategy actually arrived at each level.

Why strategy dilutes as it travels

The translation problem gets worse the more abstract the strategy is at the top. When leadership communicates direction in terms of ambitions and themes — "becoming more customer-centric," "accelerating growth in adjacent markets" — each layer below has to interpret what that means in practice. They fill the gaps with what they know. Their current priorities. Last year's targets. What got rewarded before.

Middle management sits at the most critical point in this chain. They are the translators. When they understand the strategy well enough to make real decisions with it, the cascade works. When they don't (and often they've been given the summary, not the substance) they convert strategy into tasks. And tasks are not strategy. They're activity without direction.

The gap between "what we decided" and "what people are doing" doesn't open all at once. It widens quietly, one layer at a time.

"The gap between what we decided and what people are doing doesn't open all at once. It widens quietly, one layer at a time."

What cascading actually requires

The assumption embedded in most cascade approaches is that clarity at the top creates clarity below. It rarely does. The people closest to the customer, the ones whose work will either deliver the strategy or not, need to be able to see their own work inside it. Not a summary of it. Not a theme. A genuine connection between what they do on a given Tuesday and what the organisation is trying to achieve.

That connection has to be built deliberately at each level. The senior leadership team can't do it alone, because they're too far removed from where the work actually happens. What they can do is create the conditions for it; by giving each layer enough substance, not just direction, to make the translation themselves.

Ownership is the other piece. A strategy that is handed down is a strategy someone else owns. The teams expected to deliver it will comply, but they won't commit. Real ownership forms when people have a hand in working out what the strategy means for them, when they're asked to translate it, not just receive it.

The practical test for this isn't a survey. It's a conversation. Ask someone three levels below the leadership team to describe the two or three things that matter most this year, and why. If their answer maps to your strategic priorities, the cascade is working. If it maps to last year's targets or their functional KPIs, you have a translation problem.

"Ask someone three levels down what matters most this year. The gap between their answer and yours is the size of your translation problem."

How to audit what's actually landing

When we work with leadership teams on this, we start with a simple diagnostic. Not a process review, not a culture survey; just structured conversations at different levels of the organisation, asking the same questions.

What are the two or three things we're trying to achieve this year? What does that mean for your team? What decisions have you made differently because of it?

The answers are rarely what the leadership team expects. Some teams are perfectly aligned. Others are operating on a version of the strategy that drifted away six months ago. A few are working hard on things that no longer connect to the current direction at all — not because they're disengaged, but because nobody closed the translation loop.

The audit isn't about accountability. It's about finding where the signal broke down so you can rebuild it. Closing those gaps before they harden into structural misalignment is considerably easier than trying to realign an organisation that has spent a year moving in the wrong direction.

The companies we've seen get this right treat cascading as an ongoing responsibility, not a one-time communication event. They build in checkpoints. They ask the uncomfortable question — "what do people three levels down actually think we're doing?" — before it becomes a crisis. That discipline is at the heart of making strategy stick.

Key takeaways

Strategy doesn't fail because it's wrong — it fails because it gets translated differently at every level of the organisation before it reaches the people doing the work.

Translation loss is a systems problem, not a communication problem. A town hall or a strategy deck doesn't close it.

Middle management is the most critical point in any cascade. When they have the substance to make real decisions, the strategy travels intact. When they have only the summary, they convert it into tasks. For a deeper look at why the execution gap opens in the first place, see Why Strategy Fails in Execution.

Ownership of strategy can't be assigned from above. It forms when people at each level work out what the strategy means for them — not just receive instructions.

The fastest way to audit your cascade is to ask someone three levels down what matters most this year and why. The gap between their answer and yours is the size of your translation problem.