<?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: Corporate Blogging 201 â€“ The Risks of NQA Blog Service</title>
	<atom:link href="http://www.churbuck.com/wordpress/2008/02/corporate-blogging-201-%e2%80%93-the-risks-of-nqa-blog-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.churbuck.com/wordpress/2008/02/corporate-blogging-201-%e2%80%93-the-risks-of-nqa-blog-service/</link>
	<description>Commentary on media, technology, marketing and clamming strategies</description>
	<lastBuildDate>Sat, 13 Mar 2010 01:08:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Clark</title>
		<link>http://www.churbuck.com/wordpress/2008/02/corporate-blogging-201-%e2%80%93-the-risks-of-nqa-blog-service/comment-page-1/#comment-303112</link>
		<dc:creator>Scott Clark</dc:creator>
		<pubDate>Fri, 29 Feb 2008 16:09:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.churbuck.com/wordpress/?p=1568#comment-303112</guid>
		<description>I think only an experienced blogger would know the best type of response.  I guess for me the best approach is to stick with the pursuit-of-perfection approach.. here&#039;s a response that typifies this.  

&quot;We pursue perfection with every waking hour and will continue to do so as long as there are unmet needs for our customers.  We will be enforcing those policies as they are written and continuing on our quest for improvements - largely guided by bloggers like yourself who use those products in the trenches.

We receive lots of positive feedback, and cherish it, but realize that the learning will not always come from praise.  Issues that prominent bloggers raise are the fuel that keeps our R&amp;D team&#039;s workstations humming long after most people have gone home.  You can be sure your issue was heard by every one of us as it is now on our internal team wiki, not a black hole.  Thanks.

PS: We hope you will join our beta program for the new version when it is announced.  I&#039;ll make sure you&#039;re on the mailing list, I know you&#039;ll have some good comments.

1. No policy change.
2. Admit an imperfect world.
3. Give the ego a bit of a stroke.
4. Explain how you have a continual improvement process.
5. Appreciate all comments, good or bad.
6. Always use a PS with some sort of offer to keep them informed of changes.

Just my thoughts... I have faced this several times in my consultancy and this type of response seems to work very well.  your mileage may vary!</description>
		<content:encoded><![CDATA[<p>I think only an experienced blogger would know the best type of response.  I guess for me the best approach is to stick with the pursuit-of-perfection approach.. here&#8217;s a response that typifies this.  </p>
<p>&#8220;We pursue perfection with every waking hour and will continue to do so as long as there are unmet needs for our customers.  We will be enforcing those policies as they are written and continuing on our quest for improvements &#8211; largely guided by bloggers like yourself who use those products in the trenches.</p>
<p>We receive lots of positive feedback, and cherish it, but realize that the learning will not always come from praise.  Issues that prominent bloggers raise are the fuel that keeps our R&amp;D team&#8217;s workstations humming long after most people have gone home.  You can be sure your issue was heard by every one of us as it is now on our internal team wiki, not a black hole.  Thanks.</p>
<p>PS: We hope you will join our beta program for the new version when it is announced.  I&#8217;ll make sure you&#8217;re on the mailing list, I know you&#8217;ll have some good comments.</p>
<p>1. No policy change.<br />
2. Admit an imperfect world.<br />
3. Give the ego a bit of a stroke.<br />
4. Explain how you have a continual improvement process.<br />
5. Appreciate all comments, good or bad.<br />
6. Always use a PS with some sort of offer to keep them informed of changes.</p>
<p>Just my thoughts&#8230; I have faced this several times in my consultancy and this type of response seems to work very well.  your mileage may vary!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caving to a Blogger&#8217;s Demands? Advice from Corporate America</title>
		<link>http://www.churbuck.com/wordpress/2008/02/corporate-blogging-201-%e2%80%93-the-risks-of-nqa-blog-service/comment-page-1/#comment-303042</link>
		<dc:creator>Caving to a Blogger&#8217;s Demands? Advice from Corporate America</dc:creator>
		<pubDate>Fri, 29 Feb 2008 14:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.churbuck.com/wordpress/?p=1568#comment-303042</guid>
		<description>[...] And from there, Churbuck dives into a great example of how appeasing a blogger&#8217;s gripe needs careful consideration&#8211;especially if it might set a new precedent on your company&#8217;s refund/return policy. [...]</description>
		<content:encoded><![CDATA[<p>[...] And from there, Churbuck dives into a great example of how appeasing a blogger&#8217;s gripe needs careful consideration&#8211;especially if it might set a new precedent on your company&#8217;s refund/return policy. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
