Every strategy survives the boardroom. Very few survive the trip from the boardroom to the break room.
Somewhere between the strategic plan and the daily task list, something gets lost — not because anyone is incompetent, and not because the strategy was wrong. It gets lost because organizations spend enormous effort crafting strategy and almost none translating it, and the translation layer they're relying on by default is a group of people who were never actually equipped for the job: middle managers.
The Telephone Game, Institutionalized
Every organization has an informal version of the childhood telephone game running at all times. Executive leadership defines a strategic priority, communicates it clearly in an all-hands meeting or a cascaded memo, and assumes the message will travel intact down through the organization. It rarely does — not because people are careless, but because "communicating strategy" and "translating strategy into daily decisions" are two entirely different skills, and organizations only ever train and support the first one.
Middle managers are the ones actually doing the second job, mostly without a name for it, without formal support for it, and without anyone above them checking whether it's actually happening. They're the ones fielding the question "so what does this actually mean for what I do on Tuesday?" — a question the strategy deck never answers, because it wasn't built to.
When that translation fails, it doesn't fail loudly. Nobody announces "we've lost alignment." It fails quietly, team by team, in a hundred small decisions that drift slightly off from what leadership intended — decisions that all felt reasonable to the people making them, because nobody gave them a clear enough translation to know they'd drifted.
Why This Layer Gets Ignored
Most organizational health measurement skips straight past middle management. Employee engagement surveys measure the frontline. Executive alignment gets assessed in board sessions and leadership offsites. The layer in between — the one actually responsible for turning strategic language into operational reality — rarely gets asked a direct question about how confident they actually are in their own understanding.
That's a significant blind spot, because middle managers have a kind of visibility nobody else in the organization has. They see the gap between what leadership intended and what teams are actually doing, in real time, every day. They know which strategic priorities make sense on paper and fall apart against real operational constraints. They know which trade-offs their teams are quietly making between what's urgent and what's supposedly strategic. And in most organizations, nobody is systematically asking them what they know.
What the Data Actually Shows When You Ask
When middle managers are surveyed directly and specifically — not about engagement in general, but about their own confidence in their team's strategic understanding — the results are usually more sobering than leadership expects.
A useful benchmark: confidence below 70% among middle managers is a meaningful red flag, regardless of how aligned senior leadership believes the organization to be. Below that threshold, the translation layer isn't functioning reliably, and strategic intent is arriving at the frontline in a degraded, inconsistent form — different on different teams, filtered through each manager's own best guess at what leadership actually meant.
Three questions, asked directly, tend to surface the real picture fast:
How confident are you that your team understands the company's strategy? This alone often produces a wider range of answers than leadership expects — confidence varies enormously by function, by manager, and by how much direct translation support that manager has received.
What barriers prevent your team from executing strategically? The answers here are rarely about willingness. They're almost always structural: competing priorities with no clear resolution, insufficient resources to actually act on the priority, or strategic guidance that was communicated but never made operationally concrete.
What trade-offs are you making between strategic priorities and operational demands? This question, more than any other, reveals where the real gap sits — because it forces managers to describe the choices they're actually making, not the choices the strategy assumes they're making.
Patterns across these answers are diagnostic. If competing priorities and unclear guidance show up repeatedly across different managers and different functions, that's not a series of individual management shortcomings — that's a translation mechanism that was never built.
What Organizations Get Wrong When They Try to Fix It
The default response to a strategy that isn't landing is to communicate it again — another all-hands meeting, another memo, more repetition of the same language that didn't translate the first time. That rarely works, because the problem was never repetition. It was translation.
Fixing this requires building the translation layer deliberately instead of assuming it happens automatically. That means function-specific guides that describe what a strategic priority concretely means for Sales versus Operations versus Finance, not just for the company in the abstract. It means equipping managers with actual decision frameworks — practical tools for resolving the trade-offs their teams are already quietly making, rather than leaving them to improvise. And it means treating middle management confidence as a metric worth tracking on its own, on a regular cadence, rather than an assumption baked silently into every other engagement number.
The Real Cost of Leaving This Unmeasured
Organizations that never measure this gap don't experience it as a single failure. They experience it as a slow accumulation of underperforming initiatives, each one individually explainable — "that team was slower to adopt," "that function had unusual headwinds," "that manager was newer to the role" — none of which, examined together, ever gets identified as the same root cause repeating itself.
The cost is real and it's cumulative, even though it never appears as its own line item on a financial statement. It shows up instead as strategic initiatives that technically launched everywhere but only fully executed in the functions where a manager happened to translate the strategy well on their own instinct — which means the organization's actual execution quality is being determined by individual managerial talent, not by design.
That's not a sustainable way to run a strategy. It's also, fortunately, a fixable one — but only once it's actually measured instead of assumed.
Leadership Bottlenecks and Workforce-Strategy Disconnection are two of the five risks we walk through in our Hidden Workforce Risk working session, if you want a structured way to see where your own organization stands.
