The first time, it surprised me. The second time, I thought maybe it was industry-specific. By the sixth, it started to look like gravity. Somewhere between 50 and 70 percent of the plan, a digital transformation starts to lose mass — whether it's a small company or a larger organization. Meetings happen less often. Initiatives stay open. The best people are busy with something else. Six months later, leadership is asking how a €400,000 investment ended without a clear outcome.
This isn't a piece about how to write a better plan. I'll assume the plan is good — it often is. This is a piece about what happens in that critical 60%, and why it happens so consistently, regardless of industry, team size, or the quality of the consultants who wrote the strategy.
Pattern one · One team writes the strategy, another delivers it
The classic setup. An external consultant runs the diagnostic, holds three workshops with leadership, and delivers a 60-page plan. The plan is good. A week later it moves off leadership's desk to an internal "head of transformation" — usually an existing person who's had this added to their job description. The consultant disappears. The head of transformation starts running their regular job in parallel with six more delivery work packages.
Six weeks later, the first package is late. Leadership asks why. The head of transformation explains — truthfully — that they didn't have the capacity. The second package is less late, but late. The third is "90% done." The fourth never started. Somewhere in this sequence, the quarterly rhythm is lost, and with it any clear definition of what "done" means.
The fix isn't complicated: the same team owns strategy and delivery. Not because internal people aren't capable — but because internal people already have a job. Strategy on paper is written faster than it's delivered. Delivery needs hands that are free.
Pattern two · What gets measured isn't what matters
The second pattern arrives more quietly. The strategy defines metrics — often 12, sometimes 18. A dashboard gets built, data flows into it weekly. Everything looks fine.
But five of those twelve metrics are activities, not outcomes. "Number of workshops held." "Number of employees trained." "Percentage of sprints completed." These are numbers that go up even when nothing changes. Six months in, the dashboard shows tidy progress, while the business numbers — revenue per client, delivery time, margin — hold flat or fall.
At that point, leadership is in an uncomfortable spot: the plan deserves trust, because a capable team wrote it. But the numbers that matter aren't moving. The most common reaction — paradoxically — is to add more initiatives.
Pattern three · Initiative on top of initiative
Trying to accelerate, leadership adds new projects to an already overloaded plan. The logic is understandable: some of the twelve things didn't work, but a few worked well enough that we want more. Let's start three new initiatives.
The consequence: people already running six packages now run nine. Quality drops. There are too many demos, retrospectives get skipped. Six weeks later, the number of open initiatives is larger than the number that will finish by year-end. The head of transformation no longer knows what's a priority, because everything is.
The fix is an unpopular word: cut. The biggest intervention we make mid-project isn't adding, it's subtracting. Twelve initiatives → seven. Seven → four. Four get delivered seriously. Eight go back to the backlog for next quarter.
What to do differently
1. Define "done" before you start
In the strategy document, every initiative needs a written definition of done: what must be true, by when, and who can confirm it. If you can't write that sentence in 20 minutes, you probably don't understand the initiative well enough to start it.
2. Separate activity from outcome
On the dashboard, two columns. Left: activities (effort, number of demos, number of trainings). Right: outcomes (revenue per client, delivery time, margin). The left column is for you — to know whether you've been working. The right column is for leadership — to know whether it's working.
3. A quarterly reset, not a monthly status
Monthly status meetings become ceremony. A quarterly reset is a different format — leadership and the delivery team sit down, two hours, one decision: what we keep, what we buy, what we add. The worst possible decision is "we continue everything." The third worst is "we add three more."
4. Run the plan from the calendar, not the document
A plan that isn't in someone's calendar — with real dates, real people, real results — isn't a plan. The document is a reference. The calendar is the working tool. The two are often confused.
In closing — on the silence in week 22
The most dangerous moment in a digital transformation isn't a crisis. Crises get solved because they're visible. The most dangerous moment is week 22 — when the kick-off energy is gone, when the strategy has become "a document," when leadership stops asking about the project because it's awkward to ask.
Ask. Out loud. In front of everyone in the room. Ask what isn't done, why, and what we should stop doing so the things that matter can move. That's the conversation we get called in for — and the conversation that usually separates a digital transformation that stalls from one that finishes.