AI CASE
An AI newsletter I shut down
At an organisation where I introduced AI, I built an automated newsletter about AI for my colleagues. Because almost nobody read it, I added a feedback module, and when that went unused too I stopped the newsletter.
Published on
- PERIOD
- 2025 - 2026
- USED
- Clauden8n
The problem
AI changes faster than you can follow alongside your own work, and I wanted my colleagues to know what was going on without having to look for it themselves. A newsletter seemed the shortest route.
The approach
I built a newsletter about AI developments that was compiled automatically and landed in my colleagues' inboxes.
The result
The newsletter was barely read, and the criticism that came back was that the content was not relevant enough. Because I wanted to know what did land, I added a feedback module that would show me week by week what was and was not relevant. Nobody used that module, and after that I stopped the newsletter.
What went wrong
You do not solve an adoption problem with a mechanism. Because the newsletter went unread, I built more automation around it, and that ran aground on exactly the same cause. I had built first and only asked afterwards whether it was relevant. With what I know now, I would have involved everyone from the start in what I was working on, and first defined where the time was going instead of taking on everything at once.