<?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: Turn Downtime Into a Communication WIN</title>
	<atom:link href="http://www.searchenginepeople.com/blog/turn-downtime-into-a-communication-win.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginepeople.com/blog/turn-downtime-into-a-communication-win.html</link>
	<description>Canada's Search and Social Media Authority</description>
	<lastBuildDate>Mon, 13 Feb 2012 17:01:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Cool Gifts</title>
		<link>http://www.searchenginepeople.com/blog/turn-downtime-into-a-communication-win.html#comment-9347</link>
		<dc:creator>Cool Gifts</dc:creator>
		<pubDate>Wed, 24 Jun 2009 21:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=3574#comment-9347</guid>
		<description>I really think your &quot;Don&#039;ts&quot; are spot on. As I was reading through those, I could think of exact examples where each of those have happened. I really believe it&#039;s important for companies to suck up their pride and admit that there was a problem. In times of crisis, it usually makes the customers for comfortable when the company can be as transparent as possible.</description>
		<content:encoded><![CDATA[<p>I really think your &#034;Don&#039;ts&#034; are spot on. As I was reading through those, I could think of exact examples where each of those have happened. I really believe it&#039;s important for companies to suck up their pride and admit that there was a problem. In times of crisis, it usually makes the customers for comfortable when the company can be as transparent as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SEO News Round Up for June 5, 2009 &#124; The Adventures of SEO Boy</title>
		<link>http://www.searchenginepeople.com/blog/turn-downtime-into-a-communication-win.html#comment-9031</link>
		<dc:creator>SEO News Round Up for June 5, 2009 &#124; The Adventures of SEO Boy</dc:creator>
		<pubDate>Fri, 05 Jun 2009 19:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=3574#comment-9031</guid>
		<description>[...] Social media is a fantastic way to build connections and awareness, but you need to know how to use it to handle the bad as well as the good, and this series of cause-and-effect examples can show you [...]</description>
		<content:encoded><![CDATA[<p>[...] Social media is a fantastic way to build connections and awareness, but you need to know how to use it to handle the bad as well as the good, and this series of cause-and-effect examples can show you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hendro</title>
		<link>http://www.searchenginepeople.com/blog/turn-downtime-into-a-communication-win.html#comment-9018</link>
		<dc:creator>hendro</dc:creator>
		<pubDate>Fri, 05 Jun 2009 03:44:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=3574#comment-9018</guid>
		<description>Thanks for writing, I really enjoyed your latest post.</description>
		<content:encoded><![CDATA[<p>Thanks for writing, I really enjoyed your latest post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Locke</title>
		<link>http://www.searchenginepeople.com/blog/turn-downtime-into-a-communication-win.html#comment-9009</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Wed, 03 Jun 2009 18:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginepeople.com/?p=3574#comment-9009</guid>
		<description>When people resolve the problem, they think they are done. Nope. Now, you need to fix the process that allowed the problem to be expressed on the production server. 

In the software world we call QC QA, so we never have to do QA. QA, quality assurance, isn&#039;t about fixing the bug, its about fixing the cause of the bug, which is always a process. QC is finding the bug. 

Maybe customers shouldn&#039;t stop talking about a bug until they are reassured that QA has been done to the underlying processes. 

The Twitter fails seem constant. They originate from a wide variety of issues/bugs some deliberate. The fix does let us get on with our work, but the constant fails don&#039;t let us trust. Trust is harder to achieve than random uptime. Trust requires qualtity assurance in the manufacturing sense of the word.</description>
		<content:encoded><![CDATA[<p>When people resolve the problem, they think they are done. Nope. Now, you need to fix the process that allowed the problem to be expressed on the production server. </p>
<p>In the software world we call QC QA, so we never have to do QA. QA, quality assurance, isn&#039;t about fixing the bug, its about fixing the cause of the bug, which is always a process. QC is finding the bug. </p>
<p>Maybe customers shouldn&#039;t stop talking about a bug until they are reassured that QA has been done to the underlying processes. </p>
<p>The Twitter fails seem constant. They originate from a wide variety of issues/bugs some deliberate. The fix does let us get on with our work, but the constant fails don&#039;t let us trust. Trust is harder to achieve than random uptime. Trust requires qualtity assurance in the manufacturing sense of the word.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

