A dependable colleague gives you room to do more because you can trust a handoff. With AI, the interesting question is how much responsibility you can share before explaining, checking and rescuing the work becomes another job. That can affect your concentration and confidence as well as your output. The destination is useful independence: knowing which work the system can finish, when it needs help and where your own judgment makes the difference.
EM read · 2026-11-04 · Evidence reviewed 2026-11-04
During 2027, we expect useful AI colleagues to become ordinary in digital workflows where people can assign a recurring task and recognize when it is finished well.
In the customer-support study, agents using AI resolved more customer issues per hour. METR’s February 2026 update judges that developers likely benefited more than in METR’s early-2025 developer experiment, where AI access slowed experienced developers; it cannot reliably estimate the size of the improvement. These findings support our expectation that assistance will free people to take on more work.
Anthropic’s workforce report points to the next constraint within its own organization: as agents produce more, people still have to decide what deserves attention and which results are ready to use. Defining the AI’s responsibility helps keep that supervision from becoming another full-time job.
What this means
Aim for a colleague that gives you room to attempt work you could not previously take on. Give it a recurring responsibility, a clear finish line and a way to ask for help; learn where your judgment makes the result better.
Why we take this view
The predicted shift is routine use in suitable digital workflows during 2027, building on demonstrated assisted work and 2026 internal agent use; it does not require autonomous performance across every responsibility in a job.
What has to hold
The workflow has accessible context, observable outcomes and affordable correction.
Organizations invest in the handoff and review process rather than only distributing tool access.
The strongest rival
Review queues grow faster than useful output, so apparent delegation becomes another management burden.
Reliable completion advances fast enough that routine supervision shrinks substantially, making the agent closer to a service than a colleague.
What would change our mind
Repeated deployments finish more work to the required standard per hour of human checking, without an increase in missed consequential errors.
The same workflow remains dependent on extensive prompting or repeated rescue after onboarding.
Examine what happens when a human stops checking each step.
Where this could lead
AI takes on recurring work; people manage the exceptions
Base case ·
A small team handles more work by giving agents clear responsibilities. Human effort moves toward judgment, handoffs and the cases that resist automation.
What would make it happen
We expect this working arrangement to spread in suitable digital workflows during 2027 because it builds on assisted work and internal agent use already reported.
Conditions
The agent receives enough context to finish a repeatable task.
An owner can inspect the result and handle exceptions without reviewing every action.
Watch for
People spend less time checking each piece of work that meets the required standard after onboarding.
The same agent responsibility needs fewer interventions over repeated use.
The team acquires a second job: managing its agents
Alternative ·
Agents make more output than people can use. The queue of explanations, checks and repairs grows, and the promised extra capacity becomes a coordination problem.
What would make it happen
This can emerge within a rollout and persist through the next operating year if supervision grows with output rather than with useful completed work.
Conditions
Each additional agent creates substantial demands on a scarce reviewer.
Tasks remain ambiguous or require frequent contextual rescue.
Watch for
Review queues and reopened work grow while the amount finished to the required standard stays flat.
People spend more time routing and explaining agent work than the deployment saves.
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
Second occupation read, added on 4 November 2026: product management work. The nine existing questions, including the communications read sealed earlier the same day, are retained word for word; 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: two Lenny’s Newsletter surveys of tech workers, ProductPlan’s State of Product Management 2026 (the report PDF, linked without a form), two SVPG essays by Marty Cagan, the BLS outlook for computer and information systems managers, and Indeed Hiring Lab’s October 2026 snapshot; the Microsoft Research usage study cited in the communications read supplies its limits. BLS does not project product managers as an occupation of their own, so employment evidence is indirect, and the survey evidence comes from self-selected newsletter readers and a vendor’s respondents. 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 and product management reads, 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 communications and product management reads have 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.
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
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
