How do you know when a new feature or an update has been successful?

If you are an outcome driven product team (which I hope you are), I think this should be defined as the change in behavior you expect to see/create for users of your new feature or product. Outputs are easy, outcomes are hard. Before you ever start working on the output (e.g. building) you should clearly be able to articulate: What is the problem we are trying to solve What will be the change in user behavior if we solve the problem How will we know we created that change What are the measures w ...Read More

I tend to focus on two groups of indicators. First, did we deliver a delightful user experience that added value to the customer?  My go-to for answering this is Google’s HEART framework: Happiness, Engagement, Adoption, Retention, and Task Success. For Happiness, I look at metrics like user CSAT or NPS. For Engagement, I consider metrics such as average session length. For Adoption, I focus on key activation metrics (e.g., inviting a friend to join, publishing a first post, etc.). For Retention ...Read More

Hopefully, you identified the key success metrics before the launch. These could be your product’s core metrics or specific metrics the launch was intended to influence. Measure them closely and determine whether they are moving in the desired direction. Don't rely solely on quantitative data. Talk to customers and users to understand their experience. If the goal was to expand the product’s feature set, are they actually using the new capabilities? Do they meet user expectations and solve the i ...Read More

True success isn't measured at the moment of impact; it’s measured by sustained impact to core metrics against predicted forecasts, accounting for seasonality. While it is typical to see an initial spike in metrics—especially if the release coincides with a major event or press cycle—the 4–6 week mark is the true test. A successful feature must demonstrate a measurable, lasting lift in one or more of the following areas: Adoption & Active Usage Overall Product MAU or DAU: Does the feature li ...Read More

First, any new feature or update should have pre-defined success criteria/metrics that are set before launch. That helps in objectively assessing the success or failure of the feature/update. The bigger/more requested a feature, the more important it becomes to validate that it was successful with metrics. As a general rule, I don't ascribe to the "launch first and we'll figure out what to measure after" approach as that can lead to measuring vanity metrics instead of user or business outcomes. ...Read More

Key Performance Indicators (KPIs) should be identified for every feature and those should then be monitored to determine the effect of the change. This can be the number of trouble tickets filed if fixing a problem, to the average response time (non-functional change), to the use of a particular feature. Depending on the product, blue/green deployments could be used to determine if user behavior changes such as when adding a new feature to the solution. This is not unique to a mature product per ...Read More

If you haven’t already, it’s helpful to start with the context of the question: “How do you define a mature product?” Finding success with new work on a mature product can feel daunting. It may seem like no update meaningfully moves the needle on churn, adoption, or user conversion. This is often because your target audience is already saturated, and user behavior has become fragmented across a multitude of tools and workflows. Users tend to rely on a small portion of the product’s functionality ...Read More

The best PMs define success before building a feature. To define success, teams should think through: The customer problem they're solving, what does it look like when solved (for the customer and the business)?  How impactful is it if solved (time-saving, cost-saving, revenue-generating)? How does solving this problem help the company achieve its longer-term vision/strategy? Is there a KPI or measure for the feature that helps the team know they're moving toward that strategy? Once the feature ...Read More