MVP: what to build first and what to leave out
A minimum viable product, or MVP, is the smallest version of a product that lets you learn whether people will use it. The term was popularised by the Lean Startup approach. It is a way to test an idea with real users before spending the full budget.
By the FocalID team in Colombo, , 2 min read

What an MVP is not
An MVP is not a rough draft of the whole product, with every feature half finished. It is one complete journey done properly. A food-ordering app that lets a customer order from one restaurant and pay is an MVP. One with ten screens of settings and no working payment is not.
How to choose what goes in
- Write down the one thing you most need to learn, for example “will shop owners place repeat orders in an app?”
- Pick the one type of user who matters most for that question.
- Map the single journey that delivers the value to them, from start to finish.
- List every feature idea, and keep only those the journey cannot work without.
- Do the rest by hand at first. Sending invoices manually for the first twenty customers is fine.
What you must not cut
- Security and privacy: logins, permissions and protection of personal data.
- Reliability of the main journey: it must work every time, even if it does little.
- Measurement: basic analytics, so you can see what users do.
- A way to hear from users: a feedback link, a WhatsApp number or a phone call.
Set the test before you launch
Decide in advance what result would tell you to carry on and what would tell you to change direction. For example: thirty shops invited, at least ten placing a second order within a month. Without a target set beforehand, any result can be read as success.
After launch
Watch what people do, not only what they say. Talk to the users who stopped. Then choose: build the next most-needed feature, change the product, or stop. Building in short cycles and letting evidence set the next step is the idea behind adaptive software development.
Common questions
How long should an MVP take to build?
Short enough that you learn before the budget is spent. If the first version will take more than a few months, the scope is probably too large.
Is an MVP the same as a prototype?
No. A prototype shows how something might work. An MVP works, and real users can use it.
Does an MVP have to look polished?
It must be clear and trustworthy to use. It does not need every visual refinement.

