{"id":78087,"date":"2022-04-08T15:41:32","date_gmt":"2022-04-08T14:41:32","guid":{"rendered":"https:\/\/www.prodpad.com\/?p=78087"},"modified":"2025-01-13T16:25:53","modified_gmt":"2025-01-13T16:25:53","slug":"solving-customer-problems","status":"publish","type":"post","link":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/","title":{"rendered":"Solving Customer Problems, Not Feature Requests"},"content":{"rendered":"\n<p>So often, as product managers, it can feel as though customer complaints are thrown over the wall to us in the form of unvetted <a href=\"https:\/\/www.prodpad.com\/blog\/dont-take-every-feature-request-seriously\/\">feature requests<\/a> and other prescriptive solutions. It\u2019s annoying. And it\u2019s also our job to help the customer support team understand how to pass on user feedback in a helpful way.<\/p>\n\n\n\n<p>In this post, we\u2019ll cover why support and product should work together, how to train support to collect and evaluate user feedback, and finally how to set up a solid feedback process between the two teams.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large is-resized\"><img decoding=\"async\" src=\"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2-1024x402.png\" alt=\"A Product Manager should solve customer problems\" class=\"wp-image-78091\" width=\"650\" srcset=\"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2-1024x402.png 1024w, https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2-300x118.png 300w, https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2-768x301.png 768w, https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2-1536x602.png 1536w, https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2.png 1882w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n\n<h2 class=\"wp-block-heading\" id=\"h-why-support-and-product-must-work-together-to-solve-customer-problems\">Why support and product must work together to solve customer problems<\/h2>\n\n\n\n<p><a href=\"https:\/\/www.prodpad.com\/blog\/working-with-customer-support\/\">Customer support<\/a> people are problem solvers, no doubt about it. Their job is to field complaints or difficulties, user mistakes and software malfunctions. And they\u2019re incentivized to solve the problems as quickly as possible, usually under a certain time period: two hours, 24 hours, etc. Closing tickets and customer satisfaction are critical to customer support\u2019s performance metrics.<\/p>\n\n\n\n<p>But what about the customer problems that can\u2019t be solved on the spot? Then product management gets involved.<\/p>\n\n\n\n<p>Indeed, these problems might require a longer term (i.e. more comprehensive or more foundational) solution, perhaps something built by the development team. Once a solution is in place, the support team doesn\u2019t need to field complaints about it anymore.<\/p>\n\n\n\n<p>So, reporting and\/or handing over such customer problems from support to product is clearly an important link. A strong feedback loop between these teams can better the product, improve user satisfaction, and increase support efficiency \u2013 impacting all the juicy company KPIs that are attached to those.<\/p>\n\n\n\n<p>The key is to get this hand-off right!&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to train customer support to collect feedback for product<\/h2>\n\n\n\n<p>To be fair, it\u2019s not the support team&#8217;s day job to collect and interpret feedback so much. And we\u2019re not trying to put more on their plate. Quite the opposite. We\u2019re trying to get to the root of issues, so their job is easier! (It just so happens this makes our job easier, too.)<\/p>\n\n\n\n<p>We can get there by reframing questions and using new techniques. The tenets of this training are to help the customer support team to:<\/p>\n\n\n\n<div class=\"callout content-dark\" style=\"background-color:#eeeeee\">\n<ul class=\"wp-block-list\"><li>Understand \u201cthe why\u201d: how to see customer problems holistically<\/li><li>Focus on problems, not features: how to define core issues and needs<\/li><li>Use good feedback channels: how to communicate it to product<\/li><\/ul>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Understand \u201cthe why\u201d: how to see customer problems holistically<\/h2>\n\n\n\n<p>When it comes to understanding customer feedback, product teams love the 5 Whys method. (In fact, I\u2019ve even used it <a href=\"https:\/\/www.prodpad.com\/blog\/customer-feedback-product-process-1\/\">with my own dad<\/a>!) It\u2019s a simple one to pass on to the support team.<\/p>\n\n\n\n<p>The method approaches feedback and requests with an iterative round of questioning \u2013 and that question is always simply, \u201cWhy?\u201d With each answer you receive, follow up by asking \u201cWhy?\u201d again, and you\u2019ll peel back the layers of what the customer actually needs.<\/p>\n\n\n\n<div class=\"callout content-dark\" style=\"background-color:#eeeeee\">\n<p><strong>By digging to the root of the problem like this, three great things happen:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>The solution can end up loads easier than whatever request or idea the customer originally had. That means faster, simpler, more elegant fixes.<\/li><li>The product team doesn\u2019t need to doubleback to the customer for more information and repeat the conversation.<\/li><li>The customer ends up feeling really listened to, because you\u2019ve engaged them about their problem and they\u2019re involved in the discussion.<\/li><\/ol>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Focus on problems, not features: how to define core issues<\/h2>\n\n\n\n<p>Once we\u2019ve reached the core problem, let\u2019s stay there! Let\u2019s not wander into solution territory or hypothesize how some features could be tweaked to do this or that. We don\u2019t need feature requests, we need well-defined problems.<\/p>\n\n\n\n<p>One way to help non-product people understand this concept is to give real life examples. Specifically, give them examples of when a product feature request has led to something being built that <em>wasn&#8217;t<\/em> the requested feature, but that <em>did <\/em>solve the underlying problem and in a better way.<\/p>\n\n\n\n<p>Some well-known quotes out there demonstrate this well. And although the quotes might be historically incorrect, their messages still ring true!<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>\u201cIf I had asked people what they wanted, they would have said faster horses.\u201d<\/p><cite>Henry Ford (There\u2019s no evidence he actually said this, but it\u2019s a product management maxim at this point.)<\/cite><\/blockquote>\n\n\n\n<p>and<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>\u201cThe electric light did not come from the continuous improvement of candles.&#8221;<\/p><cite>Oren Harari<\/cite><\/blockquote>\n\n\n\n<p>Once the support or success teams get the importance of staying problem-focused, you can give them convenient ways to transfer this customer feedback to the product team.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Use good feedback channels: how to communicate it to product<\/h2>\n\n\n\n<p>The final step is to make this collaboration as easy and seamless as possible.<\/p>\n\n\n\n<p>Product people know that the best practice for collecting customer feedback is to offer loads of ways for those customers to actually submit it. There should be an option in the app, on your website, via email, through Slack or social media, etc. If your team is new or just getting started with collecting feedback, have a look at <a href=\"https:\/\/www.prodpad.com\/blog\/product-feedback-process\/\">how to set up a customer feedback process<\/a>.<\/p>\n\n\n\n<p>The same applies to getting feedback from customer support to the product team. Set up several feedback channels for non-product folks to send over the information. The easier it is to share, the more feedback you\u2019ll get. And chances are it will be better quality!<\/p>\n\n\n\n<p>You can use a special email address, a Slack channel, a Typeform, an old-school shoebox with written notes inside. Provide a short template for a \u201cproblem-focused\u201d report, so the support rep only needs to fill in the blanks.<\/p>\n\n\n\n<p>Of course, it\u2019s best to automate this step as much as possible. That\u2019s exactly what we\u2019ve done with ProdPad.<\/p>\n\n\n\n<p>Within the tool, we have a <a href=\"https:\/\/www.prodpad.com\/integrations\/chrome-extension\/\">Chrome extension<\/a>, which means that people from Success can quickly write some feedback from their browser. There\u2019s also a <a href=\"https:\/\/www.prodpad.com\/features\/customer-feedback\/customer-feedback-portal\/\">customer feedback portal<\/a> where the support or success teams could add feedback on behalf of a customer.<\/p>\n\n\n\n<p>Essentially, ProdPad is a tool that helps automate the feedback collection process, and then helps product teams manage the <a href=\"https:\/\/www.prodpad.com\/features\/customer-feedback\/\">feedback<\/a> through well-designed <a href=\"https:\/\/www.prodpad.com\/features\/ideas\/\">backlogs<\/a> and <a href=\"https:\/\/www.prodpad.com\/features\/roadmaps\/\">roadmaps<\/a>. To check it out, you can <a href=\"https:\/\/app.prodpad.com\/signup\">sign up for a free trial<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>So often, as product managers, it can feel as though customer complaints are thrown over the wall to us in the form of unvetted feature requests and other prescriptive solutions.&hellip;<\/p>\n","protected":false},"author":21,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[6],"tags":[],"pp_uni_tag":[],"class_list":["post-78087","post","type-post","status-publish","format-standard","hentry","category-customer-success"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.4 (Yoast SEO v27.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Solving Customer Problems, Not Feature Requests | ProdPad<\/title>\n<meta name=\"description\" content=\"In this post, we cover solving customer problems, why support and product should work together, and how to collect and evaluate user feedback.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Solving Customer Problems, Not Feature Requests | ProdPad\" \/>\n<meta property=\"og:description\" content=\"So often, as product managers, it can feel as though customer complaints are thrown over the wall to us in the form of unvetted feature requests and other\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/\" \/>\n<meta property=\"og:site_name\" content=\"ProdPad\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/ProdPad\/\" \/>\n<meta property=\"article:published_time\" content=\"2022-04-08T14:41:32+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-01-13T16:25:53+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-Not-Feature-Requests-Blog-Image.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2040\" \/>\n\t<meta property=\"og:image:height\" content=\"1100\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Liz Love\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@prodpad\" \/>\n<meta name=\"twitter:site\" content=\"@prodpad\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Liz Love\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Solving Customer Problems, Not Feature Requests | ProdPad","description":"In this post, we cover solving customer problems, why support and product should work together, and how to collect and evaluate user feedback.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/","og_locale":"en_US","og_type":"article","og_title":"Solving Customer Problems, Not Feature Requests | ProdPad","og_description":"So often, as product managers, it can feel as though customer complaints are thrown over the wall to us in the form of unvetted feature requests and other","og_url":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/","og_site_name":"ProdPad","article_publisher":"https:\/\/www.facebook.com\/ProdPad\/","article_published_time":"2022-04-08T14:41:32+00:00","article_modified_time":"2025-01-13T16:25:53+00:00","og_image":[{"width":2040,"height":1100,"url":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-Not-Feature-Requests-Blog-Image.jpg","type":"image\/jpeg"}],"author":"Liz Love","twitter_card":"summary_large_image","twitter_creator":"@prodpad","twitter_site":"@prodpad","twitter_misc":{"Written by":"Liz Love","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#article","isPartOf":{"@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/"},"author":{"name":"Liz Love","@id":"https:\/\/www.prodpad.com\/#\/schema\/person\/2b3f20b7950b0cb2316c0beb3bf212ef"},"headline":"Solving Customer Problems, Not Feature Requests","datePublished":"2022-04-08T14:41:32+00:00","dateModified":"2025-01-13T16:25:53+00:00","mainEntityOfPage":{"@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/"},"wordCount":1047,"commentCount":0,"publisher":{"@id":"https:\/\/www.prodpad.com\/#organization"},"image":{"@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#primaryimage"},"thumbnailUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2-1024x402.png","articleSection":["Customer Success"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/","url":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/","name":"Solving Customer Problems, Not Feature Requests | ProdPad","isPartOf":{"@id":"https:\/\/www.prodpad.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#primaryimage"},"image":{"@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#primaryimage"},"thumbnailUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2-1024x402.png","datePublished":"2022-04-08T14:41:32+00:00","dateModified":"2025-01-13T16:25:53+00:00","description":"In this post, we cover solving customer problems, why support and product should work together, and how to collect and evaluate user feedback.","breadcrumb":{"@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#primaryimage","url":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2.png","contentUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2022\/04\/Solving-Customer-Problems-not-feature-requests-2.png","width":1882,"height":738},{"@type":"BreadcrumbList","@id":"https:\/\/www.prodpad.com\/blog\/solving-customer-problems\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Latest Blogs","item":"https:\/\/www.prodpad.com\/blog\/category\/latest-blogs\/"},{"@type":"ListItem","position":2,"name":"Customer Success","item":"https:\/\/www.prodpad.com\/blog\/category\/latest-blogs\/customer-success\/"},{"@type":"ListItem","position":3,"name":"Solving Customer Problems, Not Feature Requests"}]},{"@type":"WebSite","@id":"https:\/\/www.prodpad.com\/#website","url":"https:\/\/www.prodpad.com\/","name":"ProdPad","description":"Product Management Software","publisher":{"@id":"https:\/\/www.prodpad.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.prodpad.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.prodpad.com\/#organization","name":"ProdPad","url":"https:\/\/www.prodpad.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.prodpad.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2018\/12\/blue-full.png","contentUrl":"https:\/\/www.prodpad.com\/wp-content\/uploads\/2018\/12\/blue-full.png","width":2050,"height":400,"caption":"ProdPad"},"image":{"@id":"https:\/\/www.prodpad.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/ProdPad\/","https:\/\/x.com\/prodpad","https:\/\/instagram.com\/prodpad","https:\/\/www.linkedin.com\/company\/prodpad\/","https:\/\/www.youtube.com\/channel\/UCXHOx5Ed-6sHPujypIlhdMA"]},{"@type":"Person","@id":"https:\/\/www.prodpad.com\/#\/schema\/person\/2b3f20b7950b0cb2316c0beb3bf212ef","name":"Liz Love","description":"Liz Love is our Chief Commercial Officer. Having worked in software development since 2001, including 10 years experience in product management, Liz knows the day-to-day struggles of product managers all too well. She\u2019s passionate about helping others to be successful in product management, whether that\u2019s process improvement, mentoring or helping with best practices.","url":"https:\/\/www.prodpad.com\/blog\/author\/liz\/"}]}},"_links":{"self":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/posts\/78087","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/comments?post=78087"}],"version-history":[{"count":0,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/posts\/78087\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/media?parent=78087"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/categories?post=78087"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/tags?post=78087"},{"taxonomy":"pp_uni_tag","embeddable":true,"href":"https:\/\/www.prodpad.com\/wp-json\/wp\/v2\/pp_uni_tag?post=78087"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}