NPS Root-Cause Surveying
Ask the score plus 'why' so you fix root causes, not symptoms.
- Difficulty
- Easy
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 83%
Bodnar's most helpful retention practice is a monthly net promoter score survey that pairs the standard 1-10 rating with a mandatory 'please tell us why.' The open-ended answer is where the value lives, because it reveals real sentiment and, crucially, the root cause rather than the symptom. His mental model is that you always want new problems each cycle: fix customer support, and next month you'll hear about product speed or a clunky portal instead. Specific, narrow survey questions tend to surface symptoms; the open NPS question surfaces the big root causes, and AI can now theme the responses fast.
Origin
HubSpot has run a monthly NPS survey with customers for years, learning that the open 'why' field plus theme analysis exposes root causes and keeps problems from becoming systemic.
Core principles
- 01Run a monthly net promoter score survey: rate 1-10, and tell us why.
- 02The 'tell us why' matters more than the score itself.
- 03Open-ended NPS surfaces root causes; specific questions surface only symptoms.
- 04The goal is new problems each cycle, not the same festering, systemic ones.
- 05AI can cluster free-text responses into core themes quickly.
How to run it
- 1
Run NPS on a cadence
Send a net promoter score survey to customers regularly, ideally monthly.
- 2
Pair score with 'why'
Always include the open-ended 'please tell us why' alongside the 1-10 rating.
Pro tip The 'why' matters more than the number itself.
- 3
Theme the responses
Cluster the free-text answers into core themes to see what customers value or dislike.
Pro tip AI can extract the core themes from text responses very quickly.
- 4
Fix root causes, expect new ones
Address the biggest root cause; success looks like hearing about a different, new problem next cycle.
Pro tip Aim for new problems, not the same systemic one recurring.
Watch out Narrow, specific questions surface symptoms without the underlying root cause.
In the wild
Bodnar's example: fix customer support after NPS flags it, and next cycle you'll hear about product speed or a tricky client portal instead.
→ Problems keep changing rather than festering, showing the process surfaces and resolves root causes.
Common mistakes
Dropping the 'why'
A bare score gives a number with no insight into what customers actually value or dislike.
Asking only specific questions
Narrow questions surface symptoms while the true root cause stays hidden.
Is it for you?
Best for
Product and customer-success teams wanting continuous, root-cause-level customer feedback.
Not ideal for
One-off feedback needs or contexts where a specific, targeted question is genuinely what's required.
From the transcript
“The score kind of important. The tell us why is very important... you get a real sentiment as to what people value or like or…”
“When you ask specific questions, you often get the symptoms without the root cause.”
From the episode
Hala Taha: LinkedIn Marketing Strategies for Explosive Business Growth
Hala Taha