Strategy Implementation That Actually Sticks
The kickoff went well, the way these things usually do. There was a new strategy on the screen and a leadership team that had clearly done the work. When someone put up a slide reading “Day One,” everyone nodded in all the right places. Three months later I asked how it was going, and the most honest answer in the room was that everyone had gone back to doing their jobs the way they always had.
That is the part nobody warns you about. The hard problem in strategy implementation is not the launch. It is everything after it, once the energy of the kickoff fades and the old way of working starts pulling people back to where they were.
Most implementation fails for a reason that sounds almost too simple: We treat it as an event. A plan gets announced, a deadline gets set, and we assume the announcing is the doing. It almost never is.
What execution actually breaks on
Donald Sull and his colleagues studied this across more than 250 companies for Harvard Business Review, and a few of their findings quietly dismantle how most of us run implementation. One is that communicating a strategy is not the same as people understanding it. In their research, only half of middle managers could name even one of their company’s top five priorities. These were not disengaged people, they had sat through the same presentations as everyone else. The message simply had not survived the trip from the slide to the work.
Another finding cuts against our instincts. We tend to think good execution means everyone aligned vertically, marching in the same direction from the top down. The breakdown Sull found was horizontal. People could not rely on the commitments of colleagues in other departments. Implementation did not stall because the hierarchy was confused, it stalled in the handoffs between teams, where nobody quite owned the seam.
And the one leaders find hardest to accept: implementation is not about sticking rigidly to the plan. The plan is a starting position. Conditions move, and the teams that actually deliver adjust as they go rather than defending a document that reality has already outpaced.
The reason new behaviours slide backward
Here is where I lean on something from a different field. For decades, researchers have asked why training so rarely changes what people do once they are back at their desks. The recurring answer is not about the quality of the training. It is about the environment people return to. Whether a new behaviour survives depends on whether a manager reinforces it and whether anyone actually notices when it happens or does not.
Strategy implementation works exactly the same way. You can run a flawless kickoff and still watch the new behaviours dissolve, because the environment around your people is still rewarding the old ones. If the metrics and the manager conversations all still point at the previous way of working, that is the way of working you will get.
Make it a system, not a season
So the work of implementation is mostly the work of building an environment that keeps the new behaviour alive until it stops feeling new. In practice that means a regular cadence where progress gets reviewed and not just reported. It also means putting a name on each seam between teams, because a handoff that belongs to everyone belongs to no one. The last piece is feedback fast enough that people can correct course in weeks, rather than discovering at the annual review that nothing moved.
None of that is dramatic. It is the difference between a strategy that runs and one that is technically live and quietly inert.
The real test
I have come to think the honest measure of implementation is not whether the launch went well. Launches almost always go well. The measure is what is still happening ninety days later, once no one is watching the new initiative as closely. If the behaviour is still there, you built a system. If it faded, you held an event.
This is the same gap I wrote about in why strategic plans fail, the distance between a good plan and changed behaviour. Implementation is simply where you either close that distance or you do not.
And the part that decides it earlier than most leaders expect is whether people actually own the change or are merely complying with it, which is its own piece: how to get real buy-in for change. If you have a strategy that launched well and then went quiet, that is the gap my services are built to close.
So before the next big kickoff, it is worth asking what your environment is currently rewarding. Because that, far more than the plan, is what your people will keep doing once the room empties out.