My recommendation: I build strategic alignment by checking whether executive, plant, and functional leaders mean the same thing by goals, strategy, objectives, and tactics. Use one live growth or capacity decision to compare their interpretations. Agree on the outcome, measures, resource choices, and ownership before cascading commitments across sites.
I asked a room of leaders a question: can anyone explain the goal, the strategy, the objectives, and the tactics, and how we are measuring them?
The answers were all over the place.
I have seen this in two multibillion-dollar businesses. One made consumer packaged goods you would recognize in a grocery store. The other produced athletic wear around the world. They had plenty of terminology. They were adding Lean tools and methodologies. But nobody had clearly defined the terms they were using.
So the strategy introduced confusion, and people disengaged. Before adding another tool, make sure the team agrees on what the words mean. It sounds basic. In that room, it was the aha moment.
If you are leading companywide Lean deployment, a facility expansion, or a capacity ramp, those differences become operating decisions. Your COO, plant managers, finance leader, and continuous improvement team need to agree on the outcome before committing people, equipment, and improvement resources. I would test that agreement before rolling the plan out to every site.
How do you check whether plant and executive leaders are aligned?
I ask leaders to explain one current priority independently before showing them the approved wording. Compare the outcome they expect, the approach they intend, the measures they use, and the work they would prioritize. Differences expose operating choices that a shared presentation may conceal.
- Choose one current business priority.
- Ask leaders to explain the outcome, approach, measures, and actions.
- Compare the answers before debating the plan.
Do not begin by showing everyone the approved wording. Ask them to explain it independently. Otherwise, you may hear the same language without discovering whether people would make the same decision.
One leader may describe a desired result. Another may describe a project. A third may describe a departmental target. If all three call that the strategy, you have a difference to resolve before you can align execution.
The purpose is to uncover the operating consequences of the language. What will each person prioritize? Where will they put resources? What will they regard as success?
What is the difference between goals, strategy, objectives, and tactics?
I use a goal to describe the broad outcome, strategy to explain the approach and choices, objectives to specify measurable progress, and tactics to identify actions. Planning systems use different labels. Agree on working definitions that let leaders connect the enterprise direction to decisions and responsibilities.
- The goal describes the broad outcome.
- The strategy explains the approach and choices.
- Objectives make progress specific; tactics put the work into action.
Different planning systems use different labels. I am less concerned with winning an argument about terminology than with making sure the organization can use its chosen definitions consistently.
If your strategy is another aspiration, you still have not explained how you intend to reach the goal. If your objective is a list of activities, you may have assigned work without defining the result that work needs to produce.
Strategy deployment connects organizational activity to strategic objectives. Shared language helps people understand and discuss that connection across functions.
Suppose an expansion is on the agenda. One leader may mean more installed equipment, another more saleable throughput, and another a faster launch. I would ask them to identify the customer and capacity outcome, the evidence of progress, and the choices required. Those are different commitments until the leadership team connects them.
How do you test strategic alignment before a multi-site rollout?
I would test the agreed definitions against an initiative competing for resources now. Ask which objective it supports, which sites and functions must contribute, and what will wait if capacity is limited. Resolve conflicting answers before assigning more projects or deploying another methodology.
- Choose an initiative already competing for attention.
- Ask which objective it supports and why it deserves resources.
- Resolve conflicting answers before assigning more work.
This is where I would take the discussion next. A glossary can look complete while the actual priorities remain unclear. Apply the definitions to work the business is considering now.
If two initiatives depend on the same limited capacity, the leadership team must choose. If nobody can connect a project to an objective, clarify its purpose or reconsider its priority.
Keep the agreed definitions with the plan, and use them in your deployment reviews. They should help a new manager understand how decisions are made, not become another document that sits apart from the work.
Before you add another methodology, make certain your leaders can explain the same plan and act on the same priorities.
Frequently asked questions
Do we need one universally accepted set of definitions?
You need a set your organization understands and uses consistently. The practical test is whether people can connect an outcome to choices, measures, and actions.
How would you tell whether this is more than a vocabulary problem?
I would apply the terms to a live decision. Different answers about ownership, resources, or success show where the language is hiding a management problem.
Where should a multi-site leadership team begin?
I would choose one live growth or capacity decision and have executive, plant, finance, and improvement leaders explain it independently. Resolve differences in the outcome, measures, and resource commitments before cascading it to the sites.
Sources
Align leaders before the next deployment
If your executive team and sites interpret the growth plan differently, let’s clarify the outcomes and resource choices through a strategy deployment discussion.
Discuss leadership alignment and Hoshin planning