Most product managers think of MVP (Minimum Viable Product) as: "The V1 of the product they want users to use." That is 100% WRONG. In Product Management, few concepts (like MVP) are frequently used, yet gorssly misunderstood. MVP as a concept has revolutionized the way product teams approach product development. Yet, its essence is often lost in translation. Let's get to the heart of what MVP truly means The most accurate definition of MVP In the words of @ericries (pioneer of the Lean Startup movement): “A Minimum Viable Product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.” Let's break this down: Minimum: Build something that requires the least amount of effort to meet the goal. The goal: learn something specific about the customer “As you consider building your own minimum viable product, let this simple rule suffice: remove any feature, process, or effort that does not contribute directly to the learning you seek.” - Eric Ries Viable: Whatever you build, it has to be able to conclusively validate if and how your idea will solve the customer's problem. “Success is not delivering a feature; success is learning how to solve the customer’s problem.” - Eric Ries Product: This is where it gets tricky. There is no real definition of what the product should be. It could be a landing page, a google sheet, a survey, an email waitlist, an experiment. And it could be none of the above. “In the Lean Startup model, an experiment is more than just a theoretical inquiry; it is also a first product.” - Eric Ries So, as PMs, when you're thinking about MVPs, always remember: - MVPs are meant to help you learn. - MVPs should answers to the most critical questions - The answers that define the shape of your product - MVPs are meant to be built quickly - MVPs are meant to be simple Let's look at examples to put this into perspective: Dropbox MVP: A demo video showcasing the possibility of syncing files across devices Learning: is there demand to sync files Success: Video went viral; significant sign-up interest proving demand. (youtu.be/dR7tJ8wAI3M?si=qbsQ…) Airbnb: MVP: a simple website, with photos of their place L: will people be ok staying at other people's homes S: Immediate bookings, showing a market for unique accommodations (fueled.com/blog/airbnb-mvp/) Zappos: MVP: founder took photos of shoes from local stores and posted them online L: will people buy shoes online S: Orders, showing willingness to buy shoes online. (qr.ae/pKnTlr) Twitter: MVP: SMS-based platform to communicate with a small group L: are people interested in sharing short messages S: user growth and high engagement (firstversions.com/2015/07/tw…) -- How do you avoid the most common pitfalls when envisioning MVPs?