Subscribe
Sign in
How do you prioritise features for your Roadmap?
The way I like to approach this is to start by figuring out which features have the highest engagement and which ones don’t get used. Then identify which steps in your workflow cause the biggest drop-offs—where users are getting stuck. And finally, seek to understand your users’ needs, their sources of hesitation, and the conversations going on in their minds.
But there are so many different ways to tackle this, keen to hear your approach!
2
Replies
Best
Julian Burr
I think it's always valuable to have a clear set of rules that allow you to apply a "score" to any given feature, based on things like:
- impact on user experience
- impact on churn of existing clients
- impact on maintainability of the feature (e.g. DX improvements)
- estimated effort to implement change/feature
How exactly you score these will be different depending on your product and even depending on the stage the product is in IMO (an early startup might put more emphasis on the low effort high impact features, where an established product might focus more on the high impact features even if they are high effort, etc)
One key in my opinion is to not only focus on new features as part of your roadmap. Iterating over existing features, or even deleting features is often as valuable if not more valuable 😊
PS: adding measurements (e.g. analytics events) where they are missing to make informed decisions on those scores should also be part of the roadmap imo
Report
Share
@jburr90 Great answer, I completely agree!
I especially like the part where you discussed "One key in my opinion is to not only focus on new features as part of your roadmap. Iterating over existing features, or even deleting features is often as valuable if not more valuable 😊"
It's so important to reflect on existing features/ projects.