Thread by @gill_works

The case for working on many projects at once.

A strategy for supercharging the creative process and hacking productivity as an indie creator...

It’s not for everyone, but if you can’t sit still like me it helps prevent creative anxiety...

A THREAD 👇🏾

[1/13]

There are several advantages I've found to working on many projects or building several products at once.

REASON #1
You can diversify your work so you can be always creating, never blocked.

If you're blocked waiting on something not in your control, switch projects.

[2/13]

If you're experiencing a creative block, or get stuck at a point where you need inspiration, switch projects.

You can't force inspiration, it has to come in its own time, but that time doesn't have to be lost.

[3/13]

When you run into a skill gap, and need time to learn something new, switch projects.

You have to be in the right headspace to learn, so move on to something where you can stay productive, and come back later when you're ready to take the plunge and learn something new.

[4/13]

When you hit a point where you'll have to switch from a left-brain task to a right-brain task, switch projects.

A lot of momentum is lost when jumping from a task like writing copy to a task like designing a landing page.

Stick with one discipline as long as you can.

[5/13]

REASON #2
You can prioritize the order you work in so that each project leverages the previous one.

To achieve this, order your days so that you can learn a skill on one project that you know you will end up needing and using on the next project.

[6/13]

Also, order your work so that when you create something, it can be re-used again with minor tweaks.

This could be its own thread, but a portion of any completed project can easily become the majority of another project.

As @jackbutcher says: "build once, sell twice."

[7/13]

You can also compound learning and reduce the amount of time spent by re-using the same tools.

Once you find a stack that you're happy with, use it for as many projects as you can.

[8/13]

REASON #3
It reduces the mental/emotional weight of any one project.

When you have several projects going on at once, you can pull the plug on one and not feel like you're back at ground zero.

If any single project isn’t going as planned it doesn’t feel like a failure.

[9/13]

REASON #4
It allows you to collect more data for analyzing success.

You can compare & contrast results instead of comparing against what your expectations or hopes were for a project.

This takes some of the emotion out of it and gives a more impartial assessment.

[10/13]

You can also compare launch and marketing strategies with more data points.

Did one project do well because it caught steam on social media or a Product Hunt launch?

Or did you launch them the same way and one just missed the mark?

[11/13]

I use these practices in my work and it's important to note that this approach is not the same thing as "dabbling."

Each project is expected to become a full product. Not all of them will, but that is the expectation.

As @dvassallo says, it's "a series of small bets."

[12/13]

Are there downsides to this approach? I'm sure there are, but I wouldn't pay them much attention.

I firmly believe that if you throw your full energy behind leveraging the upsides to your advantage, the downsides don't stand a chance. 💪🏾

[13/13 END]