Net Promoter Score (NPS)
A metric that measures customer loyalty by asking how likely users are to recommend a product on a scale of 0-10.
How NPS Works
Net Promoter Score is calculated from a single survey question: “On a scale of 0 to 10, how likely are you to recommend this product to a friend or colleague?” Based on their response, users fall into one of three categories. Promoters (9-10) are enthusiastic advocates who are likely to drive referrals. Passives (7-8) are satisfied but not excited, making them vulnerable to competitors. Detractors (0-6) are unhappy users who may discourage others from trying the product.
The NPS is computed by subtracting the percentage of detractors from the percentage of promoters, yielding a score between negative one hundred and positive one hundred. A positive score means more promoters than detractors, and scores above fifty are generally considered excellent. Many teams supplement the numeric rating with an open-ended follow-up question, such as “What is the primary reason for your score?” to capture qualitative context that feeds into the broader feedback loop.
Why NPS Matters for Product Teams
NPS provides a standardized, easy-to-track indicator of overall user sentiment. Because the question is the same across industries, teams can benchmark their score against competitors and track changes over time. A rising NPS after a product update signals that the changes resonated with users; a falling score is an early warning that something needs attention.
During beta testing, NPS is especially useful as a summary metric that complements more granular beta testing metrics like bug counts, session length, and task completion rates. Surveying beta testers at the start and end of a testing cycle reveals whether the iteration improved perceived quality. The results often surface feature requests and pain points that quantitative analytics alone might miss.
Best Practices for Using NPS
Time your surveys thoughtfully. Sending an NPS survey immediately after a user encounters a frustrating bug will skew results negatively, while surveying right after a delightful moment will skew them positively. Aim for a neutral touchpoint, such as after the user has had enough time to form a genuine opinion of the product.
Segment your results. Breaking NPS down by user cohort, platform, or feature usage reveals which groups are most and least satisfied. This segmentation helps product teams direct improvement efforts where they will have the greatest impact and informs how you prioritize incoming feature requests.
Act on the data. An NPS program that collects scores but never closes the loop will lose credibility with users. Follow up with detractors to understand their frustrations, thank promoters for their advocacy, and communicate what changes you are making based on the feedback. The guide on giving product feedback offers useful framing from the user’s perspective.