<?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>Web-Op Blog &#187; Uncategorized</title>
	<atom:link href="http://blog.web-op.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.web-op.com</link>
	<description>Design for SEO</description>
	<lastBuildDate>Tue, 08 May 2012 23:03:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Handling Outages with Class</title>
		<link>http://blog.web-op.com/uncategorized/handling-outages-with-class/</link>
		<comments>http://blog.web-op.com/uncategorized/handling-outages-with-class/#comments</comments>
		<pubDate>Wed, 08 Jun 2011 22:46:57 +0000</pubDate>
		<dc:creator>Jack Zeal</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://web-op.com/blog/?p=325</guid>
		<description><![CDATA[I&#8217;m blogging today at home, as the Web-Op HQ blew a breaker today. That segues nicely into today&#8217;s concern&#8211; how to maintain customer trust when things go south. High-visibility outages aren&#8217;t new. Sony, in particular, averages one per week. However, only some firms can emerge from them with their dignity&#8211; and customer base&#8211; intact. Here&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m blogging today at home, as the Web-Op HQ blew a breaker today.  That segues nicely into today&#8217;s concern&#8211; how to maintain customer trust when things go south.</p>
<p>High-visibility outages aren&#8217;t new.  Sony, in particular, averages one per week.  However, only some firms can emerge from them with their dignity&#8211; and customer base&#8211; intact.  Here&#8217;s how:</p>
<p><span id="more-325"></span></p>
<ul>
<li>Tell the truth.  From day one.  All you need is one tech-savvy customer&#8211; or blogger monitoring the system&#8211; to call you out and the carefully crafter story goes down the tubes.  It&#8217;s often humbling for a rich firm to admit &#8220;something broke and we&#8217;re working on it&#8221;, but trying to blame Anonymous, or China, only goes so far.</li>
<li>Focus on partial solutions.  Maybe your hack was vast and you can&#8217;t restore everything now.  Give the customers what can be restored today and it can help keep rebellion and attrition down.  Maybe you don&#8217;t need to bring back the online store today, but adding a page where they can check your warranty and products will at least make you look alive and credible.  It&#8217;s worth an estimate of how long you can leave a customer without service before they can line up a replacement. </li>
<li>Keep us in the know.  Even if it&#8217;s just a daily &#8216;there is no news&#8217; notification, it helps reassure customers that the system is under repair.</li>
<li>Plan for the worst.  Once more, it&#8217;s admitting sad truths, but it&#8217;s often times better to announce breaches and failures in terms of the worst possible scope.  Saying &#8216;we only lost 2% of users&#8217; today, then amending six times to 3, 5, 7, 10, 12, and 50 gets you the same net damage, but seven hits in the media, and the distrust from lying the first time.</li>
</ul>
<p>Nobody wants to fail, but if you treat customers with the integrity they deserve, you can at least avoid looking sleazy or incompetent as you patch things together.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.web-op.com/uncategorized/handling-outages-with-class/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>


<!-- W3 Total Cache: Minify debug info:
Engine:             disk: basic
Theme:              29946
Template:           index
-->

<!-- W3 Total Cache: CDN debug info:
Engine:             cf
-->
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: blog.web-op.com @ 2012-05-17 15:15:36 -->

<!-- W3 Total Cache: Page cache debug info:
Engine:             disk: basic
Cache key:          w3tc_blog.web-op.com_1_page_7af9d608a5b5b106ab08738749db0a90
Caching:            disabled
Reject reason:      Page is feed
Status:             not cached
Creation Time:      0.299s
Header info:
X-Pingback:         http://blog.web-op.com/xmlrpc.php
Last-Modified:      Tue, 08 May 2012 23:03:42 GMT
ETag:               "18f9add12624f6bbdcfdc9e27dff43bd"
X-Powered-By:       W3 Total Cache/0.9.2.4
Content-Type:       text/xml; charset=UTF-8
-->
