How do you combat analysis paralysis?
How do you decide when you have enough information to move beyond analysis? What are the signs that cause you to pack it in and move on to another idea?
My goal to build something that makes money at this point (even if it's a trivial amount). I have several hobby projects where I've let myself off the hook and just built for fun but I'm ready to move beyond that.
I've become more disciplined in my pre-build idea validation but that's led to me being overly pessimistic and easily discouraged (I think?). Seeing an existing good execution of an idea really takes the wind out of my sails even though I know academically this can be a good sign. I've become obsessed with finding the right problem space which has led to months of endless analysis.
I used to do this a lot: Over analyse, over plan, never ship.
What I have now learned to do is to give myself a hard limit (usually 1 month) to ship something. Within that timeframe I'd rather remove features than push the launch time.
Reasons for this are:
As for seeing an existing good execution, no doubt that is somewhat disappointing, but I tell myself it's inevitable. I cannot be the only person that thinks there's a problem to be solved or that an opportunity exists. I think we just have to push through it and remember that there's enough space for several great products.
Thanks @stephenafamo. I appreciate the thoughts. Based on what you're saying it does feel like I've overcorrected (or found another excuse to not buckle down, haha). I've been stuck deciding when to start building (after several years of just building random stuff with no validation that never amounted to anything).
Just ship is in contention with make sure you're in a good market etc.. I probably haven't actually shipped enough stuff to have earned the right to look for the Goldilocks idea though.
Lately it's not so much that I over plan any one idea it's just that i go from idea to idea convincing myself none are any good.
I guess that's another thing. Always feels like there's so many different things to work on.
I'd say you should try to pick one, don't worry too much about "good market", and just commit to building it in a specific timeframe.
All the market validation you need will be gotten once you ship.
I try to tell myself that by finishing one idea quickly, I can move on to the next with peace of mind 😂
Just Do It. -Nike.
In my estimation, you'll never move beyond analysis. That isn't to say that you shouldn't sh*t or get off the pot, but competition should never be the reason why this happens. Competition proves that there is a market. It is a good thing in that regard. First to market is for sweeping up the early adopters, but first to market is rarely successful in the long-term. For example, almost every time Apple failed spectacularly is when they tried to be first to market. The burden of responsibility comes with being 3d, 4th, 10th to market, because now innovation is the name of the game. Most ideas are not all that innovative, or their execution isn't. It sounds like you've got the right headspace with pre-build validation.
The only way to really try and predict the future is to invent it yourself.
What are you passionate about? What would you build if money were taken completely out of the equation? Figure this out and execute it. I know, I know, it's much easier said than done, but it will spare you a lot of wasted time and needless pain.
Thanks @c0nsilience Good questions. I will think on them.
I've moved away from the stuff I'm objectively passionate about because I feel that I would be pretty passionate about a lot of product if it was actually delivering value to my customers but I have to get over that hump. That said, there are a lot of things I wouldn't consider because I know i wouldn't like the customers and/or the market so I need to find the right balance.