When Digital Transformation Loses Sight of Whom It Serves
There is a pattern that repeats itself with enough frequency to deserve serious attention: an organisation announces a digital transformation, allocates budget, hires consultants, implements platforms and, two years later, discovers that almost nothing changed where it mattered. Processes are still slow. Front-line teams never adopted the tools. And management, which oversaw everything from control dashboards, cannot explain with any precision what went wrong.
What went wrong, in most cases, was not technical. It was conceptual. The transformation was designed to modernise, not to serve. And that difference, apparently subtle, has measurable consequences.
Global spending on digital transformation surpassed 2.15 trillion dollars in 2024 and is projected to reach 3.9 trillion by 2027, according to IDC estimates. With those volumes of investment, the question of return can no longer be answered with technical indicators. McKinsey and Boston Consulting Group have consistently documented that around 70% of digital transformations fail to meet their objectives. Not for lack of technology. For lack of alignment between the investment and the purpose of the system being transformed.
The Forbes Technology Council recently published a collective analysis in which technology leaders from various industries attempt to articulate something the sector has been slow to name clearly: that every digital transformation needs to begin with a question about whom it serves, before selecting any tool whatsoever.
What emerges from that collective exercise is not an operational manual. It is a diagnosis of how organisational systems produce, without intending to, transformations that transform nothing at all.
The Problem Is Not in the Technology but in the Order of the Questions
There is a sequence that becomes corrupted with surprising ease. An organisation identifies an available technology, evaluates it technically, approves it budgetarily and then, retroactively, seeks to justify its adoption with some strategic objective. The order is inverted from the very beginning, yet nobody in the decision-making chain has any incentive to point that out.
What several of the experts consulted by Forbes highlight, each from their own sectoral experience, is that this inverted order is not an isolated error. It is a structural tendency. Organisations learn to speak the language of transformation without changing the logic with which they make decisions about it.
One of the principles that appears most frequently in the collective analysis is that of anchoring each digital initiative to a mission outcome before selecting any platform. Not as a rhetorical exercise, but as an operational filter: if an initiative cannot articulate precisely what outcome for what person or what process it will improve, that initiative should not advance. This principle seems obvious when written out. Its absence in practice is what explains a large share of the documented 70% failure rate.
The underlying problem has to do with how organisations measure the success of their technology teams. When internal indicators reward tool adoption, implementation speed or the number of initiatives launched, digital leaders respond rationally to those incentives. They produce initiatives. They adopt tools. They launch projects. And the system is satisfied with activity that generates no change in what truly matters.
The proposal to require a mission metric alongside every technical indicator is, in that context, a governance mechanism, not merely a planning practice. It forces teams to step outside the technical register and connect with real operational impact. And it forces leadership to validate that connection before approving resources.
The Silent Fragility of Leadership That Manages from the Dashboard
There is an organisational figure that appears in these conversations implicitly but consistently: the digital leader who manages transformation from above, with access to aggregated metrics, without direct contact with the processes they claim to be transforming. This is a figure that produces a sophisticated illusion of control.
From a well-designed control dashboard, everything seems to be progressing. Initiatives are showing green. Deadlines are being met. Budgets are being executed. What the dashboard does not show is whether front-line teams are actually using the tools, whether the tools solve the problems those teams face, or whether the transformation is generating more friction than it eliminates.
One of the most uncomfortable arguments in the collective analysis published by Forbes is that real transformation is, by its very nature, bottom-up. It is born in the teams closest to concrete work, not on the executive floors. The role of leadership is not to manage transformation from above but to create the conditions for the people who face day-to-day problems to identify what is worth escalating.
This has direct implications for how transformation programmes are designed. A programme designed exclusively from the top, without genuine feedback mechanisms from the front line, is building on a partial diagnosis. It can be technically impeccable and operationally irrelevant at the same time.
The warning signal that several experts describe is the project that leadership and the delivery team describe in entirely different terms. When leadership speaks of efficiency and the team speaks of additional workload, it is not a communication problem. It is evidence that the transformation was not designed with the real context of those who have to execute it in mind. When language is not shared, neither is the transformation.
The other angle that emerges with force in this analysis has to do with timing. Organisations tend to diagnose their transformations when failure is already visible: adoption is low, results are not materialising, the budget has been exhausted. But the fragility usually takes hold much earlier, during the period when the system still functions formally but already contains contradictions that nobody is naming. The project moves forward but there is no clarity about what behavioural change is expected from whom. Indicators are reported but nobody is certain whether they are measuring the right things. Change is announced but the system's incentives continue to reward exactly what the change was supposed to replace.
Treating Culture as a Dependent Variable Is the Most Expensive Mistake
There is a tendency that persists in many digital transformation programmes despite the accumulated evidence against it: treating organisational culture as a secondary problem that will resolve itself once the technology has been implemented. It is the operational equivalent of believing that adoption will come on its own once the product is good enough.
It does not come on its own. It never has.
Prosci, one of the leading reference organisations in organisational change management, has documented that projects with high-quality change management are six times more likely to meet their objectives than those with poor change management. That multiplier does not operate on the technology. It operates on the people who need to modify their everyday behaviour in order for the technology to produce value.
The reason many digital transformations fail culturally is not that people are inherently resistant to change. It is that change is presented to them as an additional burden, designed without their participation, that adds complexity to their work without eliminating any of the friction that already existed. When transformation does not remove real obstacles for those who execute it, resistance is a completely rational response.
What several of the experts from the Forbes Technology Council highlight, each from different sectoral angles, converges on the same point: the order of the questions determines the outcome. When an organisation begins by asking what work it should no longer do, what specific friction it wants to eliminate, what concrete outcome it wants to improve for an identifiable person, it is designing a transformation with real possibilities of being adopted. When it begins by asking what tool it should implement, it is building an answer to a question it has not yet formulated.
There is also a financial dimension that is rarely named with sufficient precision. Transformations that produce what some experts call "efficiency theatre" — visible activity without impact on outcomes — are not merely inefficient. They are costly in a compounding way. They consume investment budget, generate organisational change fatigue, erode the credibility of digital leadership for future initiatives and, in many cases, install systems that are subsequently expensive to replace or dismantle. The cost of a poorly aligned transformation is not paid only in the project budget. It is paid for years in the system's reduced capacity to transform again when it needs to.
Organisational Maturity Is Measured by What the System Does Without the Hero
The synthesis that emerges from this collective analysis is not a set of tools or an implementation protocol. It is a diagnostic criterion for evaluating the structural maturity of a transformation before failure becomes visible.
An organisationally mature system for digital transformation has three characteristics that do not depend on any specific technology. First: it can articulate with precision what change in outcome, for whom, justifies each investment. Second: it has genuine mechanisms for the knowledge of teams closest to concrete work to reach those who make design decisions. Third: its success indicators measure behaviours and outcomes, not activity.
When those three conditions are absent, the transformation can advance for months with all indicators showing green and produce, at the end of the cycle, exactly the same organisation it set out to change. Only with more expensive tools.
What the accumulated evidence — both academic and from executive practice — suggests with considerable consistency is that the digital transformations that produce long-term value are not those that adopt the best available technology. They are those that built, before selecting any tool, sufficient clarity about what real problem belonging to what real person they were trying to solve. That clarity does not require a sophisticated technological architecture. It requires organisational discipline to resist the temptation to answer questions that nobody formulated, with solutions that nobody requested, for audiences that were never consulted. Organisations that learn that discipline do not need a hero to lead them forward. They need a system that already knows where it is going.
