Table of Contents
Introduction
Why does the same strategy so often sound completely different depending on whether you ask the boardroom or the frontline team delivering it?
Strategy on a slide and strategy on the floor are rarely the same thing, and the distance between them isn't usually anyone's fault in particular — it's a structural gap, the natural result of a plan written at one altitude and executed at another. This raises the real question: if closing that gap once isn't enough to keep it closed, what actually is?
In this article, we'll walk through why the two versions of a strategy drift apart, why the gap reopens even in organizations that have run a good alignment process before, and the recurring habit we call the alignment code that keeps the drift in check.
Two Versions of the Same Strategy
Ask a leadership team to describe this year's top priority and you'll get a crisp, well-rehearsed answer, usually close to what's printed on the strategy deck. Ask the frontline team responsible for delivering it the same question, and the answer is often recognizable but meaningfully different — filtered through whatever got communicated down the chain, reinterpreted by a middle layer that had its own priorities to protect, and adjusted again by whatever actually turned out to be operationally possible.
"Leadership tends to assume its version is the one being executed, right up until the results come in and don't match."
Why the Gap Reopens Even After It's Closed
Organizations that run a genuine catchball process can close this gap for a planning cycle — that's exactly what catchball is built to do. What catches people off guard is how quickly it reopens. Alignment isn't a milestone you hit once; it's a state that has to be maintained against constant drift, because everything underneath the plan — headcount, constraints, the competitive picture, even which manager owns which initiative — keeps moving after the rollout meeting ends.
Closed Once vs. Maintained Continuously
| Aspect | Closed Once | Maintained Continuously |
|---|---|---|
| Mechanism | A single rollout or catchball cycle | A recurring check, built into the calendar |
| When drift is caught | At the next planning cycle | Within weeks |
| Typical discovery point | A missed number | A routine conversation |
Factors That Widen the Gap Fastest
- Middle-Management Turnover: New managers reinterpret priorities without the original context.
- Shifting Constraints: Headcount, budget, or competitive pressure changes after the plan is set.
- No Recurring Check: Without a scheduled re-verification, drift compounds silently.
- Reluctance to Reopen a "Finished" Plan: Teams treat the rollout as done, making it socially awkward to revisit.
Strategies for Running the Alignment Code
1. Ask the Floor to Restate the Priority in Its Own Words
The size of the gap between a frontline team's answer and the actual slide is usually the fastest diagnostic available.
What to Listen For
- Substituted Priorities: A different initiative has quietly become "the" priority in practice.
- Missing Context: The team knows the what but not the why, which usually means the reasoning got lost somewhere in the chain.
- Resourcing Mismatches: The stated priority doesn't match where time and budget are actually going.
2. Build the Check Into a Recurring Cadence
A single re-alignment conversation closes the gap once. A short, repeated check — modeled on the same discipline behind Toyota Kata's coaching routine — keeps it from reopening.
3. Treat Drift as Normal, Not as a Failure
Constraints change; that's expected. The failure isn't drift itself — it's not having a mechanism built to catch it early.
Real-Life Case Studies
Case Study 1: Toyota's Continuous Re-Verification of Strategy
Toyota's Hoshin Kanri practice, as discussed in our piece on why it's a yes problem, isn't run as a once-a-year event — the catchball discipline is reinforced through ongoing daily management routines that continuously check whether floor-level activity still maps to the annual objectives.
Case Study 2: Danaher's Recurring Strategy Deployment Reviews
Danaher's operating system, discussed in more detail in our Hoshin Kanri article, is widely cited for pairing its initial strategy deployment with frequent, recurring review cadences — treating alignment as something actively maintained rather than a box checked once a year.
Key Takeaways
- Strategy as understood in the boardroom and strategy as understood on the floor are rarely identical, and that's not usually anyone's fault.
- A catchball process can close the gap for one planning cycle, but the gap reopens as constraints shift.
- Middle-management turnover and changing resources are the fastest ways the gap widens.
- Asking a frontline team to restate the priority in its own words is a fast, effective diagnostic.
- A recurring check, not a one-time rollout, is what keeps alignment durable.
FAQ Section
Q: Isn't this the same problem Hoshin Kanri already solves?
A: It's closely related. Hoshin Kanri's catchball process is one of the most effective
mechanisms for closing this exact gap — this piece is about naming the gap itself and why it
reopens even in organizations that have run catchball before.
Q: Why does the gap reopen even after a successful strategy rollout?
A: Because alignment is a state, not an event. The org chart, priorities, and constraints all
keep moving after the rollout, and without a recurring mechanism to re-check the floor against
the slide, the two quietly drift apart again.
Q: What's the smallest first step toward closing the gap?
A: Ask a frontline team to describe this quarter's top strategic priority in their own words.
The size of the gap between their answer and the actual slide is usually the fastest diagnostic
available.
Q: How often should this check happen?
A: Frequently enough that drift gets caught in weeks rather than discovered a year later in a
missed number — for most organizations, that means monthly at a minimum.
Conclusion
In conclusion, the gap between the slide and the floor isn't a one-time problem to solve — it's a permanent condition to manage. As Uma KA put it in The True North Compass, "the truth isn't in spreadsheets or reports. It's here, in the dust, in the sweat of these workers, in the small inefficiencies we overlook" — and that includes the small, ongoing drift between what's said in the boardroom and what's understood on the floor.
It's the same discipline behind our strategy deployment work. Reach out to find out how wide that gap is in your own organization right now.
