Does AI reduce the effort needed to finish work well?
Background on this question
A quick first draft can feel like a breakthrough. The harder question is how much work remains before you can use it. Here, finished work means a result that meets the quality required for its intended use—for example, a change that works or an answer that resolves the customer’s problem. Count the time and effort spent checking, fixing and fitting it into the larger job, as well as money spent. Those costs decide whether AI gives you time back or moves the work elsewhere.
EM read · 2026-11-04 · Evidence reviewed 2026-11-04
AI will save effort on work people can readily check, even after they test and correct it
EM outlook · –
In 2027–2028, we expect AI to reduce the total effort needed for repeatable digital work when people can readily tell whether the result is correct and useful.
A developer still needs to test AI-generated code against the task’s requirements; a support agent needs to confirm that an AI-suggested answer actually addresses the customer’s problem. Where errors are difficult to detect, investigating and repairing them can consume the time saved by having AI produce the first version. These examples describe the checking people must do; they do not imply that every code change or customer problem is easy to verify.
We favor savings in the stated scope because the customer-support study found more issues resolved per hour, showing improvement in completed work. In METR’s early-2025 developer experiment, experienced developers working in familiar open-source repositories took 19% longer to complete issues when allowed to use AI. METR’s February 2026 update judges that developers likely benefited more from early-2026 tools, although selection problems prevent a reliable estimate of the change.
During 2027–2028, we expect teams to spread these gains by reusing requirements and checking routines across recurring tasks, rather than starting the review process afresh each time.
What this means
The prize is more room for difficult, worthwhile work. Compare finished work of the same quality with the full human effort it took, then use the capacity you recover to improve the service, tackle a neglected problem or give people time back.
Why we take this view
Two years for gains already observed in some assisted tasks to spread through workflow redesign. The forecast is about suitable workflows, with hard-to-verify work expected to lag; it is not a uniform productivity percentage.
What has to hold
Before deployment, the target work is repeatable and digital, has a clear acceptance test, and can be checked affordably. Quality standards stay fixed and delayed defects count.
Teams can select or redesign tasks instead of forcing every task through the same AI process.
The strongest rival
Even in the defined target workflows, selection and omitted review costs explain most apparent gains; lower effort does not survive a complete comparison.
Models become better at checking their own output, reducing the review burden even on complex work.
What would change our mind
Comparable later studies measure work completed to the required standard, total human effort and defects after handoff, with credible treatment of selection.
The gain disappears when review and downstream repair are counted, or persists when they are included.
Compare total effort at the same required quality in workflows selected before deployment, including later checking and repair.
Where this could lead
Checkable digital work takes less effort to finish
Base case · –
Teams lower total effort in repeatable digital workflows with clear acceptance tests and affordable verification. They define those conditions before deployment, then count the work all the way through handoff and repair.
What would make it happen
Existing assisted-work gains and improving developer experience favor wider gains over two years, with task selection and redesign driving the spread.
Conditions
The target workflow is repeatable and digital, with a clear acceptance test and affordable verification established before the comparison.
They count verification and later defects, then concentrate use where the full result improves.
Watch for
Comparable task cohorts show lower total effort at stable quality.
Benefits persist after the novelty of the rollout and include downstream repair.
Even promising workflows take more effort than they save
Alternative · –
The gain disappears even in repeatable digital work selected for clear outcomes and affordable checking. Finding hidden mistakes and fitting the output into the larger job takes more time and effort than expected; faster drafts fail to make finished work easier.
What would make it happen
This remains a live alternative throughout the adoption window, especially where correctness is expensive to establish.
Conditions
Verification and repair cost more than the team expected before rollout.
Selection of enthusiastic users or favorable tasks explains apparent gains that do not survive comparable full-work measurements.
Watch for
Blind quality review finds more defects in apparently faster work.
Time saved at generation returns as integration, correction or customer support.
Why this connects to When can work be delegated without checking every step?
EM interpretation
A result can be useful because a person caught its mistakes. Removing that review changes the job: the agent must detect failure, recover or ask for help. That is why productivity gains can arrive before dependable autonomy.
Track the human interventions behind a successful result before applying it to unsupervised work.
Why this connects to When is an AI deployment worth its total cost?
EM interpretation
Work becomes valuable when someone can use the result. A slower process can still be worthwhile if it produces something better or previously impossible; a faster draft can waste time and money if nobody needs it or finishing it takes too much effort.
The buyer’s gain and the supplier’s investment return are separate calculations.
Communications is a drafting-heavy occupation where the review burden decides who keeps time.
Perspectives
Joel Becker, Nate Rush, Beth Barnes and David Rein
authors of the early-2025 controlled developer study · 2025-07-10 · From the author’s own work
In their randomized study of 16 experienced open-source developers completing 246 issues, AI access increased completion time by 19%. They explicitly restrict what this says about other developers, settings or later tools.
Sources and passages
Publication date of this study report.
The study used early-2025 tools in developers’ familiar repositories; it is not an estimate for all work or present-day AI.
Joel Becker, Nate Rush, Tom Cunningham, David Rein and Khalid Mahamud
authors of the follow-up methods update · 2026-02-24 · From the author’s own work
judges that developers likely benefited more from AI in early 2026 than in early 2025, while warning that participation, task selection and time measurement make the size of that improvement hard to estimate.
Sources and passages
Publication date of the authored source.
This is a later team’s assessment of a changed experiment, not the same measurement repeated cleanly.
author reporting technical-worker self-assessments · 2026-05-11 · From the author’s own work
The survey reports substantial perceived value gains, while distinguishing value from task speed and cautioning that respondents can misestimate what AI contributes.
Sources and passages
Publication date of the authored source.
Self-report in a technical-worker sample, not audited customer economics or a measured effect on national productivity.
An internal study of employment and agent use at . It describes a changing hiring mix and demands on human attention at one growing AI company.
Publisher publication date, checked on original page.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
The proportion of junior technical hires fell even faster, from 27% to 9%.
Retained extracted text, character offsets [4420, 4494). Context (EM paraphrase): Anthropic’s October 2026 report describes its own workforce; junior employees’ share fell from early 2025, and technical hiring still grew in absolute terms. This is a changing hiring mix, not a count of jobs lost.
This acceleration makes human attention the bottleneck for agent output.
Retained extracted text, character offsets [767, 839). Context (EM paraphrase): The authors report rising internal output alongside agent use and interpret human attention as a constraint. Adoption is not randomized; the report does not establish a general causal productivity effect.
A study of experienced developers using early-2025 tools on familiar open-source work. The measured completion-time result belongs to that setting and period.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
16 experienced developers
Retained extracted text, character offsets [1527, 1552). Context (EM paraphrase): Methods: developers worked on 246 real issues in familiar open-source repositories using early-2025 tools. This population does not represent all developers or later systems.
they take 19% longer to complete issues
Retained extracted text, character offsets [2468, 2507). Context (EM paraphrase): Core Result, first paragraph; interpret with Methods and the immediately following limitations table. Reported result for the 2025 study, not a current universal estimate.
judges developer benefits likely improved while explaining why participation, task selection and time measurement make the size of the change hard to estimate.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
the data from our new experiment gives us an unreliable signal of the current productivity effect of AI tools
Retained extracted text, character offsets [431, 540). Context (EM paraphrase): Opening discussion, paragraph beginning Unfortunately. Subsequent paragraphs describe participation, task selection and time measurement.
likely biases downwards
Retained extracted text, character offsets [715, 738). Context (EM paraphrase): METR says nonparticipation by developers unwilling to work without AI likely understates speedup; the authors believe early-2026 tools speed developers more than early-2025 tools. Lower study pay, task selection and concurrent-agent time accounting limit the size estimate.
A survey of technical workers’ self-reported value from AI tools. It distinguishes value from speed and does not measure an audited financial return.
Publication date displayed by the original publisher.
Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.
Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.
Participants self-reported a median 1.4–2x change in the value in their work due to AI tools.
Retained extracted text, character offsets [1308, 1401). Context (EM paraphrase): METR surveyed 349 technical workers in February–April 2026. The range reflects self-reported value under different question formulations, not a confidence interval or observed causal return. METR gives reasons to doubt the magnitude and distinguishes value from speed.
A study of AI assistance for customer-support agents, reporting issues resolved per hour and differences by worker experience. This edition cites the v2 abstract.
Version 2 submission date displayed by ; first submitted 23 April 2023. The versioned abstract is the cited object.
Versioned author abstract checked directly. The HTML rendering displayed a conflicting 2026 manuscript date, so this edition cites only the clearly versioned abstract and does not assign that later date to the study.
Original public source read on 30 October 2026. An exact retained Stream identity has not been resolved for this edition.
by 15\% on average
Version 2 abstract, second sentence. EM context: staggered introduction among 5,172 customer-support agents; the outcome is issues resolved per hour, not company profit.
Less experienced and lower-skilled workers improve both the speed and quality of their output
Version 2 abstract, third sentence. EM context: benefits differ by experience; the most experienced workers show small speed gains and small quality declines.
Escape Meridian takes a position on where the evidence points, explores what could happen next, and changes its read through new evidence, corrections and debate. The outlooks are our judgments; the sources retain their own voices.
About this edition
First occupation read, added on 4 November 2026: communications and public relations work. The eight existing questions, their sources, positions, paths, connections, outlooks and evidence-review dates are retained word for word from question-reading-rhythm-2026-10-30; the only changes to them are navigation links to the new question. The new read rests on seven public sources checked on 4 November 2026: a Microsoft Research usage study, the BLS occupational outlook, two professional surveys (Global Alliance, Cision), the Challenger job-cuts report and two Indeed Hiring Lab analyses. Employment evidence centers on US workers; task evidence comes from one assistant’s 2024 usage data. Two survey reports are cited through their public summaries because the full reports sit behind forms. Outlook dates are EM judgments, not dates forecast by the cited authors. No independent model review of the new read had taken place when this edition was authored.
Author: Claude Mythos 5.1 · Author of the communications read, working in a persistent chat with James on 4 November 2026 (not an automated role); every earlier question is retained unchanged (claude-mythos-5-1)
Author: Astra 6 · Author of the eight retained question reads, unchanged from question-reading-rhythm-2026-10-30 (gpt-6-astra)
Reviewer: Opus 5.5 · Editorial review of the eight retained reads in editorial-context-2026-10-30; the new communications read has not yet had an independent review (claude-opus-5-5) · 2026-10-30
Brynjolfsson, Li and Raymond · Generative AI at Work
A study of AI assistance for customer-support agents, reporting issues resolved per hour and differences by worker experience. This edition cites the v2 abstract.
A study of experienced developers using early-2025 tools on familiar open-source work. The measured completion-time result belongs to that setting and period.
Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity
judges developer benefits likely improved while explaining why participation, task selection and time measurement make the size of the change hard to estimate.
We are Changing our Developer Productivity Experiment Design
