3 ms·
I think you bring up a good point. These metrics, formulae, etc. can only be applied when thinking about new features. When building the core product we must re
by palakchokshi 12y ago
I think you bring up a good point. These metrics, formulae, etc. can only be applied when thinking about new features. When building the core product we must rely on our knowledge of the market/users to decide what features end up in v1.0.
It is also prudent to bake in anonymized usage tracking code so you know how users are using your v1.0. This will provide a guideline on what area of the product to concentrate on when thinking about new features. This way we don't end up spending time pushing out features that few will use when our data had showed we should be concentrating on a different area of the product.
- timboslice 12y agoAny reason you suggest anonymized tracking? I like to pass user-id / segment information to my tracking tools so we can get a picture of WHO is using feature X in addition to general adoption rates
- palakchokshi 12y agoWe track user specific actions too but that is more for providing a personalized experience for the user (this is specific to our use case). We notify users of why we are collecting that data. To get an idea of what feature is popular we don't need to know WHO is using it rather HOW MANY are using it and for HOW long? Another reason to do anonymized tracking would be to address any privacy concerns users might have. If someone raises such a concern we have data we can show that says we did not do any user specific tracking. This is specific to our use case and in other cases it might be important to track who is using what feature.
- timboslice 12y agoFair enough, thanks for the response