Most strategy documents survive the meeting where they are approved and start losing shape the moment they reach middle management. Not because the strategy was wrong, and not because managers did not understand it, but because nobody translated it into what actually changes on a Tuesday morning.
A strategy that says "become more customer-centric" or "build supply chain resilience" is a direction, not an instruction. Middle managers are left to interpret it themselves, and interpretations drift: one team reads it as a cost exercise, another as a hiring freeze, a third quietly continues doing what it already did and calls it alignment.
The fix is not more communication of the strategy itself; it is translation work at each layer. What does this direction mean for how this team prioritises its next quarter? What decision would look different next week if this strategy is real? If a manager cannot answer that for their own team, the strategy has not actually landed yet, regardless of how well the town hall went.
Execution drift is also a trust signal worth watching. When teams quietly revert to old patterns a few months after a change announcement, it is rarely defiance. It is usually because the new direction was never translated into something concrete enough to replace the old habit.
Closing strategy-to-execution gaps is slower and less glamorous than writing the strategy itself, but it is where most of the value is actually won or lost.