A new product idea usually arrives with more features than a first release can carry. The purpose of a minimum viable product, or MVP, is to test the central promise with the least complexity needed for a real user to complete a real task. It should feel small, but still useful.
Name the job the product must do
Begin with one sentence: ‘This helps [a specific person] do [a specific task] so they can [a meaningful outcome].’ If the sentence needs several audiences or outcomes, narrow it. Then map the current way people handle the task. Notice where they lose time, make mistakes or give up.
Interview potential users about what they do today, rather than asking whether they like your proposed feature list. Existing behaviour is a better guide to the first release than enthusiasm for a hypothetical product.
Choose the smallest complete journey
Sketch the steps from arrival to successful outcome. Keep the features needed to finish that journey; park features that merely make it broader or more polished. For a booking product, that might mean finding a slot, submitting a request and receiving confirmation. A loyalty programme can wait.
An MVP is a complete answer to a small problem, not an incomplete answer to a large one.
Set learning goals before building
Decide what you need to learn from the release. Can users finish the main task without help? Where do they pause? Will they return when the need appears again? Choose a few signals you can observe through product analytics, support conversations and direct feedback. Avoid treating sign-ups alone as proof of value.
Launch with a feedback path
Invite a manageable group of users, explain what the product can do today and provide a simple way to report confusion. Watch them use the product if possible. Fix blockers in the core journey before adding new branches.
After the first round, decide whether to improve, expand or rethink the idea. A focused MVP gives you room to learn without committing your entire budget to assumptions made before anyone used the product.



