Feature feedback survey

This template helps you learn whether a feature was found, used, and useful for the task the customer wanted to complete.

Create my feature feedback survey

When to use this template

Send it after real use of the feature. If it just launched, wait until enough people have had a chance to find it and complete the task.

For a broader product view, use the product feedback template.

Ready-to-use questions

1. Were you able to use [feature] to do what you needed?
   • Yes
   • Partly
   • Not yet
2. How did you discover this feature?
3. How easy was it to understand what to do?
4. What helped or got in the way of using it?
5. What result were you hoping to achieve?
6. What would you change about this feature?

How to adapt the questions

Replace [feature] with the name customers see in the product. If the internal name is different, use the interface language.

Ask about the task first and the idea second. A list of requests without context is less useful than a sentence describing what the customer tried to do.

How to read the responses

Separate discovery, understanding, use, and outcome. Low adoption may be a visibility problem rather than a value problem. Strong adoption with weak outcomes may call for a change in the flow or expectations.

The product team feedback guide shows how to turn these patterns into a roadmap decision.

Common mistakes

• Asking whether someone “loved” the new feature.
• Measuring the feature with people who never found it.
• Confusing a requested solution with the underlying problem.
• Drawing a conclusion from a few responses without checking usage.
• Promising a change simply because it appeared in the survey.

Next step

Choose the biggest blocker across discovery, understanding, and completion. Fix one part of the path, measure again, and compare people who had the same experience.

Publish my feature feedback survey