Member-only story
Sorry to anyone who thought this article was about LeBron James, I’m going to touch on a subject that is close to my heart professionally, and unfortunately for my bank account, I’m not a basketball player, but a Product Owner.
I work for a consulting company and we develop digital products for different companies. Many of them come to us with product ideas and request the development of an MVP because they expect a product to be in production quickly. Unfortunately, the scope of the MVP does not always live up to their initial expectations (most not knowing exactly what is behind the term MVP) and this leads to situations of frustration.
Through this article, I want to share with you, in a few minutes, my vision of what an MVP is to clarify this concept and avoid future misunderstandings.
The MVP “by the book”
For starters, where does the term “MVP” come from? “MVP” stands for “Minimum Viable Product”. It was popularized by the Lean Startup methodology which defines it as something that “allows a team to reap maximum validated learning about their customers with minimum effort.”
Behind the MVP hides the idea of setting up a solution, as minimal as possible (therefore not always coded) and measuring its impact on users in order to learn about its value proposition, either by validating the impact…
