The strategy was fine. The rollout wasn't.

I have sat on boards with twenty-three competing partners around one table, and I have taught project management to a decade of students who wanted a Gantt chart to solve a people problem. The lesson is the same in both rooms: strategies don't fail on the page. They fail somewhere between the approval and the third month.

The pattern is familiar. A leadership team spends two quarters and a consultant's budget arriving at a genuinely good plan. It gets approved. It gets announced. And then it meets the forty people who will have to do their jobs differently, most of whom heard about it for the first time in the announcement.

Announcements are not adoption

A launch communicates that a decision has been made. It does nothing about capability, incentive or fear — the three things that actually determine whether someone changes how they work on a Tuesday.

If the new plan asks a team to drop something they have been rewarded for doing well, and nobody changes what gets rewarded, the plan loses. Not because anyone sabotaged it. Because people are rational.

Build the rollout into the strategy

The organisations that get this right treat implementation as part of the design, not a phase after it:

• Name who has to do something differently, by role, before signing off.
• Say what stops. A strategy that only adds is a wish list.
• Give the middle a script. Directors and managers carry the change; if they can't explain it in their own words, it doesn't exist.
• Measure adoption, not activity. Slides delivered is not the same as behaviour changed.

Change management isn't the soft side of strategy. It's the part where the strategy either becomes real or quietly doesn't.