A single-question metric measuring customer loyalty: 'How likely are you to recommend this product to a friend?' Widely used in business but not a direct measure of user experience.
Definition: A single-question metric measuring customer loyalty: 'How likely are you to recommend this product to a friend?' Widely used in business but not a direct measure of user experience.
The Net Promoter Score (NPS), introduced by Frederick Reichheld in 2003, measures customer loyalty with a single question: "How likely are you to recommend this product/company to a friend or colleague?" on a scale of 0 to 10.
Respondents are grouped into three categories:
NPS = % Promoters − % Detractors
The score ranges from -100 to +100.
NPS measures overall customer loyalty and sentiment toward a brand or product. It is widely valued by business leaders because it is simple and correlates with growth.
However, NPS is not a UX metric. It does not diagnose specific usability issues and can be influenced by factors outside the product interface—price, brand perception, customer service, competitor behavior.
Always pair NPS with follow-up questions ("Why did you give that score?") to understand the reasons behind the number. The score is the "what"; the follow-up is the "why."
The outermost layer of experience, encompassing every touchpoint a customer has with a company—from marketing and sales to product use and support. Broader than UX, which focuses on product interaction.
A Core Method of asking at scale using standardized questions. Enables data collection from larger samples but sacrifices the depth of interviews for breadth and standardization.
This term is referenced in the following articles:
An interactive tool that guides you to the right research method based on your goals, constraints, and context.
Standardized measurement instruments provide benchmarks and comparability. But using them effectively requires understanding what each one actually measures, and what it does not.
One of the most common points of friction is not about budget or methods, it is about timing. Your core job is to reframe research from a single, disruptive event into a continuous, value-adding loop.
How to prove your redesign actually worked. A guide to establishing baselines, tracking metrics (SUS), and calculating ROI.
Don't wait for the beta. The 3 critical moments to test: Concept (Generative), Prototype (Formative), and Live (Summative).