roducts released to production is expected to be ready for customer's production. Waiting till all features are completed is the worst idea that a startup can do. Product features must grow over time and quickly, without compromising quality. But before showcasing the product either for prospects or for pitching, you need to have the most minimal set that can solve a bigger problem. And that is MVP.
Grow the product
You cannot get a whole ERP in one shot; you cannot get a full scale POS in one pass. Every product needs time to grow and mature. The very first golden version to prove that your idea really works, is the aim of the MVP. For that we cannot boil the ocean. When you try to cover with a lot of spread, you end up losing time.
Your product design when you go with MVP approach is to extend the MVP to the next level without much disturbance. Some orgs with a lot of cash, even make throw away MVPs, but that will not help a frugal startup. Every feature you built on MVP must still work in the scaled up product version.
Do not clutter
Putting so many features in the MVP will clutter the vision. It becomes tough to demos on a large feature set product. Also when we throw so many features in MVP, each feature keeps opening its branch for open ended questions. This will become unmanageable.
Depth is more important than the spread. One strong message is the key.
Some startups build a feature just for the sake of differentiation. Unless it is the true factor for the customer to use the product, do not build that feature. MVP gives you the required time to focus on the most important core product.
The most common mistake that every techie falls into is chasing features, thinking that all features are equally important. NO. First features need to be prioritized. Even before building the product, just have mock ups and take a feedback from 10 known people in that space. No harm.
What if this feature does not exist?
Ask this question every day. Unless you are fully convinced that the customer will not use the product if this feature does not exist, do not build it. Even if you want to build those features in the future, just make mock ups and tell the customer that those features will be released soon. If they see even the very basic screenshots, they may get the feel; but to create that feel you do not have to develop a full scale product.
MVP MUST INCLUDE:
- A feature that the initial customer cannot live without
- Your true value adding differentiation
- Mock ups as appropriate to show that you are bringing those features
- Working MVP and not just all mock ups!
Every day you build the product, requires money and time. To optimally use money and time, ensure you stick to your MVP plan. Never boil the ocean.
More from
Start-ups
category
