CX Methods
NPS as a starting signal, not a verdict
When NPS moves, trigger a diagnosis: which journey, which friction, which fix. The score starts the work; it never finishes it.
A Net Promoter Score tells you sentiment moved. It cannot tell you what changed, where, or why. Companies that profit from NPS run it as the first step of a closed loop that ends in a shipped fix, not as the last slide of a quarterly report.
NPS is a thermometer. It reads the customer's temperature but says nothing about the disease. When the score shifts, something in the experience moved, and the only way to find out what is to investigate: qualitative research to hear the story behind the number, journey diagnostics to locate the friction, root-cause analysis to find what actually broke. Teams that skip the investigation rationalize instead, and a rationalized score is worse than no score, because it feels like knowledge. A good diagnosis names the journey, the stage, and the fix.
Why it matters to the business
Diagnosis pays because journeys link to revenue. McKinsey's journey research found that in industries like insurance and pay TV, a one-point gain on a ten-point journey-satisfaction scale matched at least a three-percentage-point higher revenue-growth rate. You can only capture that by knowing which journey to fix, and the top-line NPS never tells you.
There is also a goodwill cost to asking and doing nothing. Gartner finds only 16 percent of customers strongly believe their feedback drives change, and Qualtrics XM Institute data shows survey response rates have fallen seven to eight percentage points since 2021. Every unanswered survey teaches customers that answering is pointless.
How to use it
- Build the inner loop: someone follows up with detractors within days, not weeks.
- Build the outer loop: recurring root causes get routed to a named product or process owner with a deadline.
- Measure NPS at each major journey stage so you can see exactly where sentiment breaks.
- Pair the score with two or three operational drivers, like first-contact resolution, that teams can move weekly.
- Close the loop visibly: tell customers what changed because of what they said.
Where teams get it wrong
The report becomes the deliverable. The score gets computed, charted, circulated, and discussed, and the process ends there. Nothing routes to an owner, no fix ships, and next quarter the same meeting reviews the same number with fresh speculation about why it moved.
Ask your team
- Show me the last three fixes that started with an NPS movement. What did they cost and what did they return?
- Who owns follow-up with detractors, and what is the response-time standard?
- Which operational metrics do we treat as leading drivers of the score?
NPS is a smoke detector. It was never designed to fight the fire.
Apply this
Reading about nps as a starting signal, not a verdict is one thing. Seeing where it applies in your journey is the useful part.