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 ...

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 H...

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 o...

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...

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 ...

When defining a new feature or change, also define what your anticipated impact will be to the customer and OKRs. This should be part of your prioritization framework in ...

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...

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 s...