A VP at a mid-size technology company described a conversation she had with one of her directors three months after a company-wide strategy presentation. She asked him, casually, what he understood the company's top priority to be for the year. His answer was precise and confident — and accurate to about six months prior. He was working from the previous version of the strategy, one that had been quietly superseded after a board conversation that never made it below the C-suite in any usable form. He hadn't missed a meeting. He had taken notes. He just hadn't received an update that made the change legible at his level, because nobody had thought to build that translation.

The failure in this story is not one of attention or intent. It is structural. The strategy had been communicated. Nobody had checked whether it had been understood.

The Number That Should Concern Every Senior Leader

Recent data from the LHH 2026 C-Suite Research quantifies this failure at scale. Only 54% of C-suite executives report confidence that leaders two levels below them can accurately explain the company's top strategic priorities. Separate research puts the employee-wide figure at 95% — 95% of employees across industries cannot explain their organization's strategy at all.

The instinct, when confronted with numbers like these, is to prescribe more communication. More all-hands. Cleaner slide decks. A shorter memo. The instinct is understandable and almost always wrong, because the problem is not volume. Most organizations with this gap have already saturated their leadership teams with communication events. The issue is that communication and comprehension are being treated as the same thing, when they are two entirely separate events with no guaranteed connection between them.

Why Strategy Stops Traveling

A C-suite articulates strategy in the language that makes sense at that level: market position, portfolio choices, financial targets, competitive moats. These abstractions are meaningful to the people who hold them. They are almost never the right unit of meaning for a director making a resource allocation call on a Thursday afternoon, or a VP deciding which of three competing initiatives to prioritize for the quarter.

To act on a strategy, someone two levels below the C-suite needs to be able to translate it — to understand what the strategy implies for their specific decisions, trade-offs, and priorities. That translation does not happen automatically. In most organizations, nobody builds it. Leaders two levels down are left to infer, and their inferences carry the compounding error of every assumption they have to make along the way.

What makes this particularly difficult to catch is the silence that surrounds it. Signaling that you do not understand the strategy reads, in most organizational cultures, as signaling that you do not belong at the level you are at. So nobody says anything. Status updates get filtered through the same layer that failed to understand the strategy in the first place. The C-suite receives confirmation that things are on track, because it has no mechanism to receive anything else.

Executives measure what is measurable: decks sent, meetings attended, surveys completed. They rarely measure whether anyone could have explained the strategy to a peer the next morning in a way the C-suite would have recognized.

A Design Problem, Not a People Problem

The directors and VPs operating in this situation are not careless. They are operating inside a system that has no feedback mechanism — a system where the assumption of comprehension substitutes for the verification of it, and where the cost of confusion accumulates quietly before anyone with the authority to fix it can see it.

The fix is not a better slide deck or an additional all-hands. It is treating comprehension as a distinct deliverable from communication, with its own verification step. That means building in deliberate mechanisms at each level where strategy needs to travel: asking whether leaders can articulate priorities in their own words, whether those articulations would be recognizable to the people who set the strategy, and whether the gaps between them are being actively closed rather than assumed away.

In operational environments where the cost of confusion is immediate and visible, mission understanding is verified before the operation begins — not because the briefer doubts the audience's intelligence, but because the environment does not tolerate the assumption that understanding followed from communication. Corporate organizations have longer feedback cycles. The cost of misalignment accumulates slowly enough that nobody sounds the alarm until the organization has spent months executing against the wrong map.

The question is not whether your strategy has been communicated. Most have. The question is whether anyone two levels down could explain it tomorrow morning in a way you would recognize as the actual strategy — and whether your organization has any mechanism for finding out the answer.

What does your organization actually check to know the strategy has been understood, not just received?