A previous blog post described a smart way of computing the Net Promoter Score by recoding. The idea was to recode NPS ratings from 0 to 10 into three numeric values: -100 for the *Detractors* (respondents who gave a rating from 0 to 6), 0 for the *Neutrals* (7 or 8) and 100 for the *Promoters* (9 or 10). The NPS was obtained from the average of the recoded ratings. The post briefly mentioned that statistical testing could be conducted on the NPS by treating it as an average, but did go into the details of how or why this is possible. In this blog post I discuss the statistical testing of NPS, and derive expressions for estimating the standard error of NPS.

Statistical testing is essential when analyzing customer feedback data. It allows you to separate signal from noise, and test whether your results are truly meaningful.

## The problem and the solution

Having computed the NPS, it is common to want to determine if it is significant from zero or if it is different from another NPS. But how should this be done? The NPS is computed as a difference between percentages, and while there are lots of statistical tests for comparing percentages, there are none for comparing differences in *correlated percentages *(they are correlated in that if you have more promoters you will likely have less detractors, and vice versa).

Fortunately, it turns out that even though the NPS does not follow a normal distribution, we can test using standard *t*-tests. The use of the *t*-test is valid as NPS approaches normality as the sample size increases (via the central limit theorem) and the *t*-test is highly robust to deviations from normality.

The histogram at the top of this post was generated from 10,000 simulations of a 500 respondent survey in which the probability of a respondent being a Promoter was 40% and the probability of a respondent being a Detractor was 30%. A normal distribution (that was fit to the data) was overlaid on top of the histogram, and it shows how close NPS is to being normally distributed even with a moderately-sized sample.

## Computing *t-*tests

To conduct a *t*-test, the standard error of the NPS first needs to be estimated (see the following sections on how to do this). The* t*-statistic to test if the NPS is significant from (the null hypothesis is ) is

where the degrees of freedom to use in this *t*-test is . To test significance from zero, set . The *t*-statistic for comparing two NPS values (the null hypothesis is ) is

where the degrees of freedom to use in this *t*-test is

where and denote the sample sizes for and respectively.

## Deriving the NPS standard error

Let the total number of respondents be and let the random variables , and denote the number of Detractors, Neutrals and Promoters respectively, so that . The NPS score is calculated using the formula . The standard error of the NPS score is

Using the properties of the variance of random variables, this becomes

(1)

If the probabilities of these respondents being Detractors, Neutrals and Promoters are , and respectively, the vector of random variables follows a *multinomial* distribution. The variance and covariance of such variables are

Plugging this back into (1), we get

(2)

This is an exact formula for the standard error which relies on knowing and . In practice, we do not know the values of these but we can estimate them from the number of Detractors and Promoters:

Using this to replace and in (2), a sample estimate of the standard error is therefore

(3)

## NPS standard error from the average of recoded ratings

Let denote the set of recoded ratings. The NPS can be computed as sample mean . An estimate of the standard error of is

Since

the standard error of becomes

(4)

Comparing (3) and (4), we can see that the two expressions are the same except that in (3) has been replaced with in (4) due to Bessel's correction for bias. In my opinion, (4) is the better formula to use since bias would have been introduced when substituting in and to obtain (3).

Learn how to statistically test Net Promoter Score in Displayr

## Summary

I have shown how to setup *t*-tests for NPS and discussed why this approach is valid. Two ways of estimating the standard error for NPS were derived, where the approach based on averaging recoded ratings was deemed superior. Advanced Net Promoter Score analysis software, like Displayr, run a lot of statistical tests behind the scenes, taking the mathematics off your hands. However, it's always handy to know how your software is operating uner the hood.