- Digital Economy Dispatches
- Posts
- Digital Economy Dispatch #283 -- Why AI Adoption is Not AI Delivery
Digital Economy Dispatch #283 -- Why AI Adoption is Not AI Delivery
AWS published its annual Unlocking the UK’s AI Potential report last week. Read alongside Making AI Work for Britain, which I launched the same week, the two documents broadly agree on the diagnosis. Where they part company is more interesting.
A new study, supported by AWS, exploring the state of AI adoption in the UK was published last week. The temptation, when reading the AWS adoption numbers, is to feel reasonably good. Britain is ahead of others in Europe. Adoption is rising. The productivity gains are real. These advances should be celebrated. But the report's most important finding is not in its headline figures. It is in the gap they conceal, and how we address that gap is critical to the UK’s future.
A Baseline for Understanding AI in the UK
The AWS report’s headline finding is that AI adoption in the UK has reached 64% of organisations, up from 52% a year ago. Britain is now ten percentage points ahead of the European average. The productivity benefits, for those who have committed, are real: 68% report gains, 72% expect AI to drive growth in the coming year, 79% say their innovation timelines have accelerated. These are not trivial numbers, and the report is right to lead with them.
But the most arresting figure in the document is a date: 2102. That is the year by which every UK adopter will reach the most advanced stage of AI use if progress continues at its current pace. That’s right. So, while AI adoption has surged, advanced use that rewires how organisations operate has barely moved from 23% to 24% in twelve months. The problem is that the £35 billion productivity opportunity AWS identifies sits behind that 24% number, not the 64% one.
Viewed in this way, the AWS diagnosis tracks closely with the book’s argument. Britain’s danger is mistaking the appearance of transformation for its substance. Upgrading to Microsoft Copilot or buying ChatGPT licences across the workforce is all very well. But it is an adoption metric. It is not an AI strategy. The gap between adoption and advanced use is not a pacing problem to be solved by installing more licenses. It is a structural problem about how organisations procure, deploy, and integrate AI to improve today’s way of working.
Two findings in the report reinforce the book’s central argument, especially directly. The first is that 78% of organisations say they are more likely to adopt AI if the public sector integrates it into its own services. The second is the public sector itself: 31% of public adopters now sit at the most advanced stage of use, against 24% across UK businesses overall. Where the government has gone, it has gone deeper. This is the empirical case for what the book describes as consolidating demand. Government adoption is not just about better services. It shapes the market for everyone else. The 35% of UK startups citing public sector demand as a top scaling factor closes the loop from the supply side.
What the Report Does Not Say
Where the AWS report and the book part company is on the supply side. AWS’s three recommendations are entirely demand-side: move from adoption to transformation, scale AI across public services, and close the skills gap. All sensible. None of them asks who supplies the AI that Britain is being encouraged to adopt more deeply.
This is not a failing of the research. It is a function of who commissioned it. An AWS report is not the place to interrogate hyperscaler concentration. But the report’s own data raises the question. 98% of UK AI startups now build on the cloud, and the report presents this as a clear strength. The book asks a harder question. An AI economy built almost entirely on three or four foreign cloud stacks is a different proposition from one with a diverse supply. The £35 billion is meaningful for British GDP whether it accrues to British firms or to American platforms running British workloads. For headline output, those are the same thing. For strategic capability and fiscal sovereignty, they are not.
This is the silent lock-in the book takes seriously. It is not announced. It is built up incrementally, through routine technical decisions, until the cost of unwinding it exceeds the political capital available to do so. The AWS report frames cloud as table stakes. The book argues that the architectural decisions made at the bottom of the stack determine the strategic options available at the top, and that getting them right is something Britain has done before, in a different domain, within living memory. Anyone who lived through the GDS years will recognise the pattern.
The AI Skills Need
The third place where the book pushes further is on skills. The AWS report’s analysis is detailed: 49% of organisations cite skills shortages, hiring timelines have stretched from 5.5 to 8 months in a single year, and organisations are paying an average 41% salary premium for strong AI capability. All of this is correct, and all of it is workforce-framed. The skills problem is presented as workers needing to learn AI tools.
The harder skills gap sits upstream. The most consequential AI capability gap in Britain is not down at the desk level. It is up in senior leadership and procurement: the people deciding what to buy, from whom, on what terms, and with what exit options. A workforce trained on a particular vendor’s stack but unable to evaluate the strategic implications of building on that stack has not solved the problem. It has shifted it upstream and made it harder to see. The smart-buyer skills, the ones the state and large organisations need most, are not in the AWS skills count.
Delivering on the UK’s AI Future
Read together, the AWS report and Making AI Work for Britain are stronger than either alone. The report makes the empirical case that Britain has a problem worth solving. The book makes the structural case for how to solve it. Where the report says scale faster, the book asks scale toward what.
The question I would put to any senior leader reading the AWS numbers this week is the one the report itself does not quite ask. It is not whether to adopt more AI. It is whether your adoption is taking you somewhere you actually want to go, on terms you would accept if you were buying a building or signing a twenty-year lease.
Adoption is the easy part. The architectural choices underneath it are what will matter in five years.