Augment

MVP Design Checklist: What a Launch-Ready First Version Needs

A minimum viable product is minimal in scope, not in clarity. Use this checklist to find the gaps before your first users do.

A product roadmap sketched on a whiteboard with launch milestones
Photo by Slidebean on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • An MVP should do one job well and make that job obvious in the first minute.
  • Clarity of the core flow matters more than the number of features.
  • Cover the unglamorous basics: onboarding, empty states, errors, and a way to get help.
  • Test with five real users before launch. You will find the biggest problems quickly.

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

AreaCheck
OnboardingSignup is short and leads to a first useful action
Empty statesEvery blank screen explains what to do next
ErrorsMessages are plain and say how to recover
FeedbackEvery action shows that it worked
HelpThere is a visible way to ask a question
MobileThe core flow works on a phone if users will use one
TrustPrivacy, 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.

Frequently Asked Questions

One clear core job, a working end-to-end flow, and the basics: onboarding, empty states, error handling, and a way to get help.

Sources and further reading

  1. The Lean StartupEric Ries · Undated page · Accessed
  2. Why You Only Need to Test with 5 UsersNielsen Norman Group · Published · Updated · Accessed
  3. Usability (User) Testing 101Nielsen Norman Group · Published · Updated · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by Slidebean on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

MVP Design Checklist: What a Launch-Ready First Version Needs | Augment. Lab