How do you measure success for a new product or feature?
Abhishek Dutta
12 replies
Replies
Harold Gary@harold_gary
We usually assess success by metrics such as the click rate, number of downloads, activations, and conversions. For example, we have a software called iBoysoft NTFS for Mac, which allows users to mount Microsoft NTFS-formatted drives in read-write mode. By default, macOS can only read NTFS drives but cannot write to them. iBoysoft NTFS for Mac helps users mount NTFS drives and edit, add, or delete files on them.
👉 https://iboysoft.com/ntfs-for-mac/
👉https://www.producthunt.com/prod...
When the software receives new features or a major update, we track the download rate, activations, and user feedback to ensure it meets users' needs and solves their pain points.
Share
If we are developing a feature or product, we need to have a target audience and expected outcomes. These are measured using product metrics, which are defined during the creation of business requirements. If it’s a feature update, we conduct a comparative analysis of the old versus the new.
But if we are doing something genuinely innovative… we believe in ourselves for a while. And then, we add metrics.
Speech to Note
@e_slyusarchuk That's great. For the final point, you add metrics after initial customer experiences, or stakeholder experiences?
@abhishek_ux Generally, we add metrics as early as possible to ensure nothing is missed and always focus on the customer experience.
It depends on the product or feature, but it seems like the golden rule is to measure how many people use it, and how often they use it. Facebook got a ton of funding early, even with very low revenue, because it had great market capture and many of its users came back to it every day.
Speech to Note
@dan_gower Great example. You need to understand and define metric. For example you can't have same metric as a matrimonial app's KPI. That would be hilarious. 😂
Got married? Keep coming back 😂
Great point though Dan
@abhishek_ux hahaha that example is the perfect counterpoint to the importance of return visits. It's like how Hinge says it's the dating app designed to be deleted.
I measure success by how well it solves the user's problem. Key metrics like adoption rate, user feedback, and impact on the main goal are great indicators.
I know it's successful when users enjoy it and keep coming back for more.
Speech to Note
@nathanielcross Indeed. But in some cases the context will also matter. I just wrote another comment -
"For example you can't have same metric as a matrimonial app's KPI. That would be hilarious. 😂
Got married? Keep coming back 😂"
Success, in my eyes, is when the product solves problems and makes users' daily lives easier.
Speech to Note
@jade_patton Or solves that one critical problem which is part of their life but may not happen day to day.