MVP

An MVP solves the problem of learning too late. Instead of building a complete product before testing assumptions, a team ships the smallest useful version that can validate whether the idea creates value.

Where it fits

An MVP belongs in software management and product discovery. It connects product judgment to engineering tradeoffs because the point is not to build less forever, but to learn faster with less waste.

Motivation

Teams often overbuild because they confuse a complete vision with the first useful experiment. An MVP narrows the first release to the few capabilities needed to test adoption, usefulness, or feasibility.

Example

For a recommendation product, an MVP might use manually curated recommendations before investing in a full machine-learning system.

Common mistakes

• Treating an MVP as a low-quality product instead of a focused learning tool.
• Building too many edge cases before validating the core value.
• Measuring delivery instead of learning.

Related concepts

• POC
• Acceptance Criteria
• Roadmap