What is a minimum viable product?

What is a minimum viable product?

A minimum viable product, or MVP, is a product version designed to test an important assumption with the smallest practical set of capabilities. It should deliver enough value for intended users to try a meaningful workflow and provide useful evidence about the idea.

Define the learning goal and user outcome

Start by asking what you need to learn. For a wedding-management app, the hypothesis might be that a shared event and task workspace helps organizers coordinate preparation more clearly than scattered messages.

The MVP should let users experience that value. An organizer might create a wedding, add events, assign tasks, and see progress. A collection of disconnected screens would not test the same hypothesis.

Choose the audience and feedback method before expanding the feature list.

Preserve a complete core experience

“Minimum” refers to scope. It does not mean accepting broken workflows, missing permissions, or unusable interfaces. Essential validation, basic accessibility, and appropriate protection of user data remain part of a viable experience.

Dependencies matter. If assigning tasks requires collaborators, a workable collaborator flow may belong in the MVP even when it looks less exciting than dashboard charts.

Exclude capabilities that do not support the initial learning goal, such as advanced vendor analytics or elaborate theme customization.

Learn and decide what comes next

Observe how people use the product and ask about specific successes and difficulties. Measures might include whether organizers complete setup, return to update tasks, or still rely on a separate spreadsheet.

Use the evidence to improve the workflow, change the assumptions, or reconsider the idea. An MVP is a deliberate learning investment, not simply the first collection of features that was convenient to build.