The Newsletter Was Never the Point. The Curation Was.

Everyone is talking about AI taking jobs. Most of the conversation stops at the obvious cases: call centre staff, copywriters, junior analysts. Few people are looking carefully at the quieter casualties. The newsletter editor is one of them, and the way that role disappears tells us something important about how AI displacement actually works.

Bolt-on AI versus AI that removes the function

Walk into most organisations today and you will find the same pattern. Someone takes the existing newsletter process: collect news, summarise it, format it, send it out, and bolts AI onto each step. The collection gets automated. The summarising gets handed to a language model. The formatting becomes a template with a button. The job still exists. It has simply been made faster.

This is the wrong question. The right question is not “how do we automate the newsletter production process.” It is “why does a centrally produced newsletter need to exist at all, now that anyone can generate one for themselves.”

Why the centralised newsletter existed in the first place

A curated newsletter solved a real problem. Reading everything yourself took too long. Someone with judgement and time would read widely, decide what mattered, and hand you a digest. That was genuinely valuable labour. It required taste, domain knowledge, and the discipline to do it every week.

AI has not made that labour faster. It has made that labour unnecessary for most people, most of the time. Anyone can now ask an AI to read everything relevant to their interests, at the depth they want, on the schedule they want, and hand back exactly what they personally need. The editor’s judgement is no longer the bottleneck. The reader’s own instructions are.

What gets displaced is not the editor’s typing. It is the editor’s centrality.

This is the distinction that matters. A bolt-on view of AI assumes the editor keeps doing their job, just quicker. An elimination view recognises that the editor’s core value, deciding what is important on someone else’s behalf, has been disintermediated. The reader can now do that deciding themselves, instantly, for free or near enough.

This is not a small efficiency gain. It is a structural shift. The job was never “write a newsletter.” The job was “be the trusted filter between an overwhelming amount of information and a person’s limited attention.” AI has made the filter personal, instant, and infinitely configurable. Once that happens, the centrally produced version stops being the best option. It becomes the default option, kept out of habit rather than necessity.

The pattern repeats well beyond newsletters

This is worth dwelling on because the same structure recurs across many roles people assume are AI-resistant.

• The research assistant whose job was to summarise documents for an executive. The executive can now ask the AI directly, at whatever length and angle they want.
• The internal communications team producing a weekly all-hands digest. Staff can ask an AI to generate their own version, filtered to their team, their projects, their tolerance for detail.
• The market intelligence analyst circulating a sector briefing. Anyone in the business can generate a sharper, more personalised briefing on demand.

In each case, the temptation is to defend the role by making it faster with AI. The harder and more honest exercise is to ask whether the role’s reason for existing was ever about production speed, or whether it was about being the only available filter. If it was the latter, speeding up production does not save the job. It only delays the recognition that the job’s premise has gone.

What this means for leaders

If you run a function built on this kind of centralised curation, do not ask your team to bolt AI onto the existing workflow and call it transformation. Ask a harder question: if every consumer of this output could generate their own version, tailored exactly to their needs, would they still want ours?

Sometimes the answer is yes. Genuine institutional voice, accountability for accuracy, or a curatorial perspective that adds judgement beyond aggregation can still justify a centrally produced product. But that justification needs to be argued for explicitly, not assumed by default because “we have always sent a newsletter.”

Sometimes the answer is no. In that case, the honest move is to redeploy the people involved towards work that still requires a human filter: relationship building, original analysis, decisions that carry accountability. Pretending the newsletter still needs a dedicated production team, just an AI-assisted one, is the kind of accountability avoidance that delays the inevitable and wastes good people’s time in the meantime.

The uncomfortable bit

The uncomfortable truth in all of this is that AI displacement rarely looks like a single dramatic layoff. It looks like a function quietly becoming optional, then quietly becoming irrelevant, while everyone in it keeps busy making the old process faster. By the time anyone asks whether the function should exist, it has often already stopped mattering to the people it was meant to serve.

The newsletter was never the deliverable. The judgement behind it was. Once that judgement is available to everyone individually, the newsletter is just paper. It is worth asking what else in your organisation is, structurally, exactly the same.