Minimum Viable Product, three wonderful terms so very misinterpreted and misapplied.
We often hear statements like:
The MVP does not need to have good UX
The customer adoption is low, the market traction is low and the return on investment is low
The MVP does not need to be complete
Core journeys partially missing and users do not find the product useful
The MVP will be redesigned at a later stage
More time and money needed to achieve the same outcomes
The MVP will be usability tested after go live
Design and development driven by assumptions with high risk of delivering the wrong thing
These are just a few we heard and read in articles through the years 😂
The term MVP is industry agnostic.
A Minimum Viable Product (MVP) is a set of orchestrated and validated core journeys within the budget and time allocated, that allow the users, with the best possible experience, to accomplish their key objectives.
Click on this link, to read a great article that dissects and demystify the definition of the term MVP.
A clear roadmap with milestones and an agreed plan with the team and relevant stakeholders (including the design team) guarantees the delivery of MVPs that will be profitable for the business and useful for the users.
Even if your MVP is not a fully grown product, your users will find it usable, useful and fit for purpose. They will return.
Comments