Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
1
Like
12
Comments
How do you decide which features to prioritize in your product
by
Hanzlaijaz123
What advice would you give to someone who is just starting out
Based on the feedbacks. I am developing small pieces and asking other people what they think about it and their expectations.
Go with bare minimum features that are enough to launch product. For example - Tweet Scheduler, it should be able to schedule tweets and user should be able to modify them whenever it is required. By modification, I mean delete, update, and change schedule date.
Then start adding a features one by one which your competitors has and can be added quickly. Keep complex one for later.
Some good advice here, but wanted to add a bit more (a Product Manager by profession, so prioritisation is a core part of my job):
1.1. Will this get my customer to experience the 'core value' of the product?
1.2. Will this unblock my customer on the way to experience said 'core value'?
Treat every piece of feedback (customer / critique / investor suggestion) this way. It's difficult to be objective, but as a rule of thumb, always try to have an answer for why you made that decision [even if you go in the direction of just assigning must-have/could-have, etc]!
Let me know what you think!
I would do a simple prototype of the idea in AdobeXD or some similar tool. Then I would let 10-30 people test it and see what features they liked the most. Then it could be smart to prioritize the tasks based on feedback value and expected time.
Once you start working you will get biased on what features are the most valuable, so keep talking to potential users.
Good luck!
Create a spreadsheet with two columns: the feature and a dropdown listing with two choices: Must Have & Nice To Have.
Then only focus on the "Must Have" until you get market fit and enough revenue to hire people to work on the "Nice To Have" ;)
Happy hustling 🚀🌙
For my current project I've been making sure to track and log feedback from different categories of people:
By doing marketing and talking to users you'll begin to understand what features interest people plus which features people really use and you can build on top of.
One tip - be very careful adding completely new features as this can exponentially increase the scope of an app/tool. Building on top of existing features or adding slight mutations of these features will help refine the core value.
One more tip - if you do need to add new features it can be really helpful to completely isolate these as their own app, test the feature, then integrate it into your core app if people like the feature and find value in it.
Hope this helps!
sort features on following criteria need(must have, good to have etc.), development effort required and pick the top