<?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 An Angry Email Pushed Us To Start Publishing More Product Updates	</title>
	<atom:link href="https://www.groovehq.com/blog/product-update-email-rhythm/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog/product-update-email-rhythm</link>
	<description></description>
	<lastBuildDate>Sat, 16 Feb 2019 11:41:11 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.14</generator>
	<item>
		<title>
		By: Anton		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-627</link>

		<dc:creator><![CDATA[Anton]]></dc:creator>
		<pubDate>Sun, 28 May 2017 20:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-627</guid>

					<description><![CDATA[Alex, you have an awesome blog. And this article is superb. But what result you get after this information of updates? Do you improve your churn? How much?]]></description>
			<content:encoded><![CDATA[<p>Alex, you have an awesome blog. And this article is superb. But what result you get after this information of updates? Do you improve your churn? How much?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Bill Dettering		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-677</link>

		<dc:creator><![CDATA[Bill Dettering]]></dc:creator>
		<pubDate>Fri, 12 May 2017 19:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-677</guid>

					<description><![CDATA[We actually do something similar with Zingtree.  We started with Intercom based upon your advice, and we try to make a product updates blog post every week, but sometimes this only occurs monthly, even though we update more often than that.

If your team can push updates often without breaking anything, then absolutely you should let customers know.  I think 2 weeks sounds about right.

Great stuff..]]></description>
			<content:encoded><![CDATA[<p>We actually do something similar with Zingtree.  We started with Intercom based upon your advice, and we try to make a product updates blog post every week, but sometimes this only occurs monthly, even though we update more often than that.</p>
<p>If your team can push updates often without breaking anything, then absolutely you should let customers know.  I think 2 weeks sounds about right.</p>
<p>Great stuff..</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: T.S.		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-683</link>

		<dc:creator><![CDATA[T.S.]]></dc:creator>
		<pubDate>Fri, 12 May 2017 13:14:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-683</guid>

					<description><![CDATA[How many years until the starter plan is &quot;implemented on the backend&quot;?]]></description>
			<content:encoded><![CDATA[<p>How many years until the starter plan is &#8220;implemented on the backend&#8221;?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Alex López		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-684</link>

		<dc:creator><![CDATA[Alex López]]></dc:creator>
		<pubDate>Fri, 12 May 2017 09:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-684</guid>

					<description><![CDATA[Alex this is very, very interesting. 
Thanks for taking the time to share it.]]></description>
			<content:encoded><![CDATA[<p>Alex this is very, very interesting.<br />
Thanks for taking the time to share it.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Adam		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-686</link>

		<dc:creator><![CDATA[Adam]]></dc:creator>
		<pubDate>Thu, 11 May 2017 18:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-686</guid>

					<description><![CDATA[I&#039;ve already raised this with Groove, you&#039;ve got some major browser issues with your support widget.  It doesn&#039;t work on IE.

If you go to https://help.groovehq.com/help_center and click on &quot;Contact Us&quot; in IE 11, it&#039;s broken.

I got told you were working on it and then your bug fix email came out... no fix.

There&#039;s some nice things about Groove (especially how simple it is to use), but as a new client, I do wonder how long the issue has been there. I have found giving people rough ETA&#039;s definitely helps to manage expectations.
PS. I&#039;m glad I can now reorder KB articles.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve already raised this with Groove, you&#8217;ve got some major browser issues with your support widget.  It doesn&#8217;t work on IE.</p>
<p>If you go to <a href="https://help.groovehq.com/help_center" rel="nofollow ugc">https://help.groovehq.com/help_center</a> and click on &#8220;Contact Us&#8221; in IE 11, it&#8217;s broken.</p>
<p>I got told you were working on it and then your bug fix email came out&#8230; no fix.</p>
<p>There&#8217;s some nice things about Groove (especially how simple it is to use), but as a new client, I do wonder how long the issue has been there. I have found giving people rough ETA&#8217;s definitely helps to manage expectations.<br />
PS. I&#8217;m glad I can now reorder KB articles.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Josh		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-687</link>

		<dc:creator><![CDATA[Josh]]></dc:creator>
		<pubDate>Thu, 11 May 2017 18:09:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-687</guid>

					<description><![CDATA[Hey Alex - great post - we started doing this (without the email, just blog post + in-app) about two months ago, and similarly the response has been great!

We&#039;ve also found that it makes us much more accountable to deliver user facing updates, and that we&#039;re doing a lot better and shipping better things faster as a result!]]></description>
			<content:encoded><![CDATA[<p>Hey Alex &#8211; great post &#8211; we started doing this (without the email, just blog post + in-app) about two months ago, and similarly the response has been great!</p>
<p>We&#8217;ve also found that it makes us much more accountable to deliver user facing updates, and that we&#8217;re doing a lot better and shipping better things faster as a result!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Laszlo Alt		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-688</link>

		<dc:creator><![CDATA[Laszlo Alt]]></dc:creator>
		<pubDate>Thu, 11 May 2017 17:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-688</guid>

					<description><![CDATA[I like the transparency. I agree with the visuals and experience where users will never know they are &quot;upgraded&quot; unless its obvious to them or you actually announce the changes. Many people are looking for that &quot;Wow&quot; factor in updates of hardware/software. I find this new mentality to break old traditions of building stable products that are tested through time with very minor updates. Thank you for sharing!]]></description>
			<content:encoded><![CDATA[<p>I like the transparency. I agree with the visuals and experience where users will never know they are &#8220;upgraded&#8221; unless its obvious to them or you actually announce the changes. Many people are looking for that &#8220;Wow&#8221; factor in updates of hardware/software. I find this new mentality to break old traditions of building stable products that are tested through time with very minor updates. Thank you for sharing!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Geilt		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-689</link>

		<dc:creator><![CDATA[Geilt]]></dc:creator>
		<pubDate>Thu, 11 May 2017 17:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-689</guid>

					<description><![CDATA[We switched to a competitor due to HIPPA compliance and BAA agreements they signed. Needless to say, they had an app, which I loves. Using Groove on mobile was horrible even the web interface wasn&#039;t mobile friendly. Right as we made the switch, my support guy told me, oh yea Groove finally had an app...right as we switched. Ah well. It was one of the worst parts not being able to use Groove mobile, besides through email. But yea it would have been nice to know! Maybe I missed an email, or a link in the interface that showed it off.]]></description>
			<content:encoded><![CDATA[<p>We switched to a competitor due to HIPPA compliance and BAA agreements they signed. Needless to say, they had an app, which I loves. Using Groove on mobile was horrible even the web interface wasn&#8217;t mobile friendly. Right as we made the switch, my support guy told me, oh yea Groove finally had an app&#8230;right as we switched. Ah well. It was one of the worst parts not being able to use Groove mobile, besides through email. But yea it would have been nice to know! Maybe I missed an email, or a link in the interface that showed it off.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Taylor Overton		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-690</link>

		<dc:creator><![CDATA[Taylor Overton]]></dc:creator>
		<pubDate>Thu, 11 May 2017 16:47:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-690</guid>

					<description><![CDATA[I always love these blog posts -- so encouraging and inspiring. I love to share them with our support team, so that we can brainstorm how to market our products and connect with our customers more authentically. Thanks Alex!]]></description>
			<content:encoded><![CDATA[<p>I always love these blog posts &#8212; so encouraging and inspiring. I love to share them with our support team, so that we can brainstorm how to market our products and connect with our customers more authentically. Thanks Alex!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: eagle123456		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-691</link>

		<dc:creator><![CDATA[eagle123456]]></dc:creator>
		<pubDate>Thu, 11 May 2017 16:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-691</guid>

					<description><![CDATA[What an amazing article. A successful CEO just went out of his way to give some of the best and genuine business advice I have ever heard, every word true to the core. If this is the kind of care and philosophy he applies to his business, his customers and employees are very lucky :)]]></description>
			<content:encoded><![CDATA[<p>What an amazing article. A successful CEO just went out of his way to give some of the best and genuine business advice I have ever heard, every word true to the core. If this is the kind of care and philosophy he applies to his business, his customers and employees are very lucky 🙂</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Danielle Burrow		</title>
		<link>https://www.groovehq.com/blog/product-update-email-rhythm#comment-692</link>

		<dc:creator><![CDATA[Danielle Burrow]]></dc:creator>
		<pubDate>Thu, 11 May 2017 14:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2095#comment-692</guid>

					<description><![CDATA[This mindset can also be applied to how an internal Dev Team informs company employees in other departments about the recent changes that have been going on behind the scenes. Everybody always knows about the big changes, but it&#039;s so important to push out small internal system changes (and then communicate those changes) frequently and consistently to keep customers (or in our case, employees) happy with the product and/or service you’re providing. If your employees don&#039;t see the small changes being made on a daily basis, they might as well not be happening. Also, I especially loved when you said &quot;In customer relationships, perception is everything.&quot; Ideas, decisions, and actions are only as good/bad as they are perceived by those affected by them, be they clients or employees. Thanks again for the timely read.]]></description>
			<content:encoded><![CDATA[<p>This mindset can also be applied to how an internal Dev Team informs company employees in other departments about the recent changes that have been going on behind the scenes. Everybody always knows about the big changes, but it&#8217;s so important to push out small internal system changes (and then communicate those changes) frequently and consistently to keep customers (or in our case, employees) happy with the product and/or service you’re providing. If your employees don&#8217;t see the small changes being made on a daily basis, they might as well not be happening. Also, I especially loved when you said &#8220;In customer relationships, perception is everything.&#8221; Ideas, decisions, and actions are only as good/bad as they are perceived by those affected by them, be they clients or employees. Thanks again for the timely read.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
