NPS Surveys: Why the Score Matters Less Than the Follow-Up Question
Net Promoter Score gets tracked religiously by a lot of businesses we work with, charted on a dashboard, reported to a board — and used to actually change anything far less often. The number alone rarely tells you what to do next. The open-ended follow-up question almost always does.
Why the score alone is nearly useless on its own
A score moving from 42 to 38 tells you something changed. It doesn't tell you what, for whom, or what to do about it. Without the qualitative detail behind the number, an NPS score is a temperature reading with no information about what's causing the fever.
What actually makes NPS useful
- A required, specific follow-up question — "what's the main reason for your score" — read by an actual human, not aggregated away into a word cloud nobody parses.
- Segmenting responses by customer type, since a 6 from your ideal customer profile matters more than a 6 from someone who was never a good fit.
- A closed feedback loop — someone who leaves detailed critical feedback should hear back about what changed as a result, or they'll stop bothering to leave it.
- Tracking trend over time within segments, not just an overall company-wide average that hides what's actually happening in each part of the business.
The number tells you something's worth investigating. The words tell you what to actually go fix.
If your NPS process ends at a dashboard number, the survey is producing data without producing decisions — which is the same trap we describe in customer segmentation done for its own sake, just measured differently.
Talk to us
Have a project in mind? Tell us about it.
Four quick questions and we'll reply within one business day with an honest view on the fastest way to ship it, whether that's our own products, a custom build or an integration.
Start your project
Let’s build something great
Which industry does your business belong to?
Pick the closest match — we'll tailor the rest for you.
Keep reading
Customer Segmentation Without Overengineering It
Three well-chosen, well-understood segments that your team actually acts on beat twelve statistically elegant ones nobody knows what to do with.
Product StrategyFeature Requests: How We Decide What Actually Gets Built
A product that says yes to every reasonable-sounding request ends up serving no one particularly well.
ProcessHow to Brief a Dev Agency So You Actually Get What You Want
The best projects we've ever shipped had one thing in common, and it wasn't a bigger budget — it was a client who could clearly say what "done" looked like.
