Detractor Recovery and Promoter Innovation Loop
Fix customer defects locally, then test promoter-led ideas for stronger loyalty
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 98%
This loop has two linked phases. First, treat a detractor as a quality defect: contact the customer, understand the root cause, repair what can be repaired, and place the learning with the branch, product, or team that caused the problem. Second, move beyond defect reduction by studying promoters. Ask what made the experience remarkable and what would improve it further, then convert those insights into bounded experiments. Test changes with part of the customer population instead of launching them universally. If an experiment fails to increase enthusiastic scores, repeat purchases, or referrals, stop it. If it reliably creates more tens and loyalty behaviour, roll it out. The method combines local service recovery with promoter-led innovation so the organisation both removes causes of defection and creates new reasons to advocate.
Origin
Reichheld describes the earliest Net Promoter adopters using total-quality thinking to close the loop with detractors. The movement later expanded toward promoter-informed experiments designed to increase delight, referrals, and repeat purchasing.
Core principles
- 01Treat every detractor as evidence of a quality defect
- 02Close the loop at the level where the problem occurred
- 03Promoters reveal what customers find remarkable
- 04Scale only experiments that create loyalty behaviour
How to run it
- 1
Flag the defect
Treat a detractor response as evidence that something in the experience failed. Assign it to the team closest to the interaction.
Pro tip Use the customer's verbatim description as the starting evidence.
Watch out Do not dismiss a low score as merely a survey problem.
- 2
Close the loop
Contact the customer, understand what happened, and repair the relationship where possible. Identify the process or product condition behind the failure.
Pro tip Separate the immediate recovery from the systemic root-cause fix.
Watch out Do not centralise every recovery at headquarters.
- 3
Study remarkable experiences
Ask promoters what they say when referring the organisation and what made them confident enough to recommend it. Translate repeated themes into specific innovation hypotheses.
Pro tip Look for details customers voluntarily repeat to friends.
Watch out Passives often cannot tell you what breakthrough to invent.
- 4
Run a bounded experiment
Expose a limited customer group to one proposed improvement. Measure enthusiastic scores alongside repeat purchases and referrals.
Pro tip Change one meaningful part of the experience at a time.
Watch out Do not roll an unproven idea out to the whole population.
- 5
Kill or scale
Stop changes that do not work and expand those that create many tens and repeat purchases. Continue searching for the next remarkable improvement rather than resting on past strengths.
Pro tip Keep successful baseline practices while testing the next innovation.
Watch out A historically strong NPS does not remove the need to innovate.
In the wild
Amazon made returns easier by letting customers bring an unpackaged item to a UPS Store, avoiding repacking and label printing while issuing credit quickly. Reichheld presents this as the kind of continuing innovation that sustains customer enthusiasm.
→ The return experience removed effort and gave customers another reason to remain loyal.
Common mistakes
Fixing everything at headquarters
Centralising the response prevents the branch or product team that caused the problem from learning directly.
Asking passives to invent the future
Passives often report that they received what they paid for but cannot describe the remarkable innovation needed to create advocacy.
Scaling before testing
A universal rollout makes weak ideas expensive and obscures whether the change actually improved loyalty.
Is it for you?
Best for
It is best for organisations with enough customer interactions to test service or product improvements in bounded groups.
Not ideal for
It is not ideal for teams that collect scores without authority or capacity to repair the underlying experience.
From the transcript
“when I see a detractor, I've I've got a quality problem. I have a defect.”
“let's close the loop with that customer, get to the root cause, fix it, do it at the right level of the organization”
“If it doesn't work, kill it. If it creates a lot of 10s and repeat purchases, roll it out around the world.”
From the episode
Fred Reichheld: Love Your Customers
Fred Reichheld