A practical way to plan your first MVP

Start with the problem

An MVP is a way to test whether a focused product experience can address a real user need. It is not simply a smaller version of every feature you hope to build later.

Describe who has the problem, when it occurs and what they do today. If the problem is still vague, spend time learning about it before choosing features.

Decide what you need to learn

A useful first release answers a small number of important questions. Write down the assumptions that could change your product direction, then decide what evidence would help you evaluate them.

• ✓Will the intended audience recognize this problem?
• ✓Can the core task be completed with the proposed experience?
• ✓What would make someone return or recommend it?

Choose the smallest useful scope

Map the main user journey from the first step to one meaningful outcome. Keep the features needed for that journey and defer items that do not help deliver it or learn from it.

A narrow scope can still feel complete. Clear onboarding, helpful empty states and basic feedback often matter more than a long list of secondary features.

Learn, then make the next decision

Plan how you will collect feedback before launch. Decide which behaviors, support questions or user conversations will help the team understand what is working.

After release, compare what you learned with the assumptions you started with. Improve the experience, adjust the audience or rethink the product direction based on evidence.