Most companies communicate strategy the way they communicate weather: they announce it. The CEO writes a strategy memo. The leadership team presents at an all-hands. The strategy exists now. The employees have been informed.
Being informed is not the same as being able to act on something. And strategy — real strategy, the kind that should change how hundreds of people allocate their time and attention — is only valuable if it can be operationalized. That requires a completely different approach to communication.
The context gap
The most common failure in strategy communication is what the Airbnb and Eventbrite planning research calls "no context" — leadership skips directly to telling teams what to do without sharing the reasoning behind it. They produce a strategy doc and assume the context is sufficient. It isn't.
The research from FirstRound's review of the Airbnb/Eventbrite planning process is direct: "The more the Teams understand the intangibles, e.g. the 'why' behind the vision and strategy, the more likely they are to deliver great results that fall in line with the expectations of Leadership." Without the why, teams develop their own why — and those why don't converge.
What useful strategy communication looks like
Poppulo's research on strategy communication identifies the key principle: employees need to understand how the strategy connects to their specific context. The same strategy means different things to an account executive in Toronto, an engineer on the infrastructure team, and a customer success manager in Dublin. Strategy communication that ignores this produces exactly the response most companies get: nodding in the room, confusion outside it.
The components that actually work:
A limited set of strategic pillars. The five essentials from the Airbnb/Eventbrite research: Mission, Vision, Goal, Strategy, and three to five key bets. Not a ten-page strategy doc that nobody will read — a small number of focused commitments that can be remembered and applied.
The reasoning, not just the conclusion. Leadership's job in communicating strategy is to share what they know, what they're unsure about, and what assumptions they're making. "We think this market is moving toward X because of A, B, and C" gives a team enough to make good calls when the strategy document doesn't cover a specific situation.
Reinforcement across channels, not a single announcement. The Poppulo research is clear: "Leaders need to role model it, repeat it, and refer to it often." Strategy communication is not an event — it's a practice. It needs to appear in team meetings, in manager briefings, in the way priorities are discussed, in how decisions are made.
Manager capability. The most underrated component: empowering managers to translate strategy into team-specific implications. Poppulo recommends "discussion guides" that help managers have strategy conversations with their teams — not to broadcast the strategy downward, but to work through what it means for each team's specific situation. This is where strategy becomes operational.
The failure mode to avoid
The strategy document that lives in a shared drive and gets referenced once a quarter is not a strategy communication. It's a compliance artifact. Real strategy communication happens continuously, in how leaders make decisions, how they allocate time in meetings, and how they respond to questions from teams. The document is the start, not the end.
