Great post...giving me flashbacks to many of the products I've built the wrong way over the years. The things I've created that have gone the best were almost invariably stupidly simple and validated with a hacked-together solution that would embarrass any software engineer worth their salt. If I instead start by coding something elaborate, it's almost always a failure.
100%, Ryan! There are definitely many ways to validate before building the product. It could be as simple as building a landing page with an email field to capture "beta" users. If you notice that there is demand for it, you can use that as a signal to build. This way, you've, in some sense, validated the need and can reach out to some of these early adopters.
What are some ways you've validated things before building?
Great post...giving me flashbacks to many of the products I've built the wrong way over the years. The things I've created that have gone the best were almost invariably stupidly simple and validated with a hacked-together solution that would embarrass any software engineer worth their salt. If I instead start by coding something elaborate, it's almost always a failure.
100%, Ryan! There are definitely many ways to validate before building the product. It could be as simple as building a landing page with an email field to capture "beta" users. If you notice that there is demand for it, you can use that as a signal to build. This way, you've, in some sense, validated the need and can reach out to some of these early adopters.
What are some ways you've validated things before building?