Deliver it fast, then improve it
Usually, we think more features are proportional to increasing the value for the end user. Or worse, we start designing something from our perspective that will solve users' needs. That's completely wrong.
For many years, I have seen projects fail, some even before launching. One common reason is trying to include all features and delaying the release until everything is complete. And when it gets released, we enter an iteration of changes that never ends because what we have built is too complex or useless for the end user.
Usually, we think adding more features is proportional to increasing the value for the end user. Or worse, we start designing something from our perspective that will solve users' needs. That's completely wrong.
A minimum viable product (MVP) is a version with just enough features to be usable by early customers, who can then provide feedback for future product development.
When designing a product, listening to customer feedback is critical. In this way, we don't infer what the product should do and go in the direction the actual customer needs our product to go. That's how we get close to success.
The most important fact is that the faster the end user starts using our product or a feature, the quicker we will improve and satisfy their needs.
Remember, the customer's needs are the key to designing a product. And even if our product is out, the customer's feedback will polish our final product. It's a continuous iteration of delivering and listening to feedback.