from Hacker News

Ask HN: How to you track if newly released features have expected engagement?

by makwarth on 11/4/22, 12:35 PM with 10 comments

When launching new features, how do you track them and how do you measure their "success"?

Do you use a tracking plan, like Segment Protocols? How do you determine when the feature is done (doesn't need more iteration)?

Disclaimer: I'm the founder of a startup that is focused on feature analytics. It's still early days for us, so here to learn about the existing pains in this space.

  • by davikr on 11/4/22, 12:40 PM

    I can't offer any advice, but as an user, I urge for features not to be removed due to a lack of engagement, as was done for Firefox's "compact mode" for some time. I think they might have reversed that change.

  • by jesuscript on 11/4/22, 1:01 PM

    Users will always find edge case bugs and use cases the feature does not fully handle. Feedback will come for free if there is engagement.

    If you hear nothing for a new feature, then no one touches it.

  • by Raed667 on 11/4/22, 12:55 PM

    A/B test: Do users who have the feature enabled get you better KPIs or not.