Minimum Viable Product (MVP)

Technical explanation

An MVP is designed around the riskiest assumption, a target audience and measurable evidence in a build–measure–learn loop. It may be software, a prototype or a service experiment, provided it can test the hypothesis credibly.

Business relevance

The approach limits investment before evidence, shortens feedback cycles and helps teams decide whether to persevere, adapt or stop.

Implementation example

Before building a full automation platform, a team delivers a manually operated concierge service to a small target cohort and measures repeat use and willingness to pay.

Limitations and common misconceptions

Minimum does not mean unusable, insecure or low quality. An MVP that cannot deliver the value proposition tests execution failure rather than demand, and positive early feedback may not prove scalability.

Topics

Sources