How to facilitate enterprise-wide strategic planning and translate strategy into business plans

TL;DR

If you are about to lead an enterprise-wide strategic planning process, the most important thing to get right before anything else begins is this: think carefully about who is usually on the team that determines the strategy, who actually needs to be on the team this time, and what information you want them to consider when formulating the strategy.

The composition of the room and the quality of the information in it will shape everything that follows. Get those two things right, and the rest of the process has a much better chance of producing strategy that holds together from the boardroom all the way to the frontline.

---

Enterprise-wide strategic planning is one of the most complex things a leadership team will do together. Not because strategy itself has to be complicated, but because the bigger the organisation, the more places there are for something to go wrong between the boardroom and the people who need to bring the strategy to life.

Understanding where and why enterprise strategy breaks down is the first step to doing it better.

Why enterprise strategy falls apart so often

When strategic planning spans multiple departments or business units, the process tends to unravel in a handful of predictable ways. Sometimes it is one of these in isolation. Often it is a combination.

Intent gets diluted as strategy trickles down into unit plans. Original meaning gets lost in translation. Business unit plans get rehashed from the previous year with little or no reference to changes in enterprise-wide strategy, whether due to lack of capability, lack of capacity, or something less charitable. The larger strategy gets misunderstood because it was not communicated effectively, or because it was not good strategy to begin with. And strategy gets treated as a to-do list rather than a big-picture guide for decision-making.

The most damaging of these, and the least visible, is the gap between intent and content.

The gap between intent and content

When a board sets enterprise strategy, the conversation in the room carries a great deal of intent. The reasoning, the trade-offs considered, the outcomes hoped for, the risks weighed. That intent is strong at board level because everyone involved was present for the full discussion.

What gets documented and distributed, however, is content. A summarised version of the board's thinking, packaged into a strategy document or presentation. And when that content is not packaged and communicated in a way that makes it crystal clear what each business unit's role in the strategy actually is, something important happens: business units align with the broad organisational goals because the content says the right things, but they do not fully grasp the intent behind them. The result is a diluted, generic version of the strategy appearing in unit-level plans, disconnected from the thinking that produced it.

This is not a failure of intelligence at unit level. It is a failure of communication at enterprise level and sometimes a sign that the strategy was built on shaky foundations.

Building the enterprise strategy on the right foundations

Most organisations use a recognised framework to analyse the business landscape: a SWOT analysis, PESTEL analysis, Porter's Five Forces, the VRIO Framework, or similar. These tools are useful. But they are only as good as the information fed into them.

Too often, that information is filtered through management reports. This is a problem. Management reports are frequently shaped, consciously or not, to secure bonuses or protect positions rather than to give oversight a genuinely accurate picture of what is happening in the business. Relying on them as the primary source of insight means strategy gets built on a curated version of reality.

A more reliable source of input

The people working on the frontlines of the business every day see the obvious challenges and frequently have practical solutions. They do not charge a consulting fee for that perspective. Some will argue that including frontline input in strategy development is too operational. That argument confuses the source of information with the level at which decisions are made. Gathering insight broadly is not the same as letting everyone set the strategy.

In practice, this does not have to be complicated. Sending a short anonymous survey to everyone in the business, or across relevant business units, can surface insight that management reports never would. The questions do not need to be sophisticated. Simple prompts tend to produce the most honest answers. Questions like:

• If you were CEO or manager for a day, what would you change?

• If you were a customer, what would you change?

• What did you like most when you first joined the company?

• What do you like most about the company now?

The anonymity matters. People answer differently when they know their name is not attached to the response.

Once the responses are in, AI tools can process and group them according to the topics and sections the strategy developers will be working through. What used to take weeks of analysis can now be done quickly, and the output gives strategy developers a far more honest picture of the business than a stack of management reports ever could.

The harder part is not the process. It is being willing to ask the right questions and then consider the answers with a genuinely open mind.

How to structure a process that actually works

A well-facilitated enterprise-wide strategic planning process has three distinct phases for business unit leaders: before, during, and after.

Before strategy is set, business unit leaders should be asked to provide input and relevant information that will inform the enterprise strategy. The emphasis here is on helpful, not protective. Information shared at this stage should serve the organisation, not the unit's internal interests.

During the strategy-setting phase itself, active participation from business unit managers is generally not advisable. Strategy is a governance-level activity. A manager's role is to think and operate at a more technical and operational level, and pulling them into the strategy-setting conversation tends to push the discussion in the wrong direction.

After strategy is set, the dedicated session described above is not optional. It is the moment where intent either gets transferred or gets lost. How well that session is designed and facilitated will determine how well the strategy survives its journey from the boardroom into the business.

The most effective way to transfer intent, not just content, is through a dedicated face-to-face session with those who will be developing business unit plans. In person or online, but never replaced by an email with an attachment.

The session should not be a presentation of the strategy slide deck. It should be an explanation of how the strategy was formulated: what was considered, what was debated, what was set aside and why. The goal is for every person in the room to understand the purpose behind each part of the strategy, not just what it says.

That requires ample time for clarifying questions. It also requires experienced facilitation. Questions from business unit leaders at this stage are not always framed as requests for clarity. Some will be framed as challenges. Some will be thinly veiled attempts to reshape the strategy in favour of a particular unit. A skilled facilitator will set up and manage the session in a way that makes the purpose clear from the outset: this is not a consultation or an exploratory discussion. The strategy has been set. The session exists to ensure everyone understands it well enough to build on it effectively.

Translating enterprise strategy into business unit plans

The translation from enterprise strategy to business unit plan is where intent either survives or disappears entirely.

It starts during the enterprise-wide phase, not after it. The right question to ask at enterprise level is: which departments will be impacted by or have an impact on this strategy, and how? Answering that question thoroughly creates a logical framework that each business unit can tie into with clarity and ease. It also allows for proactive allocation of responsibility and resources, which prevents the very common situation where multiple units are duplicating effort and expense in one area while other areas are being neglected entirely.

The enterprise strategy itself needs to strike a careful balance. It must be high-level enough not to dictate operations, but specific enough that it is not fuzzy, unfocused, or dressed in jargon. It should make it straightforward for business unit leaders to see exactly where their unit is expected to contribute, where it is not, and what resources they have to work with. It should inspire the unit's best efforts without overwhelming it with ambition. And it should leave room for innovation while providing clear guardrails that keep the unit's output pointed in the right direction.

The business unit plan, in turn, should not try to replicate or reinterpret the enterprise strategy. It should reference how it connects with other units, be clear on how its output aligns with the enterprise strategy, and be specific about how it will measure and report on progress in ways that are tied to the enterprise strategy rather than just to conventional reporting frameworks.