Minimum does not mean unclear
The Lean Startup idea behind an MVP is to learn as fast as possible with the least effort. It is not a license to ship something confusing. If users cannot tell what your product does, you learn nothing about whether it is valuable. You only learn that it is unclear.
The core job
- Can you state the one job the product does in a single sentence?
- Does the first screen make that job obvious?
- Can a new user complete the core flow without help?
- Is the result of that flow clearly visible and useful?
The basics people forget
| Area | Check |
|---|---|
| Onboarding | Signup is short and leads to a first useful action |
| Empty states | Every blank screen explains what to do next |
| Errors | Messages are plain and say how to recover |
| Feedback | Every action shows that it worked |
| Help | There is a visible way to ask a question |
| Mobile | The core flow works on a phone if users will use one |
| Trust | Privacy, pricing, and contact information are easy to find |
Test before you launch
Run a short usability test with five people who match your target user. Give them a task, stay quiet, and watch. NN/g's research on small tests shows that five participants reveal most of the common problems in a qualitative study of one user group. Fix what you see, then test again with a few more.
Decide what you will learn
Before launch, write down the two or three questions the MVP should answer, and the numbers that will tell you. A launch without a learning goal is just a release.



