MVP

Imagine you want to test whether people will pay for a service that turns company documents into short learning lessons.

One approach:

Build accounts, billing, analytics, an editor, AI generation, and a dashboard.

Another:

Manually create the first library for three customers.

Which teaches you faster?

An MVP, or minimum viable product, is the smallest version that can test an important product assumption with real users.

The key word is not “minimum.”

It is “viable.”

The thing still has to be useful enough to learn from.

For the learning-library idea, the biggest early question might be:

Will companies pay to turn their existing knowledge into this format?

You do not need a full SaaS platform to test that.

You need customers and a credible delivery experience.

Suppose you manually:

1. collect the documents
2. structure the curriculum
3. generate the lessons
4. publish a branded site

If customers pay and use it, you learned something valuable.

Automation can come later.

A broken version of the final product is not automatically an MVP.

If your test is:

Will people trust this for onboarding?

and the product constantly loses progress, the test is contaminated.

Bad quality can make good ideas look bad.

Ask:

What is the riskiest thing we need to learn?

Then:

What is the smallest credible experience that can teach us that?

That is more useful than asking how many features version one should contain.

An MVP is not the smallest thing you can ship.

It is the smallest credible thing that helps you learn whether the idea works.