<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How Our Business Captures, Analyzes and Acts on Customer Feedback	</title>
	<atom:link href="https://www.groovehq.com/blog/customer-feedback/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog/customer-feedback</link>
	<description></description>
	<lastBuildDate>Fri, 04 Dec 2020 00:31:33 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.14</generator>
	<item>
		<title>
		By: Pablo Gutierrez		</title>
		<link>https://www.groovehq.com/blog/customer-feedback#comment-1026</link>

		<dc:creator><![CDATA[Pablo Gutierrez]]></dc:creator>
		<pubDate>Sun, 22 Jan 2017 20:13:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=1222#comment-1026</guid>

					<description><![CDATA[Hi Alex! We are also gathering feedback from our clients. However, we obtain very different and variable coments and suggestions of our service. It doesn&#039;t follow a specific trend or clients are not asking for similar features. Which feedback do you focus on? How do you control not to satisfy everyone? 

Thanks!]]></description>
			<content:encoded><![CDATA[<p>Hi Alex! We are also gathering feedback from our clients. However, we obtain very different and variable coments and suggestions of our service. It doesn&#8217;t follow a specific trend or clients are not asking for similar features. Which feedback do you focus on? How do you control not to satisfy everyone? </p>
<p>Thanks!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Vinish Garg		</title>
		<link>https://www.groovehq.com/blog/customer-feedback#comment-1032</link>

		<dc:creator><![CDATA[Vinish Garg]]></dc:creator>
		<pubDate>Fri, 20 Jan 2017 17:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=1222#comment-1032</guid>

					<description><![CDATA[Just responded to the survey before I started reading the post. Impeccable post and I simply loved your focus on *onboarding*. A lot to take away as you continue to raise the bar to make this blog space all the more useful.]]></description>
			<content:encoded><![CDATA[<p>Just responded to the survey before I started reading the post. Impeccable post and I simply loved your focus on *onboarding*. A lot to take away as you continue to raise the bar to make this blog space all the more useful.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: John Rougeux		</title>
		<link>https://www.groovehq.com/blog/customer-feedback#comment-1039</link>

		<dc:creator><![CDATA[John Rougeux]]></dc:creator>
		<pubDate>Fri, 20 Jan 2017 13:55:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=1222#comment-1039</guid>

					<description><![CDATA[Hey Alex, thanks for sharing this. I&#039;m curious how you share this feedback internally. Do you find it most effective to share the raw data with your entire team? What&#039;s your process for reviewing these items and turning them into items on the roadmap - do you handle that yourself, or do you have a dedicated product person who handles? Thanks for your thoughts!]]></description>
			<content:encoded><![CDATA[<p>Hey Alex, thanks for sharing this. I&#8217;m curious how you share this feedback internally. Do you find it most effective to share the raw data with your entire team? What&#8217;s your process for reviewing these items and turning them into items on the roadmap &#8211; do you handle that yourself, or do you have a dedicated product person who handles? Thanks for your thoughts!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: nah		</title>
		<link>https://www.groovehq.com/blog/customer-feedback#comment-1038</link>

		<dc:creator><![CDATA[nah]]></dc:creator>
		<pubDate>Fri, 20 Jan 2017 09:13:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=1222#comment-1038</guid>

					<description><![CDATA[What about feedback that your support collects? Surprised not to see that in there.]]></description>
			<content:encoded><![CDATA[<p>What about feedback that your support collects? Surprised not to see that in there.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: danielkun		</title>
		<link>https://www.groovehq.com/blog/customer-feedback#comment-1041</link>

		<dc:creator><![CDATA[danielkun]]></dc:creator>
		<pubDate>Thu, 19 Jan 2017 19:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=1222#comment-1041</guid>

					<description><![CDATA[Hey Alex, thanks for the post. And thanks for the spreadsheet - it is inspiring that you can have success with something so simple. I recently learned about productboard.com &#039;s user research feature and was hooked by it, but seeing your sheet makes me think we can have success with something similar short-term without adding tools.

I have one question though: If you say &quot;we&quot; talk to customers, do you mean &quot;I&quot;, or are there more people who do it? How do you transport you insights to the dev team so that they can come up with solutions to your customers problems themselves?]]></description>
			<content:encoded><![CDATA[<p>Hey Alex, thanks for the post. And thanks for the spreadsheet &#8211; it is inspiring that you can have success with something so simple. I recently learned about productboard.com &#8216;s user research feature and was hooked by it, but seeing your sheet makes me think we can have success with something similar short-term without adding tools.</p>
<p>I have one question though: If you say &#8220;we&#8221; talk to customers, do you mean &#8220;I&#8221;, or are there more people who do it? How do you transport you insights to the dev team so that they can come up with solutions to your customers problems themselves?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Anne Paling		</title>
		<link>https://www.groovehq.com/blog/customer-feedback#comment-1042</link>

		<dc:creator><![CDATA[Anne Paling]]></dc:creator>
		<pubDate>Thu, 19 Jan 2017 15:55:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=1222#comment-1042</guid>

					<description><![CDATA[I really appreciate the link to the google sheet! Analyzing the data seems very overwhelming but having that as a starting point, plus the idea of tagging keywords, makes it much more manageable. Killin&#039; it as always!]]></description>
			<content:encoded><![CDATA[<p>I really appreciate the link to the google sheet! Analyzing the data seems very overwhelming but having that as a starting point, plus the idea of tagging keywords, makes it much more manageable. Killin&#8217; it as always!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mike Sudyk		</title>
		<link>https://www.groovehq.com/blog/customer-feedback#comment-1043</link>

		<dc:creator><![CDATA[Mike Sudyk]]></dc:creator>
		<pubDate>Thu, 19 Jan 2017 15:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=1222#comment-1043</guid>

					<description><![CDATA[Great post Alex. We are in process of launching a SaaS app and this is gold! Thanks for putting this together. Planning on signing up for Groove when we launch]]></description>
			<content:encoded><![CDATA[<p>Great post Alex. We are in process of launching a SaaS app and this is gold! Thanks for putting this together. Planning on signing up for Groove when we launch</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
