Some companies spend nine months building something nobody uses. Not because the team was bad, but because no one validated the hypothesis before writing code. The MVP is a direct answer to that problem.
Minimum Viable Product is the smallest version of a product that still solves someone's real problem. Notice the word: real. Not a rough draft, not a stakeholder demo, not a polished Figma screen. A small product, but whole for the person who uses it.
What an MVP is, and what gets confused with it
The most common mix-up is treating an MVP like an incomplete product. It isn't. If the user can't finish the task they came to do, the lean version doesn't qualify as MVP, it's a partial delivery dressed up in MVP clothes. Trim the breadth, meaning how many things the product does, not the depth, meaning how well it does what it does.
Think about how good restaurants test new dishes. The chef serves a limited version, at a few tables, before adding it to the menu. The customer pays, eats, gives feedback. If it works, it becomes a regular item. If not, that was a cheap experiment, not a failed launch.
Why starting small actually pays off
Three things shift when you ship in a tight scope. First, feedback stops being 'I think users will like this' and turns into 'users actually used it'. Second, the cost of learning you took the wrong path drops a lot: three weeks is not the same as nine months. Third, the team learns how to ship and iterate, instead of planning forever.
How to carve yours out
Don't start with a feature list. Start with the user you want to serve and the first task they need to complete to get value. Anything outside that path stays out of the MVP, even if it feels important. And 'feels important' doesn't count as an argument.
This is where most teams trip: they want to squeeze in 'just one more feature'. Before they realize, the MVP became a full v1, late, expensive, and bloated. Resist. The dropped feature goes to the backlog. It can come back later, if the data asks for it.
“An MVP isn't a project phase, it's a stance. Teams that internalize that ship fast for years, not just at the start.”
Shipping and stopping is wasteful. The real gain comes from the loop: small release, measurement, decision, next release. In three months that loop gives you a kind of clarity no upfront plan can match. In six, you actually know whether the original bet was sound.