My recommendation: I deploy a multi-site growth strategy by clarifying the enterprise outcome, agreeing each plant’s and function’s contribution, and resolving resource conflicts before confirming commitments. Use two-way operating discussions to test feasibility, then check understanding through decisions, results, and barriers rather than attendance at a strategy presentation.
Having a strategy on paper is not enough. Your people need to know where they are going.
Without a clear, articulated strategy, decisions become harder. Teams pull in different directions. Leaders struggle to make critical choices on time. When conditions change, how do you adjust, meet your customers' needs, and keep people engaged if the organization does not understand the direction?
When I talk about communicating strategy, I mean more than announcing it. I want people to understand the outcome, see their contribution, and know what the plan means for a decision they need to make.
If you are a CEO or COO overseeing multiple plants, a new facility, or a companywide Lean deployment, an executive announcement is only the beginning. I want plant and functional leaders to explain what the growth plan means for their capacity, people, and current commitments. That is where a strategy becomes a workable operating plan.
What should executives clarify before cascading a growth strategy?
I want executives to explain the outcome, operating approach, priorities, and trade-offs before asking sites to translate the plan. A plant manager should be able to identify what changes because of the strategy. If the choices remain unclear, a larger presentation will not make the commitments workable.
- State the outcome you are trying to accomplish.
- Explain the approach and the priorities behind it.
- Name the trade-offs that should guide decisions.
A plan can contain a great deal of information and still leave the operating choices unclear. Ask what a manager should do differently because of the strategy. If you cannot give a useful answer, adding more slides will not solve the problem.
Separate the goal, strategy, objectives, and tactics. The outcome tells people where you intend to go. The approach explains how you intend to get there. The objectives and actions connect that direction to the work.
Give managers something they can explain accurately in their own words. They need to understand the choices, not just repeat the announcement.
How do you deploy a growth strategy across plants and functions?
I involve the leaders responsible for delivery in agreeing site contributions, dependencies, resources, and timing. A new plant launch, for example, may depend on engineering, suppliers, hiring, training, and production transfer. Discuss those conditions before confirming dates and assign responsibility for resolving cross-functional conflicts.
- Ask each function what it must contribute.
- Identify the dependencies between teams.
- Discuss resources and barriers before committing to actions.
I want the people responsible for delivery involved in translating the plan. They can identify a constraint, a missing capability, or a conflict that may not be visible in the leadership presentation.
Strategy deployment includes dialogue about the resources and time needed to achieve the targets. Use that exchange to test whether the plan is workable.
If one function's commitment creates a problem for another, resolve it. Otherwise, you can cascade conflicting instructions throughout the organization while believing you have created alignment.
For example, a new plant launch can depend on engineering changes, supplier readiness, hiring, training, and production transfer from another site. I would put those dependencies in the deployment conversation before leaders promise dates. Agree what each function must deliver, who resolves a conflict, and what operating evidence will trigger a change to the plan.
How do you know whether a strategy has reached daily operations?
I check how teams explain priorities and make current decisions. Can they connect an initiative to the objective, recognize a conflicting request, and identify who can resolve it? Review operating evidence and barriers through deployment reviews, then clarify the direction or revise commitments as conditions change.
- Ask teams to explain the priority without reading the plan.
- Review a recent decision and the reasoning behind it.
- Use what you learn to clarify the direction or change the plan.
Attendance at a meeting is not evidence that the strategy is understood. Look at the work. Can the team explain why an initiative matters? Can people recognize a request that conflicts with the priority? Do they know who can resolve that conflict?
Those questions give you something useful to act on. You may discover that a manager needs a clearer explanation. You may also discover that the plan contains an unresolved choice. Communication should help you find both.
When conditions change, explain what changed and what it means for current work. Keep the direction connected to operating evidence through your deployment reviews.
Your strategy has reached the organization when people can use it to make a clear decision about the work in front of them.
Frequently asked questions
Is sending the strategy document enough?
No. Explain the choices, discuss the contribution of each team, and check whether people can apply the direction to a real decision.
What feedback should managers bring to leadership?
Bring resource constraints, conflicting priorities, unclear measures, and operating evidence that challenges the plan. Those are issues leadership needs to resolve.
How do we cascade strategy without giving every plant the same action list?
I would align the enterprise outcome, measures, and major constraints first. Then have each plant propose its contribution and actions against its actual conditions. Review cross-site dependencies with functional leaders before confirming commitments, and bring operating feedback back to the executive team.
Sources
Make the growth plan executable across sites
If plants and functions are making conflicting commitments around expansion or growth, let’s connect the strategy to site-level contributions, resources, and deployment reviews.
Discuss multi-site strategy deployment