Your AI Strategy Is Digital Transformation With Better Branding

In the last three years, the volume of corporate communications announcing AI transformation strategies has reached a level that makes it difficult to identify a large organisation that is not, by its own account, in the process of transforming itself through AI. The language is consistent across industries, geographies, and organisational types: productivity, scale, efficiency, insight, augmentation. The strategies vary, but they share a framing. The company is changing. AI is the agent of change.

I want to make an argument that is uncomfortable for organisations that have invested significantly in AI strategies of the kind currently being announced. Most of what is being called AI transformation is not transformation. It is digital transformation — the process of making existing processes faster and cheaper through technology — with updated marketing language. And the reason this matters is that digital transformation, done without asking the process-elimination question, has a consistent track record of producing expensive infrastructure in the service of unchanged institutional structures.

What Digital Transformation Actually Delivered

The digital transformation wave of the 2000s and 2010s produced genuine improvements. Processes that had been executed on paper became faster and more accurate when executed on software. Customer service that had required phone calls became accessible through web portals. Financial transactions that had required physical presence at a bank branch became executable from a phone.

These were real gains. But they were, in most cases, gains in the efficiency of existing processes rather than the elimination of processes. The bank that built mobile banking did not become a different kind of institution. It became a faster version of the same institution. The call centre that deployed IVR and self-service portals reduced call volume. It did not eliminate the problem that generated the calls.

The organisations that did change structurally were the ones that used technology not to accelerate their existing operations but to ask what their operations should be. M-Pesa is the most instructive example in the Kenyan context: it did not build a faster version of the bank branch. It asked what a payment infrastructure should look like for a population that had never had a bank account, and designed an answer from first principles.¹ The result was not an improvement on what existed. It was a different kind of infrastructure entirely.

The distinction in both cases is not the sophistication of the technology. It is the willingness to ask the right question: not "how can we do what we do faster?" but "what should we be doing, and how should we build a system to do it?"

The Pattern in Current AI Deployment

The current AI deployment wave is replicating the digital transformation pattern in most organisations. The evidence is visible in the products being purchased, the use cases being announced, and the metrics being used to evaluate success.

The products being purchased are overwhelmingly interface improvements: AI tools that make knowledge workers faster at the tasks they were already doing. Copilot tools that autocomplete emails and documents. Search tools that surface relevant information faster. Summarisation tools that condense documents. Meeting transcription and action item generation. These are genuine productivity improvements. They are not process redesigns. The processes they operate on — writing emails, reviewing documents, searching for information — are unchanged. The human is still doing the work. The AI is making the human faster.

The use cases being announced are predominantly augmentation narratives: AI helping the human do the same job better. The contract reviewer who uses AI to flag relevant clauses faster. The compliance officer who uses AI to search regulatory databases more efficiently. The financial analyst who uses AI to generate first-draft models. These are real improvements in individual productivity. They are improvements in the efficiency of processes that should, in many cases, be examined more fundamentally.

The metrics being used to evaluate success are telling. The dominant metrics are tasks completed per hour (faster is better), error rates in existing processes (lower is better), employee satisfaction with tools (higher is better). These metrics measure the efficiency of existing processes. They do not measure whether the right processes are being done.

The Question That Is Not Being Asked

The question that most AI strategies do not ask is: which of our processes should not exist?

This is not a radical question. Every organisation, on honest examination, runs processes that exist because they were designed for a world that has changed — for a compliance environment that was different, for a staffing model that no longer applies, for a technology constraint that no longer binds. The digital transformation wave created more of these processes, by digitising manual workflows without asking whether they should exist, and then building dependencies on them that made them harder to question.

An AI strategy built on this accumulated inheritance — one that asks "how can AI improve each of our processes?" rather than "which of our processes should AI eliminate?" — is not a transformation strategy. It is a maintenance strategy. It is the modernisation of an institutional structure that was never designed to be optimal and has never been interrogated at the level of design.

What the Gap Looks Like in Practice

Consider two organisations in the same industry, making different choices.

The first has deployed an AI copilot for its procurement team. With the copilot, team members process expense requests faster — they get AI-generated summaries of each request, flagged against relevant policy provisions, and can approve or reject with less manual review. Request processing time has fallen by thirty percent. The team is the same size. The process is the same process.

The second has redesigned its procurement process. Spending authority is encoded in a virtual card system. Employees spend within encoded limits without requiring approval. The procurement team's role has shifted: they manage vendor relationships, negotiate contracts, and oversee exceptions — the cases that fall outside the automated system's parameters. The routine approval workflow does not exist. The team is now doing work that genuinely requires human judgment.

Both organisations will report AI success metrics. The first will report faster processing times. The second will report process elimination. In five years, the first organisation will have a more efficient procurement team doing the same work. The second will have a fundamentally different cost structure and a procurement function that operates at a different level of complexity.

The difference between these two organisations is not the sophistication of the AI they deployed. It is the question they asked before they deployed it.

The Honest Question

I am not arguing that AI-assisted improvements are worthless. They are not. I am arguing that they are not what most AI transformation strategies claim them to be, and that the gap between the claim and the reality matters because it determines the decisions organisations make about where to invest.

An organisation that believes it is transforming through AI copilots is unlikely to also invest in the process redesign work that genuine transformation requires. The belief that the transformation is already happening is the primary obstacle to the work that would make it happen.

The honest question for any organisation claiming an AI transformation strategy is this: for the processes you are most proud of having improved with AI, did the AI do the work, or did it help your people do the work faster? If the answer is the latter, you have a productivity improvement. That is worth having. It is not worth calling a transformation.

The essays that follow push this argument further. If human accountability is the stated reason for keeping humans in the process — and it often is — the next essay examines whether that reason holds up under scrutiny.