Create products that people love by solving problems. If your idea doesn't solve a particular problem you'll have a hard time finding users, no matter how many features you add. It doesn't matter if your idea doesn't benefit everyone in the world, as long as you have a few customers who desperatly need your product, you're in business.
Required readingThe MVP development cycle is based on a set of hypotheses. You're the scientist and the MVP is your experiment. If you can prove or disprove some of your initial hypotheses, you can get colser and closer to building a product people love and achieving product-market fit. For example, say you wanted to build a tool to automate every day tasks for small business or enteprises to use (using Zapier as an example here). First, you would have to determine whether these companies would even pay to use such a tool. As you go on, you will have to confirm hypotheses if you want to make your product better.
Required readingOnce you've come up with your idea and established a few hypotheses about your core users, it's time to go and validate your idea. Using tools like surveys, customer interviews and landing pages you want to confirm whetehr your product is in demand and whether you are actually solving a problem your target market has. Make sure you validate your idea before you build anything, because you want the ability to change and tweak your product at a moments notice to achieve product-market fit, while reducing costs.
Required readingLaunching quickly is of the utmost importance when launching your MVP. When you lauch quickly you are able to get that feedabck from potential users that will help improve your product. It's better to have a crappy product and/or website and a user base than a beautiful product but no user base or even validation of an existing market for your product. If you don't launch quickly you'll never know if people actually want your product and you might end up wasting months of your time and a lot of your time.
Required reading