Ideas and Validation January 14, 2020

Dropping an idea to work on another

Coderforlife22

So i've currently been working on a project for a while and I want plan to finish it but put it on the back burner for a while.

I plan to use this time to build out another saas that I really believe in and I could build it relatively fast compared to what i'm currently working on.

Has anyone ever put a project on hold to work on something else for a few months?

I am only asking because I know it's not really a good habit to not finish what you start.

Let me know your thoughts!

  1. 6

    I think it's absolutely fine to a put a project on hold if you feel the other idea is something you're more passionate about and will be more likely to win.

    My advice though is that you write down in a document the reasons you want to put the project on hold and pursue the other one. You should be asking yourself why the other project is higher priority? Have you taken in consideration the cost of putting it on hold? (i.e. You will lose momentum and it will take you longer to get the project restarted if you do pick it up again.).

    If you make a clear case for the new idea, go for it. If it turns out not to be the right direction later on, you'll be able to review what you've written down previously to see where you can improve for next time. In other words, you'll be less likely to make it a bad habit.

    1. 1

      Great suggestion! Thanks for the wisdom drop here.

  2. 2

    I did, and it has been working out for me better so far.

    The trick is to only drop your current idea when you've hit a roadblock you know you can't surmount. Lack of market is one of those roadblocks, for example. In my case, it was simply a lack of ability to sell, convince, and close customers in a vertical that I had zero familiarity with.

    I wrote about my experiences here, you might find a pointer or two: https://www.indiehackers.com/product/zlappo/first-paying-customer-booyah--Lw2qly2I2AFSjcnz_zQ.

  3. 2

    I always do this! I always joke that it's because I get bored really easily, and while that's partially true, switching projects helps me re-energize and creatively get around roadblocks. Like for thegoodstartup.com, I took a month off to work on other e-comm products and see how I could make more money, but then in the back of my mind, I was still thinking about business models for The Good Startup. That's what really motivated me into working on it again!

    Sometimes I feel bad about giving up on myself or my own projects, but the truth is, we all can only do so much in the given amount of time we have. Focus on the project that you can do the most with in the moment, then move on to a different one when the opportunity awaits. You can always come back to your original projects, which is something I'm always eager to do :)

    1. 2

      Wow. This is golden advice! Thank you so much! #Saved

  4. 2

    If you are relatively close to finishing the first project I would knuckle down and ship it first. You'll feel better for it and learn a few things before taking on the next

  5. 2

    Very good topic and it's a mixed bag:

    • If you finish something, you learn a lot, you go through the entire dev life cycle and most important: you prove to yourself that you are able to end something

    • if you start new projects on and on and don't finish you also learn a lot, sometimes even more; it can be also a good habit; if you you start and trash projects, you condition yourself to start faster and automate project starts through boilerplates + you don't loose time working on the wrong idea

    so, there is no right or wrong. important is that you work on something and not waste time on thinking and conceptualization and other shit; go quickly to market to get into feedback loops; then once you hit gold you know it and you are motivated to keep on

    1. 2

      Dude. This is GOLD. So much good advice on this thread. I hope it helps a bunch of other hackers like its helping me. Thanks so much for the time to reply!

  6. 2

    I think it depends on your personality if you have 50 ideas per year (like me), it could be better to release/finish something first. Otherwise, you may find your self in the vicious loop, where you constantly move to another "better" idea.

    1. 1

      Yeah and this is my fear. I think this will be a test and if I notice myself wanting to move on to a "better" idea again then i'll know this could be a vicious loop of constantly moving to "better" idea.

  7. 1

    I just did this yesterday, so you're not alone.

    Others have provided a lot of good feedback, so I won't reiterate most of what's already been said. But the reason why I'm putting my original project on hold to pursue this new idea that came about yesterday is because I'm utilizing a no-code approach for the new idea instead of developing it on my own (which is the approach for the original idea). Given that I would get this new idea shipped a whole lot faster and potentially start generating revenue on the side, I figured it'd be okay to put the original idea on hold for a few weeks.

    Perhaps you can try to utilize some no-code solutions to replace some of the development work that you plan to do so that you can get your new idea shipped faster? That way your original idea isn't put on hold too long (which you may not even bother getting back to if your new idea is very successful).

    1. 2

      Yep. This is basically my same thought process! Good to know your thoughts as well! really good points you raised as well. All the best with your new project!

      1. 1

        Likewise, best of luck to you!

  8. 1

    Yes it's okay and a good idea to drop something and move on...if you know you need the break and plan to circle back, the time away can be healthy. I've done that several times and have had breakthroughs while not even focusing on the project I put on hold.

    Good luck during your break.

    1. 1

      Thanks! Well, it won't be a break because i'll be working on a different product. Lol

  9. 1

    It's hard to tell the difference between a good decision of such type and one that would represent a loop.

    You should make some commitment about stages and/or time

    Don't just build a product

    Did you validate the idea? Do people care about it?
    Did you try to sell the idea with a landing page that just let's people signup for updates?

    If these are not your focus you might end up in the building limbo loop

    1. 1

      Good point! How dos the process work for trying to sell the idea with a landing page without having something for people to try out?

Recommended Posts