Technology
The AI Productivity Paradox Is Already Here
Almost everyone now uses the tools, yet the aggregate numbers stubbornly refuse to move

There is a strange quiet at the center of the artificial intelligence boom, and it sounds like a productivity statistic failing to rise. Surveys suggest that a large share of knowledge workers now reach for a chatbot or a code assistant during an ordinary working day. The tools are genuinely useful, sometimes startlingly so. And yet, when economists go looking for the corresponding surge in output per hour across whole economies, they find something closer to a shrug. The gap between how transformative the technology feels and how little it has yet shifted the macro numbers is the defining puzzle of the moment.
An old pattern wearing new clothes
Economists have a name for this disappointment because they have lived through it before. The arrival of the personal computer in offices was followed by years in which measured productivity barely budged, a lag famous enough to earn its own quip about computers appearing everywhere except in the statistics. The resolution, when it came, was not that the machines were useless. It was that organisations needed time to rewire how they worked around the new capability. Wiring, in the end, takes longer than buying.
The same logic applies now with extra force. A worker who drafts emails faster has saved minutes, but those minutes only become productivity if the surrounding process is redesigned to use them. Most firms have bolted the tools onto unchanged workflows, which captures the convenience while leaving the deeper gains stranded.
Where the time actually goes
Look closely at how the tools are used and the paradox softens. A great deal of early adoption is concentrated in tasks that were never the binding constraint on a business: polishing a memo, summarising a thread, generating a first draft that still needs careful human revision. These are real time savings, but they accrue in small, scattered pools rather than in one measurable channel. Saved minutes that are spent on more email, or on checking the machine's work, do not show up as growth.
There is also a quieter cost. When a tool produces plausible text quickly, someone has to verify it, and verification of fluent, confident output is cognitively expensive. In some workflows the editing burden offsets a meaningful slice of the drafting gain, which is precisely the kind of friction that aggregate figures absorb without comment.
The measurement problem
Part of the paradox may be that we are measuring the wrong things. Productivity statistics were built for an industrial economy of countable units, and they have always struggled with quality, variety, and intangible improvements. If a customer query is now resolved a little better, or a designer explores three more options before settling, the gain is real but largely invisible to the national accounts. The technology may be improving the texture of work faster than it is improving its tonnage.
Who captures the gains
Even where genuine efficiencies emerge, they do not automatically become measured growth. They can be handed to customers as lower prices, absorbed as slack, or competed away across an industry until no single firm shows an advantage. History suggests the largest returns flow to organisations willing to do the unglamorous work of restructuring jobs and processes, not merely to those that buy the most licences. That work is slow, political, and easy to defer, which is exactly why the numbers wait.
The honest conclusion is that the paradox is a description, not a verdict. Adoption has plainly run ahead of transformation, and transformation is the part that registers in the statistics. The interesting question is no longer whether the tools work, but whether institutions have the patience and the appetite to rebuild themselves around what the tools make possible. The technology has arrived. The reorganisation has not, and that is the variable still worth watching.
The daily digest
One email each morning, all the day’s reporting.