3 years ago1,000+ Views
MDP vs MVP vs MFP: The hypothesis-driven approach to product development
These days I have heard from many people, smart people, that they are looking to apply lean startup mentality to their products. The issue is that while in theory lean startup mentality is simple, in reality it is a very difficult concept to apply. Your product team needs to build the product to the where it is possible to test and then pivot correctly. How do you, however, define this level of product readiness? This article brings forth an interesting wrinkle that could help answer that question. In order to effectively take a hypothesis-driven approach to product development, you need to decide what is your focus: business or user experience. You need to decide between building the MVP or the MDP. a) According to Eric Ries, he calls MVP "So, the minimum viable product is that product which has just those features (and no more) that allows you to ship a product that resonates with early adopters; some of whom will pay you money or give you feedback." Basically the premise is that MVP is to test whether you have a product with a market or not? b) Minimum Viable product centers around the business perspective -- what's the minimum I need to build in order for me to figure if I have a business? c) Minimum Desirable Product is the simplest experience necessary to prove a high-value, satisfying product for users -> what is the core of the product you want to build to satisfy users, not how you can make money from them… Lastly the article goes into a little of detail on when and why you might realize that the MDP nor the MVP are suitable for your purposes. In which case, you will need to consider the MFP: d) Minimum feasible product - what is the smallest amount of work necessary to field a credible candidate for an "in lab" solution to the product"
4 Like
1 Share