I used to agree with this but it's unlikely a MVP will get enough traction to truly damage a software brand. Of course, this depends on the medium (computer software [harder to update] vs website service) and target audience (investor vs public) and if your audience understands it's a MVP.
Question is: should a user come by your MVP now or in six months when it's "done"? The earlier people see your product and not like it, the earlier you can hone it for future users. Plus, a final version could be rebranded if the MVP was that bad.
Granted, I fell into this trap with my website. I kept putting it's release off and now am learning how to refine it as I see how it's used by others.
For instance, I thought the news section of my site (http://www.survivalscout.com/news) would be really popular but almost no one visits it. It's my favorite part but I seem to be in the minority according to the logs. If I had known that earlier, I may have spent less time making it.
Question is: should a user come by your MVP now or in six months when it's "done"? The earlier people see your product and not like it, the earlier you can hone it for future users. Plus, a final version could be rebranded if the MVP was that bad.
Granted, I fell into this trap with my website. I kept putting it's release off and now am learning how to refine it as I see how it's used by others.
For instance, I thought the news section of my site (http://www.survivalscout.com/news) would be really popular but almost no one visits it. It's my favorite part but I seem to be in the minority according to the logs. If I had known that earlier, I may have spent less time making it.