A few weeks ago, @eriktorenberg told me that I could be great on Twitter "if I just took myself more seriously."
Since he basically dared me, I'm kicking off a 30 day Twitter challenge with some of my @beondeck crew.
(I named it that before I realized March had 31 days...)
Today, three pieces of writing advice that I don't usually see in other places.
Read on 👇
1. Work on multiple things at once
I try to always have at least three totally different pieces in progress at any given time. That way, if I'm feeling stuck on one, I can just jump to another one.
You're exponentially less likely to feel blocked on multiple separate things.
2. Lie as needed
If you're writing about your life, hewing too slavishly to the "truth" limits you unnecessarily.
Don't go full James Frey, but exaggerate here and there if it helps the piece overall.
Science shows your memories aren't even that accurate anyway.
3. Wait until the last minute
Your mileage may vary, but I work best under pressure.
If I have a whole week to write something, it's all too easy for perfectionism to take over and slow my progress to a crawl.
If I have two hours, you can be sure I'm going to get it done.
That's the main reason I started my newsletter—to face the risk of public shame if I didn't produce something every week.
It's also why each issue ends up coming out late Sunday night.
One of the most common things I see new writers struggling with is coming up with things to write about. I'm reminded of how impossible coming up with startup ideas seemed to me before I became a founder.
I think people in both cases suffer from the same flawed mindset.
The mistake is seeing any individual idea as the goal.
The goal isn't to come up with an idea—it's to become the kind of person for whom coming up with ideas is second nature.
Before I'd ever started a company, I had no idea how people came up with startup ideas. It took me FOREVER to find one worth working on. And it wasn't even mine—my cofounder came up with it.
Most aspiring startup founders who think they should learn to code would be better off learning to write well instead.
Here's why 👇
1. For most founders, learning to code is about being able to quickly iterate and test an MVP.
But you can often test an idea even faster just by writing about it and observing the feedback. Sometimes, the writing process itself even reveals where your assumptions are wrong.
I've had the experience of realizing an idea was bad halfway through fleshing it out in writing.
I've also had the experience of realizing an idea was bad after working on it for four years, raising $3mm, and hiring 20 people.