The room was full of smart people. The strategy deck was polished. Leadership had approved the budget months earlier. And twelve months later, almost nothing had moved. It is the most common form of digital transformation failure I know.
I have watched this play out more times than I would like to admit. Across transformation mandates at companies including EnBW and L’Oréal, and across media businesses and agencies over the past fifteen years, I have seen well-funded digital initiatives stall, shrink, and quietly disappear. Not because the technology was wrong. Not because the market shifted. The conditions for success were simply never in place.
In my work at Linelia, digital transformation failure is what I keep coming back to:
Most digital transformation failure does not happen in execution. It happens before the first kick-off meeting.
Here is what that looks like in practice.
The problem is rarely the technology
When a transformation runs into trouble, the instinct is to look at the tools. The platform was wrong. Vendors had promised too much. Integration proved more complex than expected. These are real problems. But they are almost never the cause of failure. They are symptoms.
The actual failure usually happened three to six months earlier, in the room where the transformation was first defined. Specifically: no one defined what “digital transformation” actually meant for this organisation, at this moment, with these people and this budget. Everyone assumed it. A vague phrase became a project mandate. The mandate became a programme. The programme hired vendors and bought software. And then, somewhere in month four, someone asked a question no one could answer: what, exactly, are we trying to change?
The same applies to methodology. Agile ceremonies, OKR frameworks, design thinking workshops — these can become rituals that signal progress without driving it. I have sat in sprint reviews where no one could explain what was being transformed, or why. The process was running. The transformation was not.
Technology does not transform organisations. Decisions do. And if the decisions are not made clearly at the start, the technology becomes a distraction from the fact that they were never made at all. This is the root of most digital transformation failure.
Technology does not transform organizations.
Decisions do.
Transformation without a mandate
The second pattern I see consistently: leadership announces a transformation but never assigns the authority to drive it. Someone gets a title. A steering committee forms. A kick-off happens. But when the first difficult trade-off arrives, and it always does, no one is empowered to make the call.
Many transformations are announced not because leadership has identified a specific problem that needs solving, but because the topic is trending. Competitors are doing it. The board is asking about it. A consultant has presented a convincing deck. And so the program begins, with senior sponsorship that is visible on the launch slide and largely absent from the first difficult conversation. That is not a mandate. That is a press release.
This is particularly common in large, matrixed organizations where the culture defaults to consensus. Transformation requires someone with the mandate to say: we are moving in this direction, and we are stopping that. Without that clarity, the project becomes a negotiation. Every decision gets relitigated. Momentum slows. And eventually the transformation quietly becomes business as usual, just with more meetings.
I see this in interim mandates regularly. Organisations bring in external leadership precisely because the internal structure has struggled to move. But if no one has clearly defined the mandate from day one, even an experienced interim manager is navigating without a map.
The mandate question is not about hierarchy. It is about clarity. Who decides? Who has the right to stop something? And who carries accountability when the transformation stalls? If those questions do not have clean answers on day one, digital transformation failure is already underway.
If the mandate is not clearly defined from day one, even an experienced interim manager is navigating without a map.
The roadmap that ignores the organisation
The third pattern is perhaps the most seductive, because it produces beautiful slide decks.
An organisation invests significant time and money in a transformation roadmap. The team defines workstreams, sets milestones, and maps dependencies. It looks thorough. It looks serious. And then it runs straight into the organisation’s actual operating reality and stops.
Most transformation roadmaps are built around what needs to change, not around the organisation’s current capacity to absorb change. They treat the people, the processes, and the culture as a fixed backdrop against which the transformation unfolds. But those things are not fixed. They push back. And if the roadmap does not account for that, it becomes a document that describes the future without any honest reckoning with the present.
A transformation plan that ignores the organisation’s change capacity is not a plan. It is a wish.
Real transformation planning starts with an honest assessment of where the organisation actually is. Not just technically, but culturally. What is the leadership team’s appetite for disruption? Where are the informal power structures that will slow things down? What has been tried before and why did it stop? These questions are harder than building a Gantt chart. They are also more important.
A transformation plan that ignores the organisation’s change capacity is not a plan. It is a wish.
How to avoid digital transformation failure: what has to happen first
None of this is to say that transformation is impossible. It is not. But the organisations that move through it successfully tend to share a few things in common.
They define what they are actually trying to achieve in concrete terms, not aspirational language. They identify who has the authority and the accountability to drive change, and they protect that person’s mandate. Before committing to a pace and a scope, they take an honest look at their actual capacity for change. And they treat the early phase not as a formality to get through, but as the most important work the transformation will produce.
Getting the setup right is not the slowest path to transformation. It is the fastest one. The organisations that skip it spend the next eighteen months recovering from a start they should have taken more seriously.
This is where Linelia’s transformation work typically begins: not with a platform recommendation, but with a set of hard questions that most organisations find easier to defer than to answer.
Common questions
Most transformations stall not because of the technology, but because of a gap between strategic intent and execution capacity. The objectives are vague, the mandate is unclear, or the plan does not account for the organisation’s actual readiness to change. These are setup problems, and they rarely get resolved once the programme is running.
A transformation mandate is explicit authority to make decisions, stop things that are not working, and hold people accountable for progress. Without it, even a well-resourced transformation becomes a slow negotiation. It is not about hierarchy. It is about clarity of ownership.
Readiness is less about having the right technology and more about having the right conditions: clear strategic intent, leadership alignment, honest understanding of current capability, and appetite to make real decisions under uncertainty. A useful starting point is an honest assessment of where your organisation is, not where you would like it to be.
External support, whether in the form of interim management, advisory, or project-based consulting, is most valuable when an organization needs to move faster than its current structure allows, when a specific challenge requires outside objectivity, or when a critical gap opens mid-programme. The key is defining the scope and mandate clearly from day one, so the external partner can actually move at the pace the situation requires.
If your organisation is at one of these inflection points, whether a transformation is just getting started or has already hit its first wall, I am happy to talk through what the setup should look like. Reach out via the Linelia contact page or connect with me on LinkedIn to start the conversation.
Comments are closed