NPS questions after a feature release

A release is a natural moment to listen. The people who asked for a feature want to know it shipped, and you want to know whether it solved their problem. A short survey to the people who used the new feature answers both, as long as you ask once they have had a chance to try it.

Keep the standard rating question for comparability and put the release into the follow-up. The rating tells you whether the relationship moved; the follow-up tells you whether the feature was the reason.

Questions to ask

Now that you have tried [Feature], how likely are you to recommend [Product] to a friend?
Names the feature so people answer with it in mind, and only goes to people who have actually used it, so you are not asking about something they have never seen.
Did [Feature] solve the problem you had?
A yes or no for the people who requested the feature. A "no" tells you the request and the release did not meet, which a rating on its own would hide.
What about [Feature] did not work for you, or what is still missing?
For detractors and anyone who answered "no". The answers are the first draft of the next iteration, from the people who care most.
What will you be able to do now that you could not do before?
For promoters. The outcome in the user's words, which is better material for your changelog and announcements than a feature list.
Who else on your team should know about [Feature]?
Optional. It spreads the release to colleagues who might need it, through someone who already uses it.

Who should see the survey

Target people who used the new feature at least a few times, starting with those who asked for it or voted for it. Leave out everyone else: a user who has not touched the feature can only rate the product in general, which a relationship survey does better.

Close the loop first

Tell the people who asked for the feature that it shipped before you survey them. The announcement is what turns a request into trust, and a survey that arrives without it feels like a test of whether they noticed.

Then share what you heard and what you will change because of it. People who see their follow-up answers acted on are the ones who answer the next survey.

How the answers are scored

Answers of 9 or 10 count as promoters and answers from 0 to 6 as detractors; the Net Promoter Score is the percentage of promoters minus the percentage of detractors.^{Source [1]} What counts as a good score depends on the industry and the survey method: see thecited NPS benchmarks.

Keep going

Answers to the follow-up question are often feature requests. On afeedback board they are counted with everyone else’s requests, and the people who asked hear when they ship.

Frequently asked questions

When should I survey users after a release?

Once they have used the feature a few times in real work, not on release day. Trigger the survey on use of the feature rather than on a date, so everyone has tried it.

Can a single release change my NPS?

Sometimes for the people who needed it, rarely for everyone. Compare the scores of people who used the feature with those who did not, rather than watching the total.

Should I ask everyone who voted for the feature?

Yes, if they have used it. They have the clearest expectation of what it should do, so their answers tell you best whether the release met the request.

Sources

Bain & Company, “Measuring Your Net Promoter Score”: www.netpromotersystem.com/about/measuring-your-net-promoter-score/, retrieved 2026-10-25.

Net Promoter, NPS and Net Promoter Score are trademarks of Bain & Company, Inc., NICE Systems, Inc. and Fred Reichheld.

Ask these questions with UpVoiced

UpVoiced is adding NPS and CSAT microsurveys to its widget; they are coming soon and not available yet. Its feedback board, roadmap and changelog are in development, and you can try them on a fictional demo.

Check availability Try the fictional demo