Strategy communication, in the operating sense, is everything an organization does to make its strategy known, understood, and usable by the people executing it. Not the launch event. Not the deck. The full system: the artifact that states the strategy, the occasions where people re-encounter it, and the connections that let someone see how their own work relates to it.
Defined that way, the standard playbook is revealed as one-third of a system, and the third that matters least.
The launch playbook, and what it actually produces
The standard sequence is familiar: leadership finishes the strategy, communications turns it into a deck and a narrative, the all-hands launches it, posters and wallpapers follow, maybe a video. Executed well, this produces recall. People can repeat the pillars for a few weeks. Executed brilliantly, it produces enthusiasm too.
What it does not produce is alignment, and the research on this is brutal. In the largest study of its kind, published in Harvard Business Review, Sull, Homkes and Sull found that only 55% of middle managers could name even one of their company's top five priorities. These were not companies that skipped the launch. The strategy was written, presented, and distributed. It just did not survive contact with the following months, because a message encountered once decays, and nothing in the launch playbook re-encounters it.
The deeper problem: recall was the wrong measure all along. A manager who can recite the strategy but cannot say what it changes about their team's next quarter is aligned in trivia only. We covered the mechanism in the all-hands is not alignment: a broadcast can synchronize understanding for a moment, but it has no way to notice when understanding and work drift apart again.
The artifact: strategy on a page
Communication starts with something communicable. A forty-slide strategy cannot be re-encountered weekly; a page can. The strategy-on-a-page format compresses the whole thing into what fits in working memory: the ambition, the few explicit choices about how to win, this year's priorities, the measures that define success, and, hardest and most valuable, the not-doing list.
The compression is not a summary exercise. It is a forcing function. Choices that survive compression to a page were real choices; the ones that evaporate were hedges. Our strategy on a page template has the structure as a free download, and it earns its keep even for teams that never share it beyond the leadership room, though sharing it is rather the point. A strategy nobody can recite was never really communicated, however thorough the launch.
Cadence beats campaign
The message that survives is the one that gets re-encountered on a rhythm, in context, attached to decisions. That means the operating cadence is the real communication channel. When the weekly team review opens against the same priorities the strategy named, when the monthly review scores the same measures the page defined, when a project proposal has to say which priority it serves, the strategy is being communicated dozens of times a quarter, by the structure of work itself rather than by the communications team.
This inverts where the effort goes. The launch is a day; the cadence is the year. An internal communication strategy that spends 90% of its budget on the launch and nothing on how reviews, planning, and prioritization reference the strategy has optimized the day and abandoned the year.
The part communication cannot do alone
There is a ceiling on what even well-cadenced messaging achieves, and it is worth being honest about it. Telling people the strategy, however often, leaves each person to work out privately whether their actual work serves it. Most cannot, not from any failure of intelligence, but because the connection genuinely is not visible anywhere: the strategy lives in a document, their work lives in a task tool, and nothing joins them.
So the strongest form of strategy communication is structural: a strategy people can see beats a strategy people are told. When the goals, the measures, and the work connected to them are visible in one place, every person can trace their own tasks upward to the priority they serve, and communication stops being a broadcast problem at all. The question "did the message land" gets replaced by an observable one: "is the work following the strategy", which is a thing you can check rather than survey. Making strategy visible beyond leadership is the single highest-return move in this whole area, and it is a systems decision, not a messaging one. That visible connection between strategy and daily work is exactly what Vindaris exists to maintain.
A strategy communication plan that works
The checklist, in the order that matters:
- Compress to a page. Ambition, choices, priorities, measures, not-doing. If it does not fit, the strategy is not finished.
- Launch it once, well. The all-hands still matters: it marks the moment and carries the reasoning. Spend the Q&A on trade-offs, because the not-doing list is where belief is won.
- Wire it into the cadence. Weekly and monthly reviews open against the page's priorities and measures. This is the channel; treat it as one.
- Make the connection visible. Every goal and project should name the priority it serves, somewhere everyone can see, so alignment is checkable rather than assumed.
- Instrument the drift. Watch for the teams whose work has quietly stopped referencing any priority. That signal, not a pulse-survey recall score, tells you where communication actually failed.
- Re-communicate on change, immediately. When a priority is dropped mid-year, the teams still executing against it need to hear it the week it happens. The silent deprioritization is the most expensive communication failure there is.