In March, an operations analyst discovers that the weekly reporting pack — eleven hours of his life, every week, for six years — can be assembled in four.
He does not tell anyone. This is not deviousness; it is instinct, and the instinct is correct. He spends the first genuinely empty Friday afternoon of his professional life reading about something entirely unrelated to logistics, and feels, for about three weeks, that a small and private justice has been done.
In April, someone notices the pack has been arriving on Thursday rather than Friday. Nothing is said. In May, a colleague in another team refers, in passing, to “when the pack lands on Thursday,” and the sentence goes unchallenged, because it is now simply a description of reality. By June, Thursday is the deadline. Nobody moved it. No one held a meeting about it, no policy was amended, no manager made a decision they would recognise as a decision. The deadline moved the way a shoreline moves.
Then, because the team is now visibly capable of more, a second pack appears — the regional breakdown, discussed for years and always deemed impossible. It is not impossible any more. It is a genuine improvement to the business, everyone is pleased, and the analyst builds the template.
By July he is working eleven hours a week on reporting again.
Ask him what happened and he will describe a series of reasonable events, each of which he would defend individually. He is not overworked because of a villain. He is overworked because of a ratchet, and the defining property of a ratchet is that it turns one way, quietly, under load, with a mechanism so ordinary that nobody thinks to look at it.
What the eight-month study actually found
In February 2026, the Harvard Business Review published research by Aruna Ranganathan and Xingqi Maggie Ye who had followed roughly 200 employees at a US technology company for eight months as generative AI worked its way through their jobs. It is one of the few studies of the period that watched the same people for long enough to see the second-order effects rather than the launch-week enthusiasm.
The tools worked. That is worth stating plainly, because the finding is not a story about disappointing technology. People moved faster. They handled more kinds of task. By any reasonable measure of individual capability, the intervention succeeded.
And 83% of them said their workload had increased.
The researchers identified three distinct mechanisms, and it is worth sitting with each, because none of them look like a problem while they are happening.
Task expansion. Work that had previously been out of reach became accessible, so people reached for it. Not because they were instructed to, but because the barrier that used to make it a non-question had gone. The regional breakdown was impossible for six years; the moment it stopped being impossible, it stopped being optional, without anyone ever converting it from one to the other.
Blurred boundaries. Work began leaking into the interstitial spaces that used to be breaks. If a thing takes ninety seconds instead of twenty minutes, it can be done in a lift, in a queue, at 22:40, between two other things. Each individual instance is trivially small, which is precisely why none of them ever gets refused. The working day did not get extended by decision. It got extended by capillary action.
Multitasking. With execution faster, people ran more threads simultaneously. This is the most insidious of the three, because sustained partial attention produces a strong internal sensation of productivity while degrading the quality of thought — and the sensation is what people report, while the degradation is what shows up three months later as fatigue nobody can source.
The common feature of all three: nobody chose them. There was no moment at which an organisation resolved to spend its AI dividend on intensification rather than on quality, or margin, or rest. In the absence of a decision, the system defaulted to more. Systems generally do.
The oldest pattern in the history of technology
If this feels novel, that is only because we are inside it. It is one of the most thoroughly documented patterns in economic and social history, and it has been observed at least twice with total clarity by people nobody listened to.
In 1865, the English economist William Stanley Jevons published The Coal Question, addressing a debate about whether Britain’s coal reserves would last. The prevailing view was reassuring: engines were becoming dramatically more efficient, therefore less coal would be needed. Jevons demolished it in a sentence that has since been named after him.
“It is wholly a confusion of ideas to suppose that the economical use of fuel is equivalent to a diminished consumption. The very contrary is the truth.”
— William Stanley Jevons, The Coal Question, 1865
His logic was simple and inescapable. Efficiency reduces the cost of using something. Reducing the cost of something increases the demand for it. Watt’s improved engine did not reduce Britain’s coal consumption; it made steam power cheap enough to put in places it had never been, and consumption rose by an order of magnitude. Efficiency was not the brake. It was the accelerator.
A century later, the historian Ruth Schwartz Cowan asked the domestic version of the same question. Her 1983 book More Work for Mother traced household technology from the open hearth to the microwave and confronted a fact that ought to have been a scandal: after washing machines, vacuum cleaners, running hot water, gas ovens, commercial flour and refrigeration, American women were spending about as many hours on housework as their great-grandmothers had.
Cowan’s explanation was not that the appliances were bad. They were transformative. Several things happened at once. Work previously done by servants, husbands and children was quietly absorbed by one person, because the machines made it a one-person job. And — the part that matters here — the standard rose to meet the new capability. Weekly laundry became daily laundry. Acceptable cleanliness became a moving target that tracked, almost exactly, the capability of the equipment available to achieve it. The washing machine did not buy time. It bought a higher definition of clean.
That is the mechanism we are living in now, running at software speed. Cowan’s ratchet took decades to turn. Ours turns in about a quarter.
Two accurate reports of the same event
The strangest artefact of this period is a pair of statistics that appear to contradict each other and do not.
The Upwork Research Institute surveyed 2,500 executives, employees and freelancers across four countries and found that 96% of C-suite leaders expected AI to raise productivity — while 77% of employees actually using the tools said those tools had added to their workload. A further 47% said they had no idea how to deliver the productivity gains being expected of them.
The standard reading of this is a communication gap: leadership doesn’t understand the coalface, someone should run a listening tour. That reading is comfortable and it is wrong, because it assumes one of the two groups is mistaken.
Neither is. They are describing the same event from opposite ends of the ratchet. At the organisational level, output per person genuinely rose — the executives are reading their instruments correctly. At the individual level, the work genuinely became heavier — the employees are reading theirs correctly too. Both measurements are accurate. The gain and the cost simply landed on different people, and there is no single vantage point inside the organisation from which both are visible at once.
The Harvard data shows exactly where each landed. Burnout was reported by 62% of associates and 61% of entry-level workers, against 38% of C-suite leaders. The people who set the pace are not the people who run at it. This is not a moral failing on the part of leadership; it is a structural feature of how the information travels. Throughput is legible upward. Strain is not. A dashboard will show you a rising line months before it shows you what the line cost, and by then the line is the baseline and the baseline is not negotiable.
What actually gets consumed
It is tempting to describe all this as a story about time, but time is not really the resource being eaten. The resource being eaten is slack.
Slack is the loose, uncommitted, faintly embarrassing space inside a working system. The gap between finishing one thing and starting the next. The Thursday afternoon with nothing due. The meeting that ended early. The conversation in the corridor that had no agenda and produced, six weeks later, the only good idea of the quarter.
On any dashboard, slack is indistinguishable from waste. That is its central tragedy. It has no output, no ticket number, and no defender in a budget meeting. Which makes it the very first thing an efficiency programme finds, and the very last thing anyone thinks to protect.
But slack is where several things happen that happen nowhere else. It is where people learn — not through training, but through the unhurried repetition and reflection that turns procedure into judgement. It is where people notice: the mis-stated assumption, the number that looks slightly wrong, the client who has gone quiet. Noticing requires spare attention, and spare attention is the first casualty of running three threads at once. It is where people recover, and a system with no recovery capacity is not efficient but brittle, in the specific engineering sense that it has no ability to absorb a shock without deforming.
And it is where people ask whether the work is the right work. This is the most valuable function of slack and the easiest to lose, because the question only occurs to people who have a moment in which nothing is due. Fill every moment and you get an organisation that executes with tremendous velocity and never once asks where it is going.
Here is the uncomfortable arithmetic. AI creates a large, visible, easily measured productivity gain. Slack is a large, invisible, entirely unmeasured buffer. When the gain arrives, the pressure to convert it into output falls first on the part of the system that cannot demonstrate its own value. The buffer is consumed before anyone realises it was an asset, and its absence is only detectable later, by the strange fact that nobody in the organisation seems to be learning anything or catching anything early.
The four positions on the ratchet
The pattern presents differently depending on where you are standing. Four positions, and almost everyone is in one of them right now.
The Absorber. Discovers a genuine efficiency gain and quietly reinvests all of it in more output, telling no one. The motives are usually decent: pride in the work, a wish to be useful, or a well-founded suspicion that admitting to spare capacity is professionally unwise. The effect is to set a new baseline for everyone, including themselves, on the basis of a capability they never disclosed. Absorbers are rewarded exactly once, and measured against the new level permanently. The tell is that they cannot explain how their workload grew, only that it did — and that when they eventually slow down, it registers not as a return to normal but as a decline.
The Sprawler. Responds to lowered barriers by expanding scope in every direction. Everything now feels doable, so everything gets attempted: the second report, the side analysis, the redesign nobody asked for. The work is real and often good. But scope acquired because it is possible, rather than because it is important, has no natural limit, and the Sprawler ends up carrying nine responsibilities at a level of attention appropriate to three. Their year-end review says “broad impact.” Their calendar says something else. The Sprawler’s error is treating capability as an instruction.
The Leaker. Never took on extra work and never agreed to longer hours, yet works appreciably more than a year ago. The mechanism is the ninety-second task: small enough to do in a queue, on a sofa, at 22:40, and therefore never large enough to justify refusing. The working day did not expand by decision; it expanded by a thousand individually trivial concessions, none of which would survive being described out loud as a policy. Leakers are usually the last to recognise the problem, because at no point did they do anything unreasonable.
The Ratchet-Setter. Sits above the work, watches throughput rise, and adjusts the expectation upward — reasonably, incrementally, and without ever having produced at the new rate personally. This is not villainy; it is the most natural act in management, and the information reaching them fully supports it. The rising line is real. What the line does not contain is the multitasking load, the evaporated slack, or the fact that the gain was one-off while the expectation is permanent. The Ratchet-Setter’s characteristic mistake is to treat a capability ceiling as a floor. Their characteristic surprise arrives around month nine, in the form of resignations from people who never once complained.
How to hold a line
The first thing to accept is that the ratchet has no author. There is nobody to persuade and nothing to appeal. It is a default that operates in the absence of a decision, which means the only counter available is an explicit decision, made early, and said out loud.
If you lead an organisation: name what the gain is for. There are four possible destinations — more output, higher quality, wider scope, or recovered capacity — and if you do not choose, the system chooses more output every single time. Choosing is not a soft gesture; it is the only lever that exists. And treat slack as infrastructure rather than waste. Some of the most durable firms run deliberate, funded unproductivity — protected time with no deliverable attached — not from generosity but because they have worked out that a system at 100% utilisation has no capacity to learn, notice, or absorb anything unexpected.
If you manage a team: make baseline changes visible. When a deadline moves earlier or a new deliverable appears, say so explicitly, in writing, as a change — because the danger is not the change itself but its silence. A baseline that everyone can see can be discussed and, if necessary, reversed. A baseline that arrived by drift cannot even be identified. And notice that your best performers are the ones setting the pace for everyone else, usually without meaning to. The Absorber on your team is quietly rewriting the standard your whole department will be held to.
If you are the one doing the work: stop treating your saved time as a private windfall to be hidden, and start treating it as a negotiating position to be spent deliberately. Say what you are doing with it — depth on the important thing, the analysis nobody has had time for, the review step you always skipped. Time claimed for a stated purpose is defensible. Time simply not visible gets reallocated by someone else. And learn to state what you did not do and why: the scope you declined, the request you pushed back a week. In an environment where everything is possible, the ability to say what you deliberately left undone is the only remaining evidence that judgement is being exercised at all.
If you are early in your career: understand that you have arrived at the top of a ratchet and will be told the current pace is normal. It is not normal. It is roughly three years old, and the people who set it did not have to sustain it while learning the job. Build your own protected slack before anyone can accuse you of having spare capacity, and be extremely careful about being the fastest person in the room. Speed is rewarded once. The baseline it creates lasts.
The uncomfortable truth
The prevailing story about AI and work is one of eventual liberation. First a difficult adoption period, then the productivity dividend, then — the four-day week, the reclaimed evening, the human hours restored. It is a decent story and it has one flaw: it assumes that the gain, once created, flows to the person who created it. Nothing in the history of technology supports that assumption.
The gain from the steam engine was real, and it was spent on more steam. The gain from the washing machine was real, and it was spent on cleaner houses. Neither was stolen. In both cases the capability was converted, invisibly and almost immediately, into a higher standard of what counted as adequate — and the higher standard, once established, was never renegotiated downward. Nobody in 1900 proposed returning to a fortnightly wash.
What makes this cycle different is only its speed. Cowan’s ratchet turned over generations. Ours turns over quarters, which means a person can now watch the entire arc happen to them personally — discover a gain in March, see it absorbed by June, and be described as tired by July — while remaining unable to point at the moment anything changed, because no such moment exists.
So the question worth asking is not whether AI will give you your time back. That framing has already conceded the argument, because it treats the outcome as something the technology decides.
The question is what your organisation decided to do with the gain, and whether anyone can remember deciding. If nobody can, that is not an oversight. That is the answer. In the absence of a decision, the ratchet decides, and the ratchet has exactly one setting.
Everyone is waiting for AI to hand back their time. It already did. It arrived in March, on an ordinary Wednesday, and it was gone by June — and the most unsettling part is not that it was taken. It is that nobody took it.