Most strategy rollouts move in one direction. Senior leaders build the strategy. They cascade it down. Each level of management presents what they were given to the level below.
That's not deployment. That's broadcasting.
Catchball is the ritual that's supposed to make strategy deployment actually work. The strategy gets thrown back and forth between leadership levels — questioned, challenged, refined — until each layer can say in their own words why this strategy is the right strategy and what they're committing to do about it.
Most organizations have heard of catchball. Few practice it. The ones that do produce a different kind of leadership team.
What Catchball Actually Is
Catchball comes from Hoshin Kanri — the Japanese strategy deployment method developed at Toyota and refined across lean manufacturing companies for decades. The name describes the practice: leaders throw the ball of strategy back and forth, level by level, until everyone has caught it.
The mechanic is simple. Senior leadership drafts the strategic intent — the high-level direction and the targets. They send it to the next level down: VPs and division leaders. Those leaders don't just receive it. They wrestle with it. They translate it for their part of the organization. They ask hard questions back: Is this target realistic given the constraints we see? What resources would we actually need? What could you not be considering?
Senior leadership receives those questions and responses. They adjust. They send it back down again. The next round goes from VPs to directors. Same dynamic. Same questions. Same refinement.
By the time the strategy reaches frontline managers, it has been thrown and caught five or six times. Each level has stress-tested it. Each level has shaped it. Each level has skin in the result.
For a deeper look at why one-direction cascade fails, why your strategy communication plan fails before the first all-hands maps the gap between delivery and internalization.
Why Most Organizations Skip Catchball
The reason organizations skip catchball isn't that they don't know about it. The reason is that catchball is slow, uncomfortable, and politically risky.
It's slow because real catchball takes weeks, not days. Each round of throw-and-catch produces real questions that require real answers. Senior leaders have to defend their thinking. Middle leaders have to come up with answers, not just objections.
It's uncomfortable because it requires senior leadership to be wrong publicly. The original strategy almost never survives catchball intact. Targets get adjusted. Sequencing changes. Sometimes the strategic priority itself shifts. For senior leaders accustomed to "decide and deploy," this feels like dilution.
It's politically risky because catchball reveals which leaders can actually engage with strategy and which can only execute orders. The directors who push back with substance become visible. The ones who only echo the cascade also become visible. Catchball is a leadership development ritual disguised as a planning ritual.
Most organizations choose speed and comfort over alignment. They pay for that choice when execution stalls six months later — and they don't trace the stall back to the missing catchball.
What Real Catchball Looks Like
A leadership team practicing real catchball does four things most organizations don't.
They build in time for pushback. Catchball can't happen in a single 90-minute meeting. It requires multiple sessions across multiple levels with time between for the questions to deepen. Organizations that do catchball well plan 4-8 weeks for the process. Organizations that don't usually try to compress it into one offsite and end up with a rebranded cascade.
They make pushback expected, not optional. When a director receives the strategy from their VP, the expectation is that they'll come back with concrete questions and proposed adjustments — not just understanding. The ritual itself signals that pushback is the contribution, not the obstacle. Why teams resist change and what resistance really means names the dynamic at work: when you don't invite pushback, you get compliance instead of commitment.
They train senior leaders to handle pushback well. This is the piece most organizations miss. If a senior leader gets defensive when challenged, the catchball stops. The next round produces fewer questions, and the round after that produces none. The strategy gets accepted on the surface and ignored in practice. The leadership skill catchball requires — to receive challenge as contribution rather than threat — has to be developed deliberately.
They write the questions down. The questions that come up in catchball are the questions that need answers if the strategy is going to work. Treating them as one-time discussion points loses 90% of their value. Organizations that practice catchball well capture every substantive question and either answer it explicitly or carry it forward as a known unknown the strategy depends on resolving.
The POW Framework — Power of Why — was built to make catchball happen at scale. It structures the conversation around three questions: Why does this strategy matter? What outcomes are we committing to? What's our way forward? Each level answers these questions in their own context. Each level's answers feed back up. The ritual produces alignment because it produces the conversations that alignment requires.
What Happens When a Leadership Team Builds the Capability
ArcelorMittal partnered with Duke Corporate Education to deploy strategic alignment across 710 leaders. The challenge wasn't intellectual — these leaders were highly capable. The challenge was that strategic intent at the top wasn't translating into coordinated action across geographies and business units.
After leaders went through Lead the Endurance, decision speed improved 30-40%. The improvement didn't come from removing checks and balances. It came from leaders who had wrestled with the strategy themselves — who could explain why a decision aligned (or didn't) without checking up the chain.
That's what catchball builds when it works: leaders who have caught the ball and made it their own. They don't need permission to apply the strategy in novel situations. They don't need talking points to explain it to their teams. They've already had the conversations that produce ownership.
The Connection to Strategic Patience
Catchball asks senior leaders to slow down at the start so the organization can move faster afterward. That trade-off is hard to accept in cultures that reward speed of decision over speed of execution.
But the math is straightforward. A strategy that is executed cleanly because every level owns it produces results faster than a strategy that has to be re-explained, re-clarified, and re-litigated as it moves through implementation. The time invested in catchball is time saved during execution — and the savings compound as the strategy moves through the organization.
How to cascade strategy without a slide deck walks through the conversation method that replaces presentation cascades with discovery-based catchball. The method is simple. The discipline to actually do it — including the part where senior leaders accept being wrong on details so they can be right on direction — is what most organizations lack.
Where to Start
If your organization has never practiced catchball, don't try to introduce it across the whole strategy at once. Pick one strategic priority — preferably one where execution is currently stalling — and run a real catchball process on that one priority.
Three rounds. Senior leadership to VPs. VPs to directors. Directors to managers. With substantive pushback expected and captured at every level. With senior leadership willing to adjust based on what they hear.
The leaders who emerge from that process changed are the leaders worth investing in further. The executive development path builds the muscle catchball requires — the muscle to receive challenge, hold long-range intent, and adjust without losing direction.
If you've been running cascades and wondering why execution lags, the answer might be that the strategy never got caught.
Read next: Everyone Agrees on Strategy, Then Executes Differently