A blog is the single most inefficient way of achieving ANY of your online writing goals:
- Building an audience
- Finding your voice
- Proving which topics resonate best with target readers
It's wild how many people disagree with me on this.
When SHOULD you start a blog? 👇
- Building an audience
- Finding your voice
- Proving which topics resonate best with target readers
It's wild how many people disagree with me on this.
When SHOULD you start a blog? 👇
https://twitter.com/jerinenicole/status/1384557524783878147
Scenario #1: You've validated your high-performing topics and are ready to give readers MORE of "what's working."
The VAST MAJORITY of people who start writing online *think* they know what readers want to hear from them.
They're usually wrong.
Write. Publish. Gather data.
The VAST MAJORITY of people who start writing online *think* they know what readers want to hear from them.
They're usually wrong.
Write. Publish. Gather data.
In this process, 1 of 2 things will happen:
- You'll either confirm your assumptions were correct (with data)
- Or you'll learn your assumptions were incorrect (with data) and discover new, higher-performing topics as a result.
In either case, you now KNOW.
- You'll either confirm your assumptions were correct (with data)
- Or you'll learn your assumptions were incorrect (with data) and discover new, higher-performing topics as a result.
In either case, you now KNOW.
Once you KNOW what is resonating, THEN it makes sense to double-down, build out a website (if you really care that much), and move readers over to your own domain.
But if you START there, you are building entirely on assumption.
And you usually end up building the wrong thing.
But if you START there, you are building entirely on assumption.
And you usually end up building the wrong thing.
Scenario #2: You want to build a business.
This is what people don't understand: a blog is a business.
This idea that you need to "have a centralized place for all your writing" is insanely outdated.
People don't read linearly online anymore.
We read spontaneously.
This is what people don't understand: a blog is a business.
This idea that you need to "have a centralized place for all your writing" is insanely outdated.
People don't read linearly online anymore.
We read spontaneously.
This spontaneous reading journey is what allows online writers to LEARN, faster.
Once you've learned what works and what doesn't, and you want to turn proven topics into products, services, etc., THEN it makes sense to have your own site.
Once you've learned what works and what doesn't, and you want to turn proven topics into products, services, etc., THEN it makes sense to have your own site.
But again, before you take the time to build a product or launch a service, don't you want to make sure you know that's what your readers want?
Wouldn't it be better to CONFIRM those assumptions out in the open?
The truth is, you can go years online without a blog or website.
Wouldn't it be better to CONFIRM those assumptions out in the open?
The truth is, you can go years online without a blog or website.
People think this is "the longer road."
It's actually the shortcut in disguise.
1. Practice In Public
2. Validate your high-performing topics w/ data
3. Clarify your language and create your niche
4. Build your library of content
5. THEN think about moving to your own site.
It's actually the shortcut in disguise.
1. Practice In Public
2. Validate your high-performing topics w/ data
3. Clarify your language and create your niche
4. Build your library of content
5. THEN think about moving to your own site.
Everyone wants to skip to Step 5.
As a result, they spend hours and hours launching a website and blog, go through their big "I just launched!" announcement speech on social media, and then fizzle out 30 days later.
It's a recipe for failure.
As a result, they spend hours and hours launching a website and blog, go through their big "I just launched!" announcement speech on social media, and then fizzle out 30 days later.
It's a recipe for failure.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
