The strategy reached the manager. It never reached the team.
A strategy can sound clear in the leadership meeting and mean very little in daily work.
The manager can repeat the strategic priorities. The team cannot explain what they change about the work. Leadership hears that the strategy has been communicated. Employees hear another request to connect their tasks to a direction that still feels remote.
A second presentation may help. First find out what the leaders actually agreed to.
Leaders can agree without meaning the same thing.
In the 2026 Harvard Business Review article The False Alignment Trap, Julia Dhar, Kristy Ellmer and Philip Jameson describe a common problem. Executives say they agree on a transformation, but they hold different views about why the organization is changing, what will change, and how it will happen.
In one exercise described in the article, most members of an executive team initially reported clarity about the future organization. When asked to write down the specific differences they expected, their answers diverged. If each leader had carried that private interpretation into their function, the organization would have moved in several directions while continuing to call the effort aligned.
This matters to the manager receiving the strategy. The message may not have become less clear on its way down. It may have been unclear from the start.
The manager may have received only the words.
A direction such as improving service still leaves choices about staffing, turnaround times, exceptions and cost. If leaders have not worked through those choices, the manager has a slogan to pass on and little else.
Donald Sull, Charles Sull and James Yoder reported in a 2018 MIT Sloan Management Review study that only 28% of the executives and middle managers responsible for execution could list three of their organization’s strategic priorities. Knowing the words is only the first hurdle. People must also know how those priorities change a real decision.
There is another possibility. The manager understands the direction but struggles to translate it into the choices a line or field employee makes. The connection between a company priority and Tuesday morning’s work is rarely obvious. People know what is due on Friday. They do not know which work to protect when two deadlines collide.
That gap affects more than execution. It shapes the employee experience. People asked to follow procedures without understanding the purpose have less room to improve the work or use judgment when conditions change. Employees serve customers directly or run the processes that do. What they experience will eventually reach the customer.
Test the strategy against a choice.
A familiar explanation is useful only if it helps someone make a decision. Test it against a real trade-off the team must make.
Compare three versions of the strategy.
Ask two senior leaders and one manager the same three questions separately. What is the organization changing? What is it keeping? Which trade-off does the strategy settle? Use a recent decision from the work, not an abstract question.
Then ask several team members what they would do when the same trade-off reaches them. Compare the answers. Write down the missing choice or disagreement before creating another presentation or message.
Check the next trade-off.
Ask the person responsible to make the explanation concrete. Name the work to prioritize, the work that can wait and the measure that matters. Return to a real decision later and see whether the team used that direction.
The strategy has reached the team when people can choose between competing priorities, explain why a procedure changed, improve the work, and know when to escalate. It has gone further when people know which decisions they can make without waiting for permission.
That requires managers to translate the strategy. It also requires senior leaders to give them choices specific enough to translate.