Why most digital transformations fail at the third quarter

Digital transformation programmes tend to come apart at a predictable point, and it is later than most people expect. The first three months run on kickoff energy, when the steering committee leans forward and nobody has yet produced an outcome anyone can argue about. The second quarter still has novelty working for it. It is somewhere between week twenty-four and week thirty-six that things go wrong, once the novelty has gone, operational reality has reasserted itself, and the programme has become one more thing competing with everyone’s actual job for attention.

The symptoms are consistent enough to use as a checklist. Steering committee attendance drops: the CEO sends a deputy, the CFO sends a delegate, and the deputies send minutes, so a forum that was making decisions becomes a forum reporting on decisions made elsewhere. The initiative acquires scare quotes, and people in operations start calling it their project rather than ours. Slide decks recycle the wins from months one to four because nothing comparable has happened since. Unrelated operational problems get attributed to it, a late shipment, an outage, a customer complaint, fairly or otherwise. And people begin asking whether it is still happening, not maliciously but because they genuinely do not know.

Underneath all of that is one fact about the fuel. Kickoff energy comes from novelty, executive attention, and the absence of any real outcomes to argue about, and by month seven all three are gone. Novelty wears off because humans habituate. Executive attention moves to the next item on the strategy agenda, which is how executives work and is entirely rational. And outcomes have started landing, some of which disappointed people, so the programme has made its first enemies.

Without a structural change to how the programme runs, the gravity of normal business pulls everything back. People revert, not out of preference, but because the new way needs sustained energy to hold in place and the old way needs none. Which suggests that most transformations do not fail at quarter three so much as reveal at quarter three that they were built to fail from the start, with the kickoff energy masking it.

What survival looks like structurally

Programmes that get through and into the operating-norm phase tend to have made a few choices early and held to them. None are complicated, and all of them cost something at the point where they are easiest to skip.

The win condition has to be a number the business already tracks. Defining success as completing the implementation, or training eighty percent of users, does not survive contact with quarter three, because neither is a thing the CFO was worried about in the first place. Cycle time, cost per unit, on-time delivery, conversion rate: something already on a dashboard, visibly bending by month six. Where that curve has not moved, there is nothing to defend the programme with when attention runs out.

Sponsorship is the other structural variable, and it is closer to existential than most plans assume. The default trajectory after a sponsor change is unwind, and surviving one takes deliberate work to re-anchor the incoming sponsor rather than an assumption that the mandate transfers. Any programme that will outlast its sponsor’s likely tenure needs that written into the plan rather than discovered halfway through.

Two smaller things matter more than they look. A visible kill option, meaning a stated set of conditions under which the programme stops, creates a kind of urgency that kickoff energy cannot sustain on its own. And the transformation team should be a temporary structure: by month nine its members belong back in the line organisation with the new way of working written into their jobs. A permanent transformation team still running at month twelve is usually a sign that nothing was ever operationalised, and that the programme has settled into performing transformation activities indefinitely.

If you are already in it

Recognising the symptoms late is the normal case rather than the exceptional one, and there is a move that tends to work. Not a relaunch, which is marketing and which people see through immediately. A structural reset, which starts by admitting the original plan is partly broken and then amends it in public.

Three things make it up. A thirty-minute steering committee with the original sponsor answering what to accelerate, what to kill and what is missing, producing a one-page revised plan communicated in the sponsor’s voice within five working days. A handover of authority from the transformation team to the operational leaders, with the team moving into support, which is the step that actually converts activity into operating norms. And a public re-baselining of the success metric, whether that means naming a better one or resetting a timeline that was always optimistic.

The reset is not free either. Announcing that the plan was partly wrong costs the sponsor something, and that is precisely why it works when a relaunch does not. It is also why most programmes do neither, and quietly wind down instead.

Get in touch if this sounds like your situation, or read more about how we run engagements.