Minimum Viable Product (MVP)
A Minimum Viable Product, or MVP, is the smallest version of a product that real users can actually use and that gives you meaningful feedback in return.
The term MVP became widely known through Eric Ries's Lean Startup approach, which describes the version of a product that takes the least effort to build while still letting you test a core assumption with real users. Instead of spending months developing a complete solution, you focus on the one feature that delivers the most value and tests your most important hypothesis. The goal is to get genuine reactions as early as possible, rather than planning further based on guesswork. That lowers the risk of pouring time and money into features nobody actually wants.
An MVP is not a half-finished prototype and not a click-through demo. The word viable means users can genuinely accomplish something with it, even if the feature set and polish are still very limited. An MVP for an ordering app has to actually take an order, even if payment processing or a polished design are still missing. Fall short of that bar and you get opinions about an idea instead of solid feedback.
In practice, working with an MVP means running the build-measure-learn loop. You develop the smallest working version, measure how users actually behave, and use that to decide what to change next. This cycle repeats several times, replacing long planning phases with short, testable learning steps. The biggest risk is stripping the MVP down so far that it no longer shows the product's real value, which makes the data you collect worthless.
Practical Example
A trades business wants to build an app for handling job requests. Instead of implementing scheduling, invoicing, and a customer portal right away, it starts with a simple online form that triggers an automatic email to the team. Within six weeks, 40 requests come in through the form, and the data shows that more than half of customers also expect to see available appointment slots. Only with that insight does the business invest its estimated 15,000 euros in development budget into exactly that feature, instead of guessing upfront.
How Leanshift Helps
An MVP is Kaizen applied to the start of a project: small steps, real feedback, targeted adjustments instead of one big bet made on assumptions. That mindset carries directly into process work on the shop floor, where you also test an improvement on a small scale before rolling it out widely. It is a way of improving not just a product, but the team's ability to apply that same learning rhythm elsewhere.
Frequently Asked Questions
Is an MVP the same as a prototype?
No. A prototype is usually for internal demonstration or testing, while an MVP goes into the hands of real users for actual use, which gives you real usage behavior instead of just opinions.
How small can an MVP be?
As small as possible, but not smaller than what's needed to test your most important assumption. What matters is that the one core feature works completely, not how many features you include.
When is an MVP done?
An MVP is never finished in the traditional sense. It's considered complete once you have enough solid feedback to make the next development decision.