Watch the short webinar above to learn more about creating a Product Feedback Policy.
- What is a product feedback policy?
- Why is it important?
- What should it cover?
- Where should we publish it?
What is a product feedback policy?
Your product feedback policy governs and lays out the whole process you employ to gather and manage feedback.
If you want to see an example of a product feedback policy, then here is our very own version: Receptive's Product Feedback Policy.
Why is the policy important?
It's important to create a policy as you start using Receptive. Having a policy ensures that everyone (both team members and customers alike) will understand how they can submit feedback, and how their feedback will be managed.
It sets expectations from the start and keeps your organization on track with your feedback process.
Creating a policy is easy and hassle-free, and should take up very little of your time.
What should the policy cover?
Firstly, you need to explain your approach to feedback. State your intentions.
How important is feedback to your organization?
What will you be using it for?
Next, you can explain the general process.
How can people submit their feedback?
What happens to it from there?
How often is it reviewed and who by?
Finally, explain how customers and team members can be kept in the loop.
How can you track the status of the feedback?
Are people told when their feature is released?
Below are some ideas to help you answer the questions...
Your Feedback Approach
You should explain that you take feedback extremely seriously and that it's crucial to your product and as an organization.
Chances are, you'll be using the feedback you collect to figure out the most important additions to the product, based on the priorities of both team members and customers.
The General Process
The way that people can submit feedback depends on how you integrate Receptive with your product.
It could be that you use the in-app widget and so customer and team members can click the button at the side of the screen. Or it might be that they navigate to the help menu within your app and click on a link from there.
Within your policy, it would be wise to send your team members and customers to relevant help docs to show them how Receptive works and how they can use it.
You then need to map out your process for them.
If you follow the guidelines that we establish in the Launchpad series, then your process will look a little something like this:
1) New requests are set to "Awaiting Feedback" while we wait for other users to vote and comment on them.
2) Our product team meets regularly (weekly/biweekly/monthly). In the meetings, we review the highest priorities from customers, team members, and prospects.
3) If we decide to build a feature, the status will be changed to "Planned" or "Building" and we'll aim to give a timeframe of completion on our roadmap.
Kept In The Loop
You should end with a few points about how you'll keep those who submit feedback in the loop.
With Receptive, this is easy. Customers and team members who have submitted (or voted to say they wanted) a feature will automatically be notified if the status of that feature changes.
Mention that you'll try to give an explanation whenever a feature is rejected in order to help them understand your reasoning.
Where should we publish our feedback policy?
We recommend publishing a full, in depth version of your policy on your knowledge base. Then taking relevant sections for your marketing materials, Receptive announcements, blog posts, etc.
And finally, we recommend linking to your policy when moving requests to "Awaiting Feedback" status in Receptive.
Product Feedback Policy Template
You can use this template as the starting point for your own Product Feedback Policy.
Our approach to product feedback
Here at [NAME OF YOUR ORGANIZATION], we take product feedback extremely seriously.
We believe that listening to our customers, team members and prospects - by taking their ideas on board - is a sure-fire way to build a better product.
We use your feedback to identify the most important features, ideas, pain points, and opportunities so that you can get more value from our product as efficiently as possible.
How to give us your product feedback
Submitting your feedback couldn't be simpler.
[DESCRIBE YOUR PROCESS HERE. Include images where appropriate. If you give customers access to Receptive, show an imagine of the link/button or widget you have installed so they know what to look for]
What happens to your product feedback
[Note: this workflow is if you allow your customers to access Receptive]
All new requests are set to the "Awaiting Feedback" status so that more people can vote, prioritize and give us information. This allows is to gauge demand, gather use cases and automatically establish impact & value.
[Every quarter] our Product Teams hold a product feedback meeting. They discuss the highest priorities for our customers, team members and prospects and look at how the requests align with our own strategy.
As the team goes through, they will update the status of each request in Receptive so that you immediately know the outcome.
If we decide to build a feature or make an improvement, the status will change to "Planned" or "Building". It will be added to [our product roadmap which you can view at any time - add link here if appropriate.]
Anyone who has submitted or voted on a specific request will be notified when the status so the request if updated. We will always provide an explanation as to the nature of the status update.
Our product feedback portal always has the most up-to-date information about our products and what we are building next.
If you reach out directly to our Support or Customer Success teams, they'll be able to look up ideas for you, but they won't have any additional information or provide an estimate for when your request will be reviewed.
How long will it be before the product team reviews my idea?
Items will be reviewed by the product specialist on a monthly basis; we take the top requests and update the status where appropriate. Roadmapping meetings occur quarterly. Make sure your ideas are clear and concise so others can vote on it & prioritize. Also be sure to prioritize your own requests too - that way, we will know if a particular requests is important to you.
My request hasn't been reviewed yet and I submitted it 6+ months ago. What can I do?
If we haven't reviewed your item yet and it is a high priority for you:
- Make sure it's at the top of your priority list
- Make sure your request is clear. Why do you need this? What is it stopping you from doing? What is the impact of that? Please add these details in a comment on your idea.
Thank you for your feedback, understanding, and support as we work together to build the best products possible!
Feedback policy examples: