<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>mathewingram.com/work &#187; screwup</title>
	<atom:link href="http://www.mathewingram.com/work/tag/screwup/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mathewingram.com/work</link>
	<description>... at the intersection of media, technology, business and the web</description>
	<lastBuildDate>Sat, 09 Jul 2011 15:34:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Blogs are good and bad for PR &#8212; BluePulse</title>
		<link>http://www.mathewingram.com/work/2006/01/27/blogs-are-good-and-bad-for-pr-bluepulse/</link>
		<comments>http://www.mathewingram.com/work/2006/01/27/blogs-are-good-and-bad-for-pr-bluepulse/#comments</comments>
		<pubDate>Sat, 28 Jan 2006 02:57:18 +0000</pubDate>
		<dc:creator>Mathew</dc:creator>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[Web2.0]]></category>
		<category><![CDATA[Advertising]]></category>
		<category><![CDATA[BluePulse]]></category>
		<category><![CDATA[cache]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[MobHappy]]></category>
		<category><![CDATA[screwup]]></category>

		<guid isPermaLink="false">http://www.mathewingram.com/work/index.php/2006/01/27/blogs-are-good-and-bad-for-pr-bluepulse/</guid>
		<description><![CDATA[Earlier today, I came across a link on Steve Rubel&#8217;s blog to the story on MobHappy about something they wrote regarding BluePulse, a cellphone app startup. As described by Steve and by Carlo of MobHappy, the site wrote something positive about BluePulse, but then Carlo questioned whether the company&#8217;s app really ran on &#8220;any phone&#8221; [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.mathewingram.com%2Fwork%2F2006%2F01%2F27%2Fblogs-are-good-and-bad-for-pr-bluepulse%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.mathewingram.com%2Fwork%2F2006%2F01%2F27%2Fblogs-are-good-and-bad-for-pr-bluepulse%2F&amp;source=mathewi&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Earlier today, I came across a link <a href="http://www.micropersuasion.com/2006/01/blogger_relatio.html">on Steve Rubel&#8217;s blog</a> to the story on MobHappy about <a href="http://mobhappy.com/blog1/2006/01/27/how-not-to-deal-with-blogs-a-case-study/">something they wrote</a> regarding BluePulse, a cellphone app startup. As described by Steve and by Carlo of MobHappy, the site wrote <a href="http://mobhappy.com/blog1/2006/01/22/bluepulse-the-write-once-play-anywhere-mobile-platform/">something positive</a> about BluePulse, but then Carlo questioned whether the company&#8217;s app really ran on &#8220;any phone&#8221; as it said on the website. Someone wrote back and said the copy on the site said &#8220;almost any phone&#8221; &#8212; and sure enough, when Carlo checked, it did say that.</p>
<p>Of course, Carlo being smart enough to know about Google&#8217;s cache, he soon found a copy of the original page, and posted it &#8212; along with a discussion of how the incident was <a href="http://mobhappy.com/blog1/2006/01/27/how-not-to-deal-with-blogs-a-case-study/">an example of &#8220;how not to deal with blogs.&#8221;</a> And he&#8217;s right &#8212; it is.  But there&#8217;s more to it than that, interestingly enough. Although the comments on Steve&#8217;s blog said that BluePulse was ignoring the whole thing, there&#8217;s now <a href="http://mobhappy.com/blog1/2006/01/27/how-not-to-deal-with-blogs-a-case-study/#comment-1568">a long and apologetic comment</a> on MobHappy from one of the founders of BluePulse.</p>
<p>According to Alan Jones, he realized the copy was wrong and asked a developer to change it, and was going to get back to Carlo and apologize &#8212; but before he did, an over-eager employee responded in the comments. As he describes it:</p>
<blockquote><p>&#8220;Luke is an enthusiastic, talented young guy&#8230; heÃ¢â‚¬â„¢s also a new and enthusiastic blogger. HeÃ¢â‚¬â„¢s not a PR person (neither am I) and heÃ¢â‚¬â„¢s definitely not an asshole. Sitting in the same room as the developer, he got word of the change IÃ¢â‚¬â„¢d asked for, and took it on himself to let you know. Luke has made an important error of judgement in pretending the text was never changed. However, I donÃ¢â‚¬â„¢t think it serves anybodyÃ¢â‚¬â„¢s interests to go making him out to be anything sinister. Come on, heÃ¢â‚¬â„¢s a technical sales guy, and this is his first job out of college &#8211; who among us havenÃ¢â‚¬â„¢t made an error of judgement in our early 20s?&#8221;</p></blockquote>
<p>Alan goes on to say that blogs have been an important part of <a href="http://www.bluepulse.com">BluePulse&#8217;</a>s success, and he says he is sorry about how things worked out &#8212; and I&#8217;m sure Luke is pretty sorry too (although he didn&#8217;t say that). I think this one is a good example not just of how companies can screw up in dealing with blogs, but how they can make it right too &#8212; and I hope Alan&#8217;s explanation and apology get the same kind of coverage <a href="http://www.boingboing.net/2006/01/26/carlo_longino_uses_g.html">his screwup did</a> (at least <a href="http://thomashawk.com/2006/01/how-not-to-deal-with-blogger.html">Thomas Hawk</a> and <a href="http://www.boingboing.net/2006/01/26/carlo_longino_uses_g.html">BoingBoing</a> have made note of it).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mathewingram.com/work/2006/01/27/blogs-are-good-and-bad-for-pr-bluepulse/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

