From Decision to Implementation: How a Strategy Rollout Is Really Received

The effort required to keep a rollout consistent is not an end in itself. The LSA Global study (410 companies, eight industries) shows that highly aligned companies grow 58 percent faster and are 72 percent more profitable, and that strategic clarity accounts for about 31 percent of the difference in performance. Alignment does not result from the strategic decision itself, but from the shared understanding that a rollout is intended to create. That is precisely why the visual as a common thread is more than just a communication tool. It is the instrument that sustains alignment over time. When, in the third month of the rollout, the fifth team is looking at the same big-picture view as the first team did in the first month, consistency emerges—and that consistency translates into measurable alignment. A rollout without this shared point of reference generates activity, but not clarity.

- Choose an image as a unifying theme. Select a single "big picture" that applies throughout the entire rollout. It serves as the anchor point to which every round and every location refers.

- Cascade, don't just distribute. Roll out the strategy step by step—but in a way that allows each level of leadership to explain the big picture on its own, rather than just passing it along. Those who have to explain it understand it better.

- Translate what it means for each person. At every level, the question must be answered: What does this strategy specifically mean for us, for this team, for this role? The shared vision remains the same; the interpretation is tailored to the local context.

- Create spaces for conversation. Plan formats in which people can ask questions and make sense of what they see. Understanding comes from dialogue, not from listening.

- Stay the course. Incorporate the vision into recurring formats over the course of several months—team meetings, reviews, progress updates. A rollout that ends after the kickoff event won’t take root.

The biggest mistake is treating the rollout as an event rather than a process. A big kickoff event, followed by a return to business as usual—that’s not how you embed a strategy. Embedding a strategy requires repetition over months, not a single powerful moment. A second mistake is giving each level the freedom to create its own materials. This may seem efficient, but it destroys consistency. If every department visualizes its own interpretation, you’ll end up with many strategies instead of one. The overall picture must remain the same across all levels; only the interpretation of what it specifically means is localized.

The third mistake is to omit the translation entirely. A concept that is merely presented but not broken down into the specific work of each department remains abstract. People won’t implement a strategy they can’t connect to their own daily lives. And finally, the mistake of failing to plan for opportunities for dialogue: A rollout that only sends messages and never listens won’t resonate with people.

A newly adopted strategy that is to be rolled out across the entire organization over the course of two or three quarters. A company with many locations, all of which need to share the same understanding. A realignment that is being communicated in cascading sessions from leadership down to the teams. Or an existing strategy program that, after its launch, risks fizzling out and needs a common thread to ensure it takes root.