The Telephone Problem
A CEO shares a clear strategic priority with the executive team. The executives translate it for their directors. The directors explain it to their managers. The managers pass it to their teams.
By the fourth translation, the original meaning is gone. Not because anyone was careless. Because nobody practiced the translation.
This is the cascade problem. It is not about communication. It is about capability. Leaders at every level need a method for translating strategic intent into language and action that makes sense for their specific team.
Why Traditional Cascade Fails
Most organizations cascade strategy through presentations. The senior team builds a slide deck. They present it at a town hall. They send a follow-up email with a PDF attachment. Then they wonder why nothing changes.
Presentations transfer information. They do not build understanding. Understanding requires leaders to wrestle with questions like: What does this priority mean for my team's daily work? What do we need to stop doing? What trade-offs does this create?
At ArcelorMittal, 710 leaders went through Lead the Endurance via Duke Corporate Education. The experience worked because leaders did not receive the strategy passively. They practiced translating strategic priorities into team-level decisions under real pressure. The result was leaders making decisions 30-40% faster because they understood how their piece connected to the whole.
The Three Translation Layers
Effective cascade requires translation at three levels:
Layer 1: Strategic intent to divisional priorities. The executive team takes each strategic pillar and defines what success looks like in their division. Not a restatement of the corporate goal. A specific, measurable divisional outcome that directly supports it.
Layer 2: Divisional priorities to team-level changes. Directors and senior managers identify what their teams need to start, stop, or change. This is where most cascade breaks down. Leaders restate the priority without identifying the specific behavioral or operational shift required.
Layer 3: Team-level changes to individual actions. Frontline managers connect the dots between the strategic shift and each person's daily work. This is the layer that makes strategy real.
The POW Framework in Action
The POW Framework (Purpose, Outcomes, Way Forward) gives leaders a repeatable structure for each translation layer.
Purpose: Why does this strategic priority matter for our team specifically? Not the corporate answer. The team-level answer.
Outcomes: What will be different in 90 days if we execute well? Not vague aspirations. Specific, observable changes.
Way Forward: What are the first three actions we take this week? Not a 12-month roadmap. Immediate, concrete steps.
When every leader at every level uses the same framework, the cascade stays coherent. The language may change at each level. The structure holds.
Practice Under Pressure
Reading about cascade is different from doing it. In Lead the Endurance, leaders face Shackleton's Antarctic crisis and experience what happens when strategic intent breaks down across multiple teams operating under pressure.
The simulation compresses months of organizational dynamics into hours. Leaders see their own cascade patterns — where they default to vague direction, where they assume understanding without checking, where they skip the translation work entirely.
This pattern recognition is what changes behavior back at work. Leaders who have felt the consequences of poor cascade in a simulation carry that awareness into every team meeting and strategy conversation.
Three Practices That Preserve Meaning
Practice 1: The Echo Test. After cascading a priority to your team, ask each person to explain it back. Not to recite your words. To describe what it means for their specific work. If the echo does not match the intent, the translation failed.
Practice 2: The Trade-Off Question. Every new priority implies a trade-off. Ask your team: What will we do less of to make room for this? If nobody can name the trade-off, the priority is an addition, not a shift. Additions get ignored. Shifts get implemented.
Practice 3: The 90-Day Checkpoint. Build a 90-day review into every cascade. Not a status update meeting. A genuine check on whether the strategic intent survived the translation. If it drifted, course correct early.
What Happens When Cascade Works
Organizations that get cascade right share a common characteristic: leaders at every level can articulate the connection between their team's daily work and the organization's strategic priorities. Not in corporate language. In their own words, specific to their context.
This alignment produces faster decisions, fewer escalations, and less wasted effort on work that does not support strategic priorities.
Read more about why strategy dies in the middle for the root cause of cascade failure. And explore the strategy cascade mistake every CEO makes for the most common executive blind spot. See how the executive development path builds cascade capability into leadership teams.
Read next: The Strategic Planning Mistake That Wastes Everyone's Time
[Book a discovery call](https://bookme.name/DougBolger/free-discovery) to explore how to build cascade capability into your leadership team.