There is a familiar pattern in digital transformation. The strategy is developed with care. Leadership endorses it. There is a launch, perhaps a presentation to staff, some genuine enthusiasm.
Then, slowly, very little happens. A year later the document is still accurate, still sensible and still mostly unimplemented.
It is tempting to blame the strategy. Usually that is the wrong diagnosis. The strategy was fine. What was missing was everything needed to turn it into changed work.
Approval is not the finish line
A strategy approval feels like an ending. A lot of effort went into it, and getting sign-off is an achievement. But for the people expected to deliver it, approval is only the beginning, and it often arrives with no extra time, budget or clarity about what to do first.
Transformation stalls in the space between what the strategy says and what anyone does on Monday morning. In my experience, that gap opens up for a small number of predictable reasons.
Five reasons it stalls
1. The strategy describes intentions, not actions
Many strategies are written at the level of direction: "become a data-informed organisation", "modernise our systems", "use AI responsibly". These are useful statements of intent. They are not things anyone can start doing.
Without a translation into specific initiatives, each with an owner and a first step, people agree with the strategy and carry on as before.
2. Everything is a priority
A strategy that lists twelve initiatives of equal importance has not prioritised anything. When everything matters, people default to whatever is most urgent in their own area, and the strategy loses to the daily workload every time.
Real prioritisation means deciding what comes first, what waits and what is not happening at all. That last category is the hardest to write down and the most useful.
3. Nobody owns the change
Strategies are often owned by the leadership team collectively, which in practice can mean nobody owns them. Individual initiatives get assigned to managers who already have full-time jobs and no authority over the other teams they depend on.
Change needs someone with the time, mandate and accountability to keep it moving, and a leadership team that follows up.
4. The operating model hasn't changed
A strategy might call for more collaboration across teams, faster decisions or better use of data. But if the structures, meetings, approvals and systems that shape daily work stay exactly the same, behaviour will too.
People don't resist change because they disagree with it. Often they are simply working inside a system that still rewards the old way.
5. Implementation is treated as a project, not an adoption
When initiatives do get delivered, they are often treated as finished at go-live. The new system is switched on, training happens once and the project team moves on.
But delivery is not adoption. Unless people actually change how they work, the old habits and workarounds come back within months.
What keeps transformation moving
None of these problems needs a new strategy. They need a different kind of attention after the strategy is approved.
- Translate before you celebrate. Before launch, turn each strategic goal into a small number of concrete initiatives. For each one: an owner, a first step, a decision point and a way to tell whether it is working.
- Sequence ruthlessly. Choose the few initiatives that make others possible, and start there. Be explicit about what is paused. Publish the sequence so people stop guessing.
- Give ownership real weight. Assign each initiative to someone with the time and authority to deliver it. Protect that time. Ask about progress regularly, and treat slippage as a signal to remove obstacles, not to assign blame.
- Change the system around the work. Look at the meetings, approvals, reports and tools that shape daily behaviour. If they still reflect the old way of working, change them. This is often where the biggest gains are.
- Plan for adoption, not delivery. Treat go-live as the midpoint. Budget time for support, reinforcement and adjustment. Watch whether people are using the new approach, and fix what makes it harder than the old one.
A simple check
If you have an approved strategy and are not sure whether it is moving, ask three questions.
Can each person responsible for an initiative tell you what they are doing this month to advance it? Can your leadership team name what has been deliberately stopped or delayed? Has anything about how people work day to day actually changed?
If the answers are unclear, the strategy is probably not the problem. The work of turning it into change has not started yet. That work is less visible than writing the strategy, and it matters far more.