The title is a bit of a garden path sentence[1], since "build" can be a noun or a verb.
I initially misread it as, "Before launching (your) build, software people use" and was confused by the apparently nonsensical second clause[2]. "Before launching, build software that people use" would be a less ambiguous wording.
[2] well, semi-nonsensical. If you ignore the plurality disagreement between subject "software" and verb "people", then "software people use" could be interpreted as "software occupies a purpose for which something may be employed", which is par for course in corporate buzzspeak.
As much as I hate to be that guy, I don't really see anything new here. "Find your users first, build an MVP around one core feature, and test often!" is basically startup gospel at this point.
I suppose I wrote this blog entry as much for myself as for other nascent entrepreneurs. If you've been in the business for awhile, and your successful, the content shouldn't be new to you.
Some good thoughts here and as the founder of countless failed startups I can totally relate to the message.
However, over the years I've come to the conclusion that "Finding Customers" is what you do when you are a contract designer or developer. I've reframed this concept into "Validate the value proposition". Yes, this is kind of like "finding customers" but redirects the focus to doing what you really need to do and that is "prove in some quantitatively valid manner that your target market will in fact purchase and use your app".
The big problem with this approach is that developing a "quantitatively valid methodology" is tricky and will be different for every startup and market. That said though, if you can figure out a way to do this it will greatly enhance your chances of both securing angel and VC funding and of being successful.
I love talking about this stuff though and greatly appreciate the efforts of people like lian who take the time to write down their thoughts.
6 comments
[ 17.3 ms ] story [ 75.3 ms ] thread[1] http://en.wikipedia.org/wiki/Garden_path_sentence
[2] well, semi-nonsensical. If you ignore the plurality disagreement between subject "software" and verb "people", then "software people use" could be interpreted as "software occupies a purpose for which something may be employed", which is par for course in corporate buzzspeak.
Not necessarily. If you are a regular visitor to HN, chances are that you'd come across similar content/gist more than once.
However, over the years I've come to the conclusion that "Finding Customers" is what you do when you are a contract designer or developer. I've reframed this concept into "Validate the value proposition". Yes, this is kind of like "finding customers" but redirects the focus to doing what you really need to do and that is "prove in some quantitatively valid manner that your target market will in fact purchase and use your app".
The big problem with this approach is that developing a "quantitatively valid methodology" is tricky and will be different for every startup and market. That said though, if you can figure out a way to do this it will greatly enhance your chances of both securing angel and VC funding and of being successful.
I love talking about this stuff though and greatly appreciate the efforts of people like lian who take the time to write down their thoughts.