Every product roadmap has unexpected twists and turns, but customer feedback forms the signposts that can guide you in the right direction.

Every product roadmap has unexpected twists and turns, but customer feedback forms the signposts that can guide you in the right direction. If you understand precisely what your customers are asking for, you can deliver it in a way that delights users and provides value for your company.
Customer feedback offers you a guide for your product development, but you need a process to gather and act on it. With an organized approach to feedback collection, you can prioritize the most impactful changes and turn even negative feedback into actionable steps that take you closer to a consistently valuable and successful product.
Your first step in improving your product is to gather customer feedback from sources across your organization. Customer feedback can come in passively, or you can actively collect it. Feedback can include positive reviews from satisfied customers, customer complaints, new feature requests, bug reports and fixes, and testimonials.
Regardless of the source, it’s helpful to funnel customer suggestions through a single customer feedback tool that’s shared by team members across all departments. A centralized feedback hub creates a shared understanding of the customer experience of your product, and it makes managing and triaging requests easier. It also makes product feedback analysis simpler since you can examine feedback in real time within the same tool.
Passive user feedback is unsolicited. It comes from customers reaching out to your company on their own without you asking for their opinions.
Passive feedback funnels into your company from several channels:
If you don’t have passive feedback channels established, consider adding a few. These are low-lift ways to open up the lines of communication with your customers. Try giving customers a way to leave reviews or star ratings, or start collecting and analyzing data on how your customers use your product.
Active customer feedback is directly solicited. Companies seek out and collect this type of feedback through a directed effort, generally as a way to get answers to specific questions or to gauge overall customer satisfaction.
You have a few options for collecting active feedback:
In each of these methods, you have the chance to talk directly to your customers and ask the questions that you need answers to. You can target your approach around a specific circumstance that you need actionable feedback for, like gathering feedback on a new feature before developing it. Active feedback collection is also a beneficial part of your overall customer feedback strategy. By building in regular touchpoints, you create an open line of communication with your customers where they can share their negative experiences or positive feedback as needed.
The value of customer feedback comes from gaining a deeper understanding of your customers’ pain points and a jumping-off point on how to address them. Each piece of feedback tells you what to consider fixing, adding, removing, or updating on your product in order to meet customer needs.
However, you’re probably not working with the unlimited time and resources you would need to take action on every piece of feedback you receive. You can’t do it all—nor should you. When you decide to address a specific customer request, you’ll end up taking on a new project, getting your product engineering team involved in development, and potentially tapping the product marketing team to come up with a promotion plan or new messaging about your product changes. Weigh your options before making a decision to change your product based on customer opinion.
At UserVoice, we follow the ICE Scoring Model to prioritize customer feedback. We look at:
With limited time and resources available, you won’t be able to address every piece of customer feedback. However, you can focus your efforts on those requests that will have the highest impact on your customer satisfaction and/or strategic business goals.
There are a few ways to figure out which requests are likely to have the most impact:
As much as you may want to deliver exactly what your customers have asked for, some product changes won’t fit with your overall strategy and vision.
Ask yourself if addressing that feedback would align with your strategy and, if so, to what degree. Your answers to those questions can feel a little subjective. However, tackling changes that are misaligned with your strategy can disrupt your long-term product plans while throwing off your other departments’ work as they shift to meet your new changes. One-off updates that don’t align with your product roadmap often aren’t scalable or particularly valuable for your company.
There are times when addressing a specific piece of feedback may be beneficial for turning dissatisfied users into happy customers—and that is a powerful motivator for any customer-focused product manager. However, in these scenarios, avoid giving people exactly what they ask for without evaluating and researching it first.
For example, if you’ve received feedback that your product price doesn’t fit customers’ expectations, carefully consider your guiding strategy before changing your pricing model. If changing your pricing fits with your product and may help you attract new customers, it might be a good idea to tackle it—but it isn’t something to take lightly.
The final piece of the puzzle (and a core part of product management) is coming up with feasible solutions that address customer needs, align with your strategy, and are likely to add value to your product.
Come up with ideas on how to address your customers’ feedback. Then determine your confidence levels for each possible solution. How likely is your idea to solve the problem, and how likely is it to create value for your company and customers? That concept of confidence can be subjective. However, if you’ve collected data as part of your process, you can also determine an objective confidence level in your results.
As a best practice, this step in the process should involve research. You can conduct check-ins with customers to validate your proposed solutions. If the problem you’re addressing is impactful enough on your product, you may want to create a prototype and show it to a handful of customers to gauge their reactions.
Finally, collaborate with product engineering to determine how feasible your proposed solution is. Sometimes, there just isn’t enough time available to devote to a product update, but that doesn’t mean your solution is off the table entirely. Once your engineering team has the bandwidth in their development cycle, they may be able to work on your project.
Turn scattered user data into meaningful customer intelligence, guiding smarter decisions and creating a better product.
Talk to an Expert