<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Comment Hell or Comment Heaven</title>
	<atom:link href="http://digitalstuffing.com/2008/11/comment-hell-or-comment-heaven/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitalstuffing.com/2008/11/comment-hell-or-comment-heaven/</link>
	<description>Digital marketing, engagement, transmedia, games, fun</description>
	<lastBuildDate>Thu, 12 Jan 2012 11:01:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Rachel</title>
		<link>http://digitalstuffing.com/2008/11/comment-hell-or-comment-heaven/comment-page-1/#comment-58</link>
		<dc:creator>Rachel</dc:creator>
		<pubDate>Sat, 22 Nov 2008 15:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://digitalstuffing.com/?p=71#comment-58</guid>
		<description>I agree - and I&#039;m guessing if it had not blew up on a weekend they may have taken more time to work it through and may have taken that option. But businesses, unlike social media, are rarely 24/7 and I think the bloggers and tweeters calling for action could have remembered that a little.   

My guess is they had never thought this through, did not have a plan and reacted - they knew they had to react and did the one that was probably the easiest route. That&#039;s why it is key for brands to plan for this the same as they do for any PR crisis but mostly that seems to focus on product issues, not advertising issues.</description>
		<content:encoded><![CDATA[<p>I agree &#8211; and I&#8217;m guessing if it had not blew up on a weekend they may have taken more time to work it through and may have taken that option. But businesses, unlike social media, are rarely 24/7 and I think the bloggers and tweeters calling for action could have remembered that a little.   </p>
<p>My guess is they had never thought this through, did not have a plan and reacted &#8211; they knew they had to react and did the one that was probably the easiest route. That&#8217;s why it is key for brands to plan for this the same as they do for any PR crisis but mostly that seems to focus on product issues, not advertising issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul M. Banas</title>
		<link>http://digitalstuffing.com/2008/11/comment-hell-or-comment-heaven/comment-page-1/#comment-57</link>
		<dc:creator>Paul M. Banas</dc:creator>
		<pubDate>Sat, 22 Nov 2008 15:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://digitalstuffing.com/?p=71#comment-57</guid>
		<description>I realize the makers of Motrin are taking it on the chin this week, but I wonder if they may have overreacted.  They are a second tier brand in a highly competitive category, dominated by private label.  Their brand has been surrounded by more buzz in the past week then they&#039;ve seen in the past year or more.  Rather then pull everything down in a rush, with apologies flying left and right, if they had thought a bit, they could have used their 15 minutes of social media fame to engage in the conversation, rather than running from it.</description>
		<content:encoded><![CDATA[<p>I realize the makers of Motrin are taking it on the chin this week, but I wonder if they may have overreacted.  They are a second tier brand in a highly competitive category, dominated by private label.  Their brand has been surrounded by more buzz in the past week then they&#8217;ve seen in the past year or more.  Rather then pull everything down in a rush, with apologies flying left and right, if they had thought a bit, they could have used their 15 minutes of social media fame to engage in the conversation, rather than running from it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

