MDP vs. MVP

I first heard the concept of MDP as a Minimum Desirable Product from Sandy Sharma, Co-Founder of Indigo Slate and the Chief Digital Officer of Zensar Technologies, while we were working together on several projects. I like how Sandy was emphasizing Desirability before any further investment is made on a product. It led me to reflect on MVP in light of desirability in a fresh way.

The concept of a Minimum Viable Product (MVP) has its roots in the lean manufacturing methodologies developed by Toyota, later adapted for the tech industry as part of the Lean Startup approach. This shift, popularized by Eric Ries, emphasized creating an initial version of a product with only the essential features to test assumptions about customer needs without incurring substantial costs. In practice, the MVP approach enables teams to gather early feedback, pivot as necessary, and refine based on real user interactions before diving into full-scale production .

In my work across both Fortune 100 companies and startups, I’ve noticed that focusing solely on functionality often overlooks a critical aspect: desirability. MVP’s focus on functionality is invaluable, but it misses an opportunity to inspire early adoption. I believe there’s a preliminary phase—what I call the Minimum Desirable Experience (MDE). This phase focuses on designing a product concept that captures users’ interest and imagination, even if it’s just a prototype or an early model. The aim is not only to prove feasibility but also to ignite a sense of excitement and engagement, effectively validating that people will want to use it.

The MDE isn’t just about aesthetics or features; it’s a strategic layer of product development that goes beyond usability. It ensures that the design and experience reflect something users genuinely desire. By treating MDE as a precursor to MVP, teams can refine the product vision with feedback on both functionality and appeal, laying the foundation for a product that not only works but resonates with the market. This approach gives UX research and design strategy a greater role, helping ensure that future iterations align with user needs from the very start.