How 'Minimum' should a Minimum Viable Product (MVP) be for taking it to market?

Question

Asking this question in context to launching via Product Hunt and getting early adopters.

Nha Hyerin · Accepted Answer

- **"Minimum" doesn’t mean a lack of quality**: An MVP should deliver sufficient value and usability, even if it’s a smaller set of features.
- **Focus on the problem**: Ensure your MVP addresses the core problem and appeals to your target audience.
- **Build for feedback**: Include ways to learn from users, whether through surveys, tracking usage, or direct feedback.
- **Speed and efficiency**: Aim to launch quickly to test your assumptions, and be ready to iterate based on user insights.

Answer

It depends on your product and target audience, but generally I'd say an MVP should be just functional and polished enough to demonstrate the core value prop and get meaningful feedback from early adopters. Don't go overboard with features, but also don't put out something too rough around the edges. The key is getting it in front of users ASAP to start learning and iterating!

How 'Minimum' should a Minimum Viable Product (MVP) be for taking it to market?

Replies