I think that there shuold be some level of validation before implementing, but when it comes to developing net new products/features (especially AI powered ones), I've found a couple things:
2. The initial "idea" often morphs and changes as you discover what is/isn't possible with the current state of the technology - as such, the idea you validated initially may end up being different enough from where you end up. In this case, it's important to validate and iterate along the way.
Thanks for the product founder fit! It’s great if you’re already passionate enough about a problem that you’re involved in those communities or even leading them.
What do you think of product led growth demand testing before implementation. Here’s my example of getting 100 sign ups for a donut image generation app before building it:
Love products over features. Why not validate before implement?
I think that there shuold be some level of validation before implementing, but when it comes to developing net new products/features (especially AI powered ones), I've found a couple things:
1. Informed Intuition is a great way to think about building new ideas (https://jacalulu.substack.com/p/informed-intuition-over-deep-rigor) - in this case, validation usually comes after an MVP has been built.
2. The initial "idea" often morphs and changes as you discover what is/isn't possible with the current state of the technology - as such, the idea you validated initially may end up being different enough from where you end up. In this case, it's important to validate and iterate along the way.
Thanks for the product founder fit! It’s great if you’re already passionate enough about a problem that you’re involved in those communities or even leading them.
What do you think of product led growth demand testing before implementation. Here’s my example of getting 100 sign ups for a donut image generation app before building it:
https://bit.ly/aidonut