Ask HN: How do you decide on what to build/avoid decision paralysis?

I&#x27;ve actually suffered form something similar for many years. I was recently talking to a mentor of mine complaining about this and he asked me &quot;What is it that gives you paralysis and causes you to abandon projects?&quot;<p>It really made me think about it. For me it was spending hours thinking &quot;what if someone looks at my code and I&#x27;m not using the absolute best-fit design pattern because I didn&#x27;t know about it. What if I used the wrong package or project structure...&quot;<p>After I told him this, he said to me &quot;You build things for people to use... only other developers are going to sweat the details. At the end of the day, let&#x27;s say you do come up with a project that gets wings... who is going to be cutting the check? People who use the product and only care if it fits THEIR needs or a room full of developers who have nothing to show for anything other than a lot of flame posts?&quot;<p>At the same time as this conversation was occurring, I was reading Seneca&#x27;s &quot;On the Shortness of Life.&quot; Pretty much a whole dialogue about getting off your a@# and just doing something.<p>Finally, take what you learned doing partial project A and see if you can apply those lessons to partial project B... it just may be that a few projects can be refactored from lessons and insights gained from other projects.

At least with me, externalizing the ideas, having literally any process helps focus so much.<p>Whenever I get a cool idea, big or small, I write it on a post-it and put it on a wall, then I can have faith that it is still there after I&#x27;ve finished what I&#x27;m doing. This is on a feature level, but some of them are ambitious multi-week things.<p>I think at least for me, the more I work the more ideas I have, and the more difficult it becomes to focus on finishing something that isn&#x27;t very fun. If I can trust they still exist later, that isn&#x27;t so much of an obstacle, but an asset, and I can finish drawing the owl in peace.<p>Having a battery of ideas ready to go also means sometimes I can often be extremely productive, and finish like 5-6 features in a few hours. Usually when I get stuck and end up procrastinating, it&#x27;s because I don&#x27;t know what to do next. The wall-of-ideas solves that.<p>It&#x27;s like zero planning scrum. YMMV, but I&#x27;ve found it incredibly effective.

&gt; How do you manage?<p>You&#x27;re asking bcs you think the way it is is bad, no?<p>You&#x27;ve spent 3 years trying to find out what the best thing to do could be. If you had found it &amp; done it, that would&#x27;ve been the best outcome. But you didn&#x27;t, and did almost nothing. Even doing anything would&#x27;ve been better than that! So, do that: do anything.<p>In my view, finishing something is almost always better than finding the best project to finish. So pick something, anything, and do it. If you can&#x27;t decide which, then which you choose doesn&#x27;t matter. And whenever you feel the urge to think again: but what if I did this? Look back 3 years, and notice that this doesn&#x27;t work out. If you really want to switch, use that want to finish the current project faster. You can reduce scope, but always finish.

It comes down to persistence and originality. If the given idea is original and the value is worthy I will follow it at great expense.<p>For example I maintain a peer to peer application that used to use HTTP for all its traffic. I found an alternate transmission scheme that dramatically increased both performance and simplicity but it took me about a year to implement from scratch across all aspects of the application. This was a great effort and at first appeared incredibly fragile and broken, but once I really nailed down the concept it became far more durable that other more common transmission techniques.<p>I have been working on this application for just over three years and have almost no users. I keep going because now the application can do amazing things that everyone else cannot.

The last time I was paralylized for 3 weeks and decided on one of the ideas I had. I think to this date that this has been the best decision according to the knowledge that I had at the time. Nevertheless, after 1 year of working on it, I had to take a pause due to life circumstances, literally a 1 year pause (which is still in progress). During that time, I could not help but think about other ideas. I&#x27;m not 100% sure what I will end up doing, but it kinda looks like I&#x27;m taking the first product, rebuilding it into a completely different (and much simpler) product that will put me on the path to launch the product (much more complex) I decided to skip on earlier.<p>I don&#x27;t know, it&#x27;s like. You have to keep building, keep the momentum up and do some periodic direction checks, but don&#x27;t let it get out of hand with your time. I would be building my first product to this day if I was not forced to take a pause. But since I took that pause, my knowledge got updated and all things considered I think I will be building the idea I decided to skip earlier.<p>All product ideas that I have are complex, and even the simplest one requires some 5,000h total to launch. I learned that if even something that I considered simple takes time, maybe I overshat the complexity of the more complex product and if it&#x27;s so much time and life sacrifice, I will pick the idea I&#x27;m more interested on and don&#x27;t mind it taking more time. If it fails, at least I know that I did not kept anything back. If the simpler idea failed, I would be full of regret that, it failed anyway, I should have pushed for the thing I was more interested about.<p>I hope that once I invest in a product enough time, there will be no going back and no reason to question direction anymore. I spent 1,500h on this one, and it&#x27;s still such a long way to go that scratching it can be justified, especially since I&#x27;m re-using some of that code. But once I settle on that more complex idea, push some 3,000h, I will know that there&#x27;s no going back and I need to go all the way to 10,000h or whatever it will take to build it.<p>That said, I think it&#x27;s valuable to question too much. So much in this game depends on what you build. No matter how shiny the product is, if it&#x27;s useless.

There’s the “pivot or persevere” concept from the “Lean Startup” book. Basically, if you’re stalled out, you step back, ask why, craft alternatives, compare their relative qualities, and decide which you’ll go pursue in the next time window. So basically just every now and then have a self convo of “how’s this actually going”, and set a deadline for when you’ll decide to persevere or pivot.<p>It’s worked for me loads of times, the important thing is that it both encourages and validates project momentum, which is probably the most important thing of all.

I juggle things too, I think we all do.<p>I&#x27;ve found nothing motivates me to finish something like the prospect of being able to use it myself. If it will make my life better I&#x27;ll work on it til it&#x27;s done. Now, I don&#x27;t build SaaS stuff, so this makes sense.<p>Just pick something that you&#x27;d use, that would make your life better, and build it for yourself, and then see if other people could benefit from it as well.

I set a time limit to ship whatever I can, like a week for example. Magically the work compresses to fill the allotted time, Parkinson&#x27;s Law. It&#x27;s a good way to finish and ship rather than get mired by decision paralysis, which I had, just like you.

A recurring idea that doesn’t give you rest combined with enthusiasm.<p>These are the driving forces that will take you through the ups and downs, not some kind of magical willpower or merit.

Chances are you don’t actually want to build things.