How to scope an MVP that actually tests your idea

The phrase minimum viable product is often used to mean a smaller version of everything. That usually leads to a thin product that doesn't prove much. A better definition is the smallest thing that can answer your most important question.

Name your riskiest assumption

Every new product rests on assumptions. Customers have this problem. They'll pay for a solution. They'll switch from what they do today. Write yours down and choose the one that would end the idea if it turned out to be wrong.

Test before you build, if you can

Some assumptions can be tested without software. Customer conversations, a landing page with a clear offer or a manual service behind a simple form can all produce evidence quickly.

Cut by outcome

List everything the product could do, then ask which features a customer needs to reach the core outcome once. Keep those. Move the rest to a later list. Administrative screens and rarely used settings can often wait.

Don't cut trust

Minimum applies to scope, not to quality. Security, reliable data handling and a usable design aren't optional, because a poor experience tells you about the execution and not about the idea.

Decide what success means first

Before launch, write down what you'd need to see in order to continue. Otherwise, it's easy to read any result as encouraging.