Product managers must select a balanced set of indicators for successful product iteration and growth in an agile environment, as a single number rarely tells the whole story. According to Scrum.org, product metrics are indicators that assess the customer and business value a product delivers, offering insights from users and the market. The most effective approach involves choosing metrics that map to distinct use cases, such as understanding customer value, measuring business impact, or ensuring team effectiveness.

Metrics are grouped by their primary strategic purpose—assessing customer value, measuring business impact, or evaluating team health. This grouping helps product managers select the right indicators for their specific context.

1. For Measuring Customer-Centricity

Customer-centricity metrics provide direct feedback on user perception and interaction, fundamental to iterative development. They confirm whether the product is solving the right problem for the right audience.

Customer Satisfaction (CSAT)This metric directly measures user sentiment and their perceived value of the product. According to Scrum.org, customer satisfaction is a key metric for evaluating customer-centricity. It is typically captured through surveys that ask users to rate their satisfaction with a product or a specific interaction on a numerical scale. From a user-centric perspective, CSAT provides a clear signal on whether recent changes have improved or degraded the user experience. It serves as a crucial feedback loop in an agile cycle, allowing teams to quickly validate their hypotheses about user needs.

  • Key Data: Often measured on a 1-5 or 1-10 scale, the final score is usually presented as the percentage of "satisfied" or "very satisfied" respondents.
  • Limitation: Satisfaction can be subjective and influenced by factors outside the product itself, such as customer support interactions or pricing. According to a report from Medium, one of the common pitfalls of metrics is overemphasizing objective data, and CSAT scores must be paired with qualitative feedback to be truly actionable.

Customer UsageWhile satisfaction reveals how users feel, usage data shows what they do. Scrum.org also lists customer usage as a core customer-centricity metric. Tracking metrics like daily active users (DAU), feature adoption rates, and session duration provides objective, behavioral insights. In an agile context, these metrics can validate whether a newly shipped feature is being discovered and used as intended. A sudden drop or spike in usage can act as a leading indicator that warrants further investigation, aligning with the principle that a metric should signal a pattern change, as noted by Age-of-Product.com.