GUIDE 2026

How to prioritize features using NPS: When I’d use it (and when I wouldn’t)

Josh Fechter
By
Josh Fechter
Josh Fechter
Josh Fechter
Josh Fechter is the co-founder of Product HQ, founder of Technical Writer HQ, and founder and head of product of Squibler. You…
More About Josh →
×

NPS can inform prioritization. It shouldn't be your prioritization system. Here's how I'd use it without cargo-culting.

What NPS is good for

  • Directional loyalty / sentiment trends
  • Segment differences (who loves you vs who tolerates you)
  • Follow-up interviews with detractors and promoters

What I'd never do

  • Rank the roadmap solely by "features mentioned in verbatims"
  • Chase a score for board optics while ignoring retention mechanics
  • Treat a single survey wave as truth

A healthier workflow

  1. Read verbatims by segment
  2. Cluster problems (not feature requests)
  3. Estimate impact on your real product metrics
  4. Validate with discovery / experiments
  5. Re-check NPS as a lagging signal later
Signal Role
NPS + verbatims Problem discovery fuel
Activation / retention Outcome truth
Effort / risk Sequencing reality

NPS® is a registered trademark of Bain & Company / Fred Reichheld / Satmetrix—use the methodology carefully and check current guidance.

Prioritization craft sits at the core of a PM Certification. More analytics-minded notes in the newsletter.

Josh Fechter
Josh Fechter
Josh Fechter is the co-founder of Product HQ, founder of Technical Writer HQ, and founder and head of product of Squibler. You can connect with him on LinkedIn here.