On Being a Good Newsletterer (2020)
craigmod.com
craigmod.com
I cannot relate. If I subscribe to a newsletter I know that for months to years whenever a mail pops up in my inbox.
I also cannot relate to:
> Have killer voice.
In regards to tone, my preference is authenticity. If someone has genuine “killer voice”, fair enough, if someone doesn’t, great as well. Overall, the quality of content is far more important to me than the style of presentation. (Which doesn’t mean it wouldn’t matter, it’s just not my top priority.)
Plus, with so many newsletters out there on the same topic, I usually need to subscribe to a few before deciding which ones to cut.
A far cry from the old days when the only way to discover a newsletter would be on HN's periodical "favourite newsletter" threads.
I've seen this intro in the newsletters I subscribe to, but didn't think of adding to the one I send out. Used to just say what's the issue number. To be fair, the links to the newsletter and unsubscribe were automatically added at the end of the email, will now add these details at the top as well.
Regarding the third point of images-as-text, I use it for one section (programming tip, with syntax highlighting) but also provide link to the text version with explanations.
He has a point, but much in the same way as "don't slow down your website with a bunch of unnecessary JS" also has a point.
It's just people don't seem to care enough for this to make a difference. Every Substack newsletter I'm subscribed to embeds tweets into the email or web page, which is worse than just a static image being served from cdn.email.substack.com or whatever.
Besides these, a welcome sequence where I send some of the most liked editions worked great for my newsletter.
It allows a new subscriber to get familiar with the content and unsubscribe early on if it's not for them. I saw a 10-15% increase in open rates thanks to this.
Obviously, this is for newsletters with timeless content rather than news.