Minimum Viable Product (MVP)

A minimum viable product is an intentionally limited offering used to learn whether a proposed solution addresses an important problem. “Minimum” refers to avoiding unnecessary scope, not removing essential usefulness or safety. The team should identify a specific assumption, decide what evidence would challenge it, and create a version that customers can realistically experience. An MVP is a learning tool, not a synonym for a cheap or unfinished website.

For a service firm, an MVP might be a carefully scoped introductory package offered to a small set of suitable customers before building a full self-service platform. Useful evidence includes observed task completion, repeat use, willingness to pay and qualitative feedback about what failed. A prototype can test comprehension, but a prototype shown in a meeting is not always an MVP if no real product or service value is delivered.

MVPs should include adequate privacy, accessibility and security for their intended use. Teams should distinguish the experiment’s learning criteria from launch vanity metrics. After reviewing the evidence, they may improve the idea, change the target customer or stop development. The purpose is to reduce uncertainty responsibly before committing to a larger build.