An MVP is not a smaller version of every feature in the final vision. It is the smallest credible product that can test the assumption most likely to make the business succeed or fail.

Name the Riskiest Assumption

Write down what must be true for the idea to work. It may be that customers trust the workflow, that a process can be automated, or that the benefit is important enough to justify switching tools.

Choose One Core Journey

Define the user, the trigger that brings them to the product, the action they need to complete, and the outcome they receive. Everything outside that journey must earn its place in the first release.

Decide What Evidence Counts

Set a measurable signal before launch: completed workflows, repeat usage, time saved, qualified requests, or paid commitments. Downloads and page views rarely answer the most important product question.

Build for Learning and Trust

Keep the scope narrow, but do not compromise the reliability, security, or clarity users need to evaluate the product honestly. A broken test produces misleading evidence.