10 shades of MVP (or: how to develop a product without developing a product...)
A minimum viable product (MVP) is often perceived as a subset of the real product: a minimized version, lacking some features or missing some UI fine-tunes, but in fact, an MVP is more of a tool to test the core idea of what’s intended to be a product someday. While the name MVP suggests that it has to be both a product and a viable thing - the software industry has proven it doesn’t have to be the case. In fact, an MVP doesn’t have to be a product at all: it can be an email, a Facebook group, a service, or a bunch of processes performed manually. An MVP is there to help you test your business riskiest assumptions, see if your product can provide enough value to attract customers, and collect some feedback that can guide you through the product development. And last, people should be willing to pay for it (with real money or some level of commitment) - otherwise, it’s just theoretical exercise that cannot prove that the idea is...