Last week, I sent this email to 7,118 people:
Scary, but necessary. For a while now, I've been feeling my weekly emails aren't as good as they should be. Open rates are dropping, subscribers are churning almost as fast as they're coming in…
Not a good place to be. ?
I mean, just look at this. 36% open rate on the random question, 22% on the weekly email two days later. Not good at all.
Yes, that does list only 5,197 subscribers. It's because my email list is split between two Drip accounts. The big list is for people who subscribe by buying a product or signing up for a technical course or getting a free book chapter or something like that. A smaller, 2,000-person list is for those who subscribe directly through this blog.
You could say one list leans towards customers and the other leans towards fans. Open and click-through rates are similar for both lists.
The lists are split because I thought they were two different types of audiences back when I set it up. They're not.
77 people hated the question and unsubscribed. That hurt, but it's only 1%. I guess I'll live.
32 people loved it and shared it on Twitter from the "Thank you for being awesome" page.
15 people replied.
3 people complained on Twitter that I only gave them one voting option. This was on purpose to force a decision :)
500 people clicked a link and voted. That's amazing. Thank you. ❤️
Here's the breakdown:
It's okay. I've heard rumors that the reason people like my code writings is because I make them personal and approachable. ?
So how am I going to use this info to make my weekly emails better?
I'm going to make the emails a lot more personal. I know people said they don't care, but I think that secretly they do. Every week, there's going to be a short cover letter that’s exclusive to the mailing list. This, I think, will improve our relationship.
And while all three groups are going to get the same content, it's going to be personalized. For the technical group, the lead story will be technical; for business, the lead will be business; and so on. This, I think, will improve open rates.
I'm also going to use this to improve people's onboarding experience. After you subscribe, you'll get to choose a topic.
The overall goal is to help people become better engineers. We'll see if it works :)
Continue reading about Why People Read my Weekly Emails
Semantically similar articles hand-picked by GPT-4
- Initial Results of my Patreon Experiment
- I Got Schooled
- Why I don't write more Nightowls type stuff
- So how many readers _actually_ read a blog post?
- Best blogging week I have ever had
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️