eNPS explained for small teams

eNPS is a single number built from a single question. It is useful, and it is also easy to misread, especially when your whole company fits in one room. This guide covers how to calculate it and how to use it sensibly on a small team.

The question

Employee Net Promoter Score comes from one question: "On a scale of 0 to 10, how likely are you to recommend working here to a friend?" Some teams add "or colleague". The wording matters less than keeping it the same every time.

The calculation

Group the answers into three bands.

• Promoters: 9 or 10.
• Passives: 7 or 8.
• Detractors: 0 to 6.

eNPS is the percentage of promoters minus the percentage of detractors. Passives count in the total but drop out of the subtraction. The result runs from -100 to +100 and is written as a whole number, such as +20 or -15.

A worked example

Say 20 people answer. Seven give a 9 or 10, eight give a 7 or 8, and five give 6 or below.

• Promoters: 7 of 20 = 35%.
• Detractors: 5 of 20 = 25%.
• eNPS = 35 - 25 = +10.

The eight passives do not change the subtraction, but they do dilute both percentages.

Why small teams need extra care

On a team of ten, one person is ten percentage points. One person moving from a 6 to a 7 shifts the score by 10. So a drop from +20 to +10 on a ten-person team can be one person having a bad week. Treat a single reading with suspicion, and look for movement across several surveys.

The same is true for comparison with other companies. Published benchmarks come from big, mixed groups, and they tell you little about a company of fifteen. Compare yourself with yourself.

What to look at besides the number

• The spread. Ten people who all answered 7 or 8 give an eNPS of 0. Five 10s and five 0s also give 0. Those are very different companies. Look at the distribution.
• The average. A plain average of the 0 to 10 answers is steadier than eNPS on a small team, because it does not jump when one person crosses a band boundary.
• The comments. An open question next to the score, such as "what is one thing we should change?", is where the useful information is.

Keep it anonymous

People answer honestly only if they believe it is private. Do not ask for department or tenure on a small team, because those split a group of twenty into pieces of two or three. Hold the results until at least a handful of people have answered. We hide results until three responses and recommend treating anything under eight as sensitive.

How often to ask

Quarterly is enough for most small teams. Monthly is fine if you pair it with a few other pulse questions. Whatever the cadence, ask at similar times each cycle so you are not comparing a quiet month with a deadline crunch.

What to do with a bad score

Do not defend, and do not search for who gave the low scores. Share the result with the team as it is. Pick one or two themes from the comments and say what you will change. Then do it, and mention it the next time you ask. Over a few rounds, what people see you do will matter more than the number.

What to do with a good score

Say thank you, and still read the comments. A company at +40 usually has a few people quietly frustrated about something specific, and a good score can hide them.

A fair summary

eNPS is a conversation starter. It is a rough thermometer that works best when you read it over time, next to words from the same people. It does not tell you why people feel the way they do, and it should not be used to evaluate a manager on its own.

For question ideas to pair with it, see our pulse survey questions.

Reporting it to the team

Share three things: the score, the spread, and what you plan to do. For example: "Our eNPS is +10. Most people answered 7 or 8, a few gave low scores, and the comments pointed to unclear priorities. This month we will write the priorities down on one page and review them every Monday." It takes two minutes to say, and it shows you read the comments.

Avoid explaining away the result. If the number is lower than you hoped, say so without apology or excuses.