| I would also add learning to evaluate your idea(s) objectively. When you think you've thought of a great idea, by definition, you're biased toward it. If you then start building it, the sunk cost makes you even more resistant to abandoning it. In my experience, just "building the product" can take a lot longer than you expect. I've spent several months building out what were mostly CRUD apps. Why? I didn't realize it at the time, but I was working part time, I had to figure out how to do many things for the first time, I had to keep myself motivated, and I had to do development but also design and PM work. If I was working on something new, I probably would: 1. think of a problem to work on 2. talk to a lot of users following the Mom Test (keeping in mind your product has many personas of users) to validate the problem 3. think of a lot of ideas to solve the problem 4. somehow identify what idea to prototype first and what the feature set should be 5. prototype it in Figma, show it to users, improve the prototype until customers are asking "when can I buy this?" I haven't done this yet. If anyone has any suggestions for getting from set of ideas -> a prototype users want, I would love to hear them! |