Too Many Features, Too Little Time

Bryce Murray
11 replies
We've built our MVP. Along the way, we identified plenty of features we could add to it. We can't add them all, but we want to continue building a great product. What strategies do you use to prioritize which features to build next?


Ng Fang Kiang
Build a simple feature that would attract people to sign up and use immediately. Pick the core features.
Bogomil Shopov - Бого
Well that't the basics of Product Management. I'd recommend you to start with this book:
Bryce Murray
@bogomep This looks great! Thanks for sharing. Project management is definitely out of my core competencies, and it's been difficult to find valuable resources (plenty of noise out there). Thanks again!
Bogomil Shopov - Бого
@bryce_murray I'll be happy to talk to you and give you some more details if I understand what you need exactly :)
Fabian Maume
Ask your users which feature they are willing to pay for. You can also prioritize features which give recurrent value over on-time value delivery.
Do you have a Roadmap? Ideally one your users can vote on?
Bryce Murray
We're getting close to launch! We do have a roadmap, but we're trying to determine what comes next on that roadmap. We've discovered plenty of things that would be practical, but how do you know what's worth building? With fewer users, maybe the answer is wait until we have XX users before having them vote. Thanks for your feedback!
Caleb Leong
a/b test with as little cost as possible, feedback by asking current users what they feel is important.
Mohmmad Khalaf
Well Bryce, I think you are jumping into the feature game trap. it's too hard to compete in today's markets with a feature-based approach, and even if you came with a winning feature the market sooner or later will follow and copy you. a great example to demonstrate how hard its today would be Marketing Technology Landscape, I have attracted research talking about how fast the market is growing. Nonetheless, what you should do in my opinion is continually perform user research to have a greater understanding of the user needs and pain points. you should always be solution agnostic while you are trying to identify your problem statement. if you have one try to validate it. if it's invalid go back to the discovery phase and try to find what is the problem. You still in the MVP stage all what you should care about is building a solid product hypothesis. Articles I would recommend you to read: Also, Shameless plug, you can check my notion database for PM it has more than 1000+ articles it could be handly. Good Luck.