4
5 Comments

How do you plan your product / big updates before building it?

I have an idea for a nice product - but now I have to build it. In the past, I've always just started building it, planning the code architecture and the whole project setup on the fly. This time I want to do things differently, because of the workload of the project.

I'm curious how you guys plan your products or big updates before you actually build them? Do you guys have any specific strategies? I would love to learn from you!

on July 12, 2021
  1. 1

    I'm a big fan of waiting to build until as late as possible. Have you already shared your idea with others and gauged whether people will actually care? There's tons of places to pitch pitch your idea on the internet and get unbiased feedback

    1. 2

      I haven't pitched it to the masses yet, because somehow I still have a bit of the old-school mindset that the idea might get stolen from me before I have time to build it. However, I plan to do so (even though I'm pretty sure people care and it's just about good execution)

      1. 1

        That is understandable but from what I have heard from most people is that it's very rare that your idea does get stolen.

        I think you can try putting up a landing page showing that the product solves this and this problem without actually revealing how it does so

        1. 1

          That's a good idea! Could offer some form of early signup etc. to check the actual interest in the idea

      2. 1

        And especially because it depends so much on good execution, it is so important to me to approach the whole thing as structured as possible