What an MVP is and how small it should be

Lens: Simplicity, focus and saying noLast reviewed:

Short answer

An MVP, a minimum viable product, is the smallest thing a real customer can use that shows you whether they want the result. It is not a broken version of your final product. It is an experiment. Make it small enough to get into one person's hands within a few weeks, and have it do only the one thing the customer comes for.

What an MVP is for

The point of an MVP is learning, not revenue and not praise. You have one specific question, for example whether people will pay for this result, and the MVP is the cheapest way to answer that question.

If you do not know which question the MVP is meant to answer, it is not time to build it. Write the question first, then the smallest thing that answers it.

An example of the method, not of a real company: someone who wants to start a weekly meal planning service does not need to build an app first. They can send a plan by hand to a few families every week and see who pays for the second week. If nobody does, an app would not have helped.

How small

Smaller than you think. One simple rule from Ousta: if you are not embarrassed by your first version, you probably waited too long. Every feature the customer can do without and still get the main result has to go.

Often an MVP is not software at all. It can be a form and a spreadsheet, a service you do by hand yourself, or a weekly message you send by hand. The customer does not see the difference, because they only see the result.

What to leave out

Ousta's lens here is saying no. Write a list of every feature in your head. Then next to each one ask: without this, does the first customer still get the result? If the answer is yes, cross it out.

Things that usually go: complicated user accounts, settings, a separate mobile version, automatic payment when you can send an invoice by hand, and anything you only need for the day you have lots of customers.

  1. Write the question the MVP has to answer in one sentence.
  2. List every feature in your head.
  3. Cross out every feature without which the result is still delivered.
  4. See what you can do by hand instead of building.
  5. Set a near date for the first version to reach one person.

When to make it bigger

When the people who used it came back, paid, or brought someone else. Those signs say the result is worth something. Then automate the parts you were doing by hand, one at a time, starting with the one that takes most of your time.

If nobody came back, do not add new features. Find out why first. The problem is usually the result or the customer, not a missing feature.

To find out, ask those same few people when they last used it and what stopped them from coming back. Their answers tell you which part to change and which part you never needed.

Common mistakes

Building a complete product and calling it an MVP. If it took months, it is not minimal any more. Choosing tools and technology before you know who the customer is. And listening to one customer who asked for a particular feature instead of looking at the pattern in the rest.

Common questions

Should an MVP be free?

Not necessarily. If your question is whether customers will pay, giving it away for free spoils your answer. A real price, even a low one, teaches you more.

What if people see the MVP and think my product is weak?

Early customers usually come to get their problem solved, not for looks. If they get the result, they forgive a small product. Tell them plainly that this is the first version.

Do I need a programmer for an MVP?

Often not. First see whether you can deliver the same result with ready-made tools or by hand. Leave programming for when you know what needs to be automated.

Terms in this guide

Last reviewed:

This guide is a method, not a promise of results. Your situation is not the same as anyone else's.

Ask the board your own question