MVP vs Validation: Which Should Come First?

Many teams build an MVP when they really need a demand test first. The order depends on what uncertainty you are trying to reduce.

An MVP is useful when the biggest uncertainty is whether people can use a proposed solution successfully. A validation experiment is useful when the biggest uncertainty is whether enough people care about the problem and proposition in the first place.

Start with the uncertainty that matters

Teams often jump straight to an MVP because building feels concrete. But if market demand is still highly uncertain, the MVP may answer the wrong question very expensively.

A landing page, concierge service, manual prototype, demo, or smoke test can often answer the demand question faster. If the response is weak, you have learned something important without committing to months of product work.

What to measure

Once demand is credible, an MVP becomes more valuable. Now the experiment shifts from “does anyone care?” to “can this workflow deliver the promised outcome well enough that people keep using it?”

The right order is therefore based on the largest unknown. Market uncertainty suggests validation first. Solution or usability uncertainty suggests an MVP may be appropriate sooner.

How to run the test

This does not mean you should never prototype early. A rough prototype can make a market test more believable. The mistake is treating the prototype itself as evidence of demand.

Build only enough product to answer the next important question.

Common questions