Net promoter score: How I’d use NPS as a PM (and when I wouldn’t)
Our reviewers evaluate writing services independently. Learn how we stay transparent, our methodology, and tell us about anything we missed.
NPS is famous, overused, and still useful—if you treat it like a signal, not a religion. Here's how I'd use Net Promoter Score as a PM.
What NPS is
Ask: How likely is it that you would recommend this product to a friend or colleague? (0–10)
- Promoters — 9–10
- Passives — 7–8
- Detractors — 0–6
NPS = % promoters − % detractors (passives count in the denominator of percentages but not in the subtraction numerator).
Simple. That's the appeal.
How I'd measure it
- Sample real users (not only power users who love you)
- Keep the survey short; always allow open-text "why?"
- Segment by plan, tenure, persona, and acquisition channel
- Don't spam it weekly—cadence should match product cycle (often quarterly or event-triggered: after onboarding, after support, after renewal)
Event-triggered NPS often teaches more than a random blast.
Why it can matter
NPS approximates advocacy. Promoters refer; detractors churn and warn others. Trend lines beat absolute "good score" mythology—industry benchmarks vary wildly.
Open-text comments are frequently more valuable than the number. The score tells you that something moved; comments hint at what.
Insights I'd look for
- Are new users more detractory than month-6 users? (onboarding problem)
- Do enterprise accounts score differently than self-serve? (fit / support gap)
- Did a release coincide with a drop? (regression or messaging miss)
- Which themes dominate detractor comments? (prioritization fuel)
Limitations I won't ignore
- It's attitudinal, not behavioral—people say they'd recommend and never do
- Cultural and regional response patterns differ
- Easy to game with survey timing ("ask right after a win")
- One number hides multimodal pain (half love you, half hate a workflow)
- Leadership can fetishize NPS and ignore retention, activation, and revenue quality
I'd never use NPS as the sole north star.
How I'd pair NPS with product work
- Track NPS + retention / expansion for the same cohorts
- Tag comments into a backlog themes list
- Close the loop with detractors when appropriate
- Ship fixes; remeasure the affected segment
NPS is only one signal; I pair it with customer loyalty metrics for product managers to see whether advocacy reflects durable behavior and value.
My take
NPS is a flashlight, not a map. Use it to find where to dig—then dig with behavioral metrics and research.
Building PM judgment on metrics and customer signal? Start with the Product Manager Certification and skim the newsletter for practical notes.
