Skip to content
SYCH-TECH
GlossaryProduct & Startup

Minimum Viable Product

Minimum Viable Product is a product and startup concept for shipping the smallest product that tests core value with real users so founders make clearer build-and-grow decisions.

This definition sits in our Product & Startup glossary cluster alongside Customer Acquisition Cost and Lifetime Value LTV.

Definition of Minimum Viable Product

Minimum Viable Product in practical startup work means shipping the smallest product that tests core value with real users. For lean teams, results are strongest when each cycle tracks learning velocity per engineering week instead of narrative momentum alone. A recurring failure mode is building a full feature set before validating the primary problem, which burns runway and delays real learning.

Why Minimum Viable Product matters

  • It gives a concrete lever to improve learning velocity per engineering week with limited team capacity.
  • It connects product, growth, and monetization choices to measurable outcomes.
  • It reduces wasted build time by forcing evidence before scale.
  • It prevents building a full feature set before validating the primary problem from becoming an expensive recurring pattern.

Example: Minimum Viable Product for an indie product team

A small startup applies Minimum Viable Product by focusing on habit app launches with manual reminders before investing in AI coaching. After the next cycle, they review movement in learning velocity per engineering week and double down only on what works.

Related terms for Minimum Viable Product

Terms that reference Minimum Viable Product

Common questions about Minimum Viable Product

How should a small team apply Minimum Viable Product without overengineering?

Start with one decision tied to learning velocity per engineering week and use Minimum Viable Product to clarify that bet. Ship learning loops fast and document what changed outcomes.

What is the most common mistake with Minimum Viable Product?

The common trap is building a full feature set before validating the primary problem. When this happens, teams confuse activity with progress and miss PMF signals.

Keep reading

More in Product & Startup

Browse Product & Startup glossary

Explore topics related to Minimum Viable Product