3 ms·
I like this concept of 'launch debt'. It's true. Moreover, some people seem to optimize their early process for fastest time to social gratification, and not fa
by jmitcheson 15y ago
I like this concept of 'launch debt'. It's true. Moreover, some people seem to optimize their early process for fastest time to social gratification, and not fastest time to user adoption.
What I mean is, if you rush too much and release something that "isn't quite there", then (in my opinion) your user adoption will be lower until you work out all your bugs. The only thing you would have gained here is that you got to tell your friends and family "we've launched" and gotten lots of pats on the back. Your friends and family don't care about the missing polish, but the users sure will. End in the end, they are all that matter..
- fragsworth 15y agoI think it's OK to release something that "isn't quite there" - in the sense that you don't expect to get too many users. Even with a small user base, you will gain vast amounts of information that you wouldn't have otherwise. From statistics and user feedback, you will learn lots more about what your product needs to do than if you're still in pre-launch development.