{"id":2523,"date":"2020-07-01T09:00:39","date_gmt":"2020-07-01T13:00:39","guid":{"rendered":"http:\/\/blog3.canny.io\/wordpress\/?p=2523"},"modified":"2026-03-10T21:04:47","modified_gmt":"2026-03-11T01:04:47","slug":"understanding-customer-feedback-why-it-matters-who-is-saying-what","status":"publish","type":"post","link":"https:\/\/canny.io\/blog\/understanding-customer-feedback-why-it-matters-who-is-saying-what\/","title":{"rendered":"Understanding customer feedback: why it matters who is saying what"},"content":{"rendered":"<p>It\u2019s important to keep track of what your customers are saying about your product. All the feedback you get matters.<\/p>\n<p>But the reality is, when you\u2019re choosing what to build, the feedback you get from some customers might matter <em>more.<\/em><\/p>\n<h2>The key to understanding customer feedback? Knowing which customers are giving it<\/h2>\n<p>All your customers are important.<\/p>\n<p>But when it comes to choosing what to change or build, not all customer feedback holds the same weight.<\/p>\n<p>An important part of understanding customer feedback is knowing who is saying what. Not all of your users use your product to the same degree.<\/p>\n<p>Some might have used it once or twice. Others use it daily. And, it\u2019s likely that some customer segments are more critical to the success of your business than others. They might pay more. They might represent an important industry you\u2019re trying to appeal to. They might be a loyal, long-standing customer that\u2019s been with your business from the beginning.<\/p>\n<h3>Here&#8217;s an example:<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2546\" src=\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/customer-profiles-understanding-customer-feedback.jpg\" alt=\"understanding customer feedback is easier if you know where it's coming from\" width=\"1628\" height=\"915\" srcset=\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/customer-profiles-understanding-customer-feedback.jpg 1628w, https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/customer-profiles-understanding-customer-feedback-300x169.jpg 300w, https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/customer-profiles-understanding-customer-feedback-768x432.jpg 768w, https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/customer-profiles-understanding-customer-feedback-210x118.jpg 210w\" sizes=\"auto, (max-width: 1628px) 100vw, 1628px\" \/><\/p>\n<p>Both of these customers matter. Providing great support and listening to both of them is important.<\/p>\n<p>But, if each customer requested a feature, <a href=\"https:\/\/canny.io\/blog\/roadmap-prioritization-guide\/\" target=\"_blank\" rel=\"noopener noreferrer\">which would you want to prioritize?<\/a><\/p>\n<p>The trouble is, <strong>if you don\u2019t know where your feature requests are coming from, you can\u2019t prioritize effectively.<\/strong> Without visibility into who is asking for what, you won\u2019t be able to know which feature requests are coming from which customer segments.<\/p>\n<p>To put it bluntly, you\u2019re working blind. It\u2019s impossible to prioritize what to build next based on how much value it brings to the customers that have the biggest impact on your business.<\/p>\n<p>Here\u2019s a deeper dive into why this is important.<\/p>\n<h2>You\u2019ll get insight into which customers want what<\/h2>\n<p>You want to build the features your ideal customers most want.<\/p>\n<h3>When you get a feature request, is it coming from:<\/h3>\n<ul>\n<li>Your biggest customers?<\/li>\n<li>A customer segment you want to attract more of?<\/li>\n<li>Smaller customers that you <em>care<\/em> about, but who might not be willing to pay for additional features?<\/li>\n<li>A customer segment that you\u2019re not especially interested in attracting more of in the future?<\/li>\n<\/ul>\n<p>You might prioritize different segments at different times. Sometimes, it\u2019s more important to build something your biggest customers want. Or, maybe you\u2019re looking to attract more of a specific type of customer, and you\u2019ll be able to do that better if you build a certain feature.<\/p>\n<p>But without knowing who wants what, you can\u2019t make informed decisions around product. You can\u2019t make decisions with specific customer segments in mind.<\/p>\n<p><!--HubSpot Call-to-Action Code --><span id=\"hs-cta-wrapper-e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa\" class=\"hs-cta-wrapper\"><span id=\"hs-cta-e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa\" class=\"hs-cta-node hs-cta-e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa\"><!-- [if lte IE 8]>\n\n\n<div id=\"hs-cta-ie-element\"><\/div>\n\n\n<![endif]--><a href=\"https:\/\/cta-redirect.hubspot.com\/cta\/redirect\/5705808\/e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" id=\"hs-cta-img-e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa\" class=\"hs-cta-img aligncenter\" style=\"border-width: 0px;\" src=\"https:\/\/no-cache.hubspot.com\/cta\/default\/5705808\/e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa.png\" alt=\"Canny free trial\" width=\"1300\" height=\"642\" \/><\/a><\/span><script charset=\"utf-8\" src=\"https:\/\/js.hscta.net\/cta\/current.js\"><\/script><script type=\"text\/javascript\"> hbspt.cta.load(5705808, 'e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa', {\"region\":\"na1\"}); <\/script><\/span><!-- end HubSpot Call-to-Action Code --><\/p>\n<h2>You can prioritize features that will actually drive revenue<\/h2>\n<p>Some features are \u201cnice-to-haves.\u201d Others are going to drive revenue.<\/p>\n<p>Okay, so it\u2019s not always that black and white.<\/p>\n<h3>But before you build something new, it\u2019s important to ask:<\/h3>\n<ul>\n<li>Is this feature going to attract new paying customers?<\/li>\n<li>Is this something that will add value to existing customers?<\/li>\n<li>Is this something that you\u2019ll charge existing customers more for?\n<ul>\n<li>And if so: Are the customers who are requesting a certain feature <em>actually<\/em> going to pay for it?<\/li>\n<\/ul>\n<\/li>\n<li>Does this new feature earn you an update to your pricing structure?<\/li>\n<\/ul>\n<p>If you know who is asking for what, you can get a better sense of if it will actually bring in money.<\/p>\n<p>You&#8217;ll have visibility on pricing for customers requesting a feature. You can reach out directly and ask if they&#8217;d pay for a new feature. You\u2019ll be able to make, at the very least, some educated guesses.<\/p>\n<p>Otherwise, you might build a bunch of things that are nice to have, but won&#8217;t actually drive revenue.<\/p>\n<h2>You can follow up and get clarification<\/h2>\n<p>Understanding customer feedback is also about making sure you see the entire picture. If you know who is asking for what, you can follow up and get more details.<\/p>\n<p>We recently covered why it\u2019s important to <a href=\"https:\/\/canny.io\/blog\/how-to-ask-the-right-customer-feedback-questions\/\" target=\"_blank\" rel=\"noopener noreferrer\">ask the right customer feedback questions<\/a>, so check out that article too.<\/p>\n<div class=\"callout\">\n<p><strong>The short version is:<\/strong><\/p>\n<p>If you don\u2019t ask for details about the feedback you get, you\u2019re missing out on important context.<\/p>\n<p>You might misinterpret a request, and build something that doesn\u2019t really solve the problem.<\/p>\n<\/div>\n<p>This is one reason anonymous feedback isn\u2019t very helpful: you can\u2019t get clarification.<\/p>\n<p>At Canny, we use Canny Identify to connect feedback with a user. When users leave feedback, it\u2019s tied to their existing user account.<\/p>\n<p>So, for example, <a href=\"https:\/\/feedback.canny.io\/\" target=\"_blank\" rel=\"noopener noreferrer\">we use Canny to track feature requests from users<\/a>\u00a0(as well as share our roadmap and changelog).<\/p>\n<p>Requests and comments are tied to specific user profiles. So, we can <a href=\"https:\/\/canny.io\/blog\/ask-for-feedback-saas\/\" data-wpil-monitor-id=\"12\">ask clarifying questions that help us better understand customer feedback<\/a>.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"border size-full wp-image-2454 aligncenter\" src=\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/Screen-Shot-2020-06-01-at-11.52.24-AM-1-e1591037864631.png\" alt=\"\" width=\"816\" height=\"222\" srcset=\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/Screen-Shot-2020-06-01-at-11.52.24-AM-1-e1591037864631.png 816w, https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/Screen-Shot-2020-06-01-at-11.52.24-AM-1-e1591037864631-300x82.png 300w, https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/Screen-Shot-2020-06-01-at-11.52.24-AM-1-e1591037864631-768x209.png 768w, https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/06\/Screen-Shot-2020-06-01-at-11.52.24-AM-1-e1591037864631-210x57.png 210w\" sizes=\"auto, (max-width: 816px) 100vw, 816px\" \/><\/p>\n<p style=\"text-align: center;\"><em>An example of a follow-up question based on a request from a Canny user.<\/em><\/p>\n<p>You can read more about why this is important in <a href=\"https:\/\/help.canny.io\/en\/articles\/10517751-why-should-i-authenticate-my-users-to-give-feedback\" target=\"_blank\" rel=\"noopener noreferrer\">our help center article on authenticating users<\/a>, and <a href=\"https:\/\/developers.canny.io\/install\" target=\"_blank\" rel=\"noopener noreferrer\">learn more about Canny Identify here<\/a>.<\/p>\n<h2>You can find (and collaborate with) beta testers<\/h2>\n<p>If someone has been requesting a feature or integration with your product, they\u2019re interested in it. This means they\u2019re probably willing to test it out if you build it.<\/p>\n<p>But, if you don\u2019t know who is asking for what, you won\u2019t know who to reach out to once your beta is ready.<\/p>\n<p>If you know which users have requested something, you can reach out to them directly and <a href=\"https:\/\/canny.io\/blog\/beta-testing-with-user-base\/\" target=\"_blank\" rel=\"noopener noreferrer\">ask if they\u2019d be interested in beta testing<\/a>.<\/p>\n<p>If you\u2019re using a tool like Canny, you can also take it one step further and give beta users a private space to leave feedback, by <a href=\"https:\/\/canny.io\/blog\/using-canny-privately\/\" target=\"_blank\" rel=\"noopener noreferrer\">using a private feedback board<\/a>.<\/p>\n<h2>You can personalize release announcements and updates<\/h2>\n<p>If a specific customer requested a feature, they\u2019ll be thrilled if you build it.<\/p>\n<p>If you know who asked for what, you can <a href=\"https:\/\/canny.io\/blog\/announce-product-updates-features\/\" target=\"_blank\" rel=\"noopener noreferrer\">reach out to them personally with product releases and updates<\/a>. You can let them know you took their input, and actually built the thing they asked for.<\/p>\n<p>This is huge\u2014both in terms of the practical benefit your customers get from your tool, and for building loyalty.<\/p>\n<p>It <a href=\"https:\/\/canny.io\/blog\/should-you-use-a-changelog-tool\/\" target=\"_blank\" rel=\"noopener noreferrer\">closes the feedback loop<\/a>. You can directly connect with users and show that you took their requests seriously.<\/p>\n<h2>It&#8217;s easier to understand where customer feedback is coming from with the right tools<\/h2>\n<p>If you aren\u2019t currently using a customer feedback tool like Canny, it\u2019s worth noting that it will make the process of understanding customer feedback a whole lot easier.<\/p>\n<p>And, you\u2019ll be able to automatically update users who submitted or voted on a request. They\u2019ll be looped in throughout the entire process. So it\u2019s just that much easier to keep your customers up to date with product changes.<\/p>\n<p>You can check out our article on <a href=\"https:\/\/canny.io\/blog\/need-a-product-feedback-tool\/\" target=\"_blank\" rel=\"noopener noreferrer\">deciding if a feedback tool is right for you<\/a> if you\u2019re still on the fence. Our own <a href=\"https:\/\/feedback.canny.io\/\" target=\"_blank\" rel=\"noopener noreferrer\">Canny feedback board<\/a> is also a great way to see Canny in action. And, you can also <a href=\"https:\/\/canny.io\/register\" target=\"_blank\" rel=\"noopener noreferrer\">try Canny free for 14 days<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The key to understanding customer feedback? Knowing which customers are giving it. Here&#8217;s why it&#8217;s important to track where your feedback is coming from.<\/p>\n","protected":false},"author":10,"featured_media":6357,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[8],"tags":[],"class_list":["post-2523","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customer-feedback"],"aioseo_notices":[],"modified_by":"Eric Hoppe","_links":{"self":[{"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/posts\/2523","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/comments?post=2523"}],"version-history":[{"count":25,"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/posts\/2523\/revisions"}],"predecessor-version":[{"id":10681,"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/posts\/2523\/revisions\/10681"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/media\/6357"}],"wp:attachment":[{"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/media?parent=2523"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/categories?post=2523"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/canny.io\/blog\/wp-json\/wp\/v2\/tags?post=2523"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}