<?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/"
	xmlns:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>GigaOM &#187; Collaboration</title>
	<atom:link href="http://gigaom.com/collaboration/tag/outage/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com</link>
	<description></description>
	<lastBuildDate>Sat, 26 May 2012 13:40:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='gigaom.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://0.gravatar.com/blavatar/0db8f6557d022075dbbf010c54d46d93?s=96&#038;d=http%3A%2F%2Fs2.wp.com%2Fi%2Fbuttonw-com.png</url>
		<title>GigaOM &#187; Collaboration</title>
		<link>http://gigaom.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://gigaom.com/osd.xml" title="GigaOM" />
	<atom:link rel='hub' href='http://gigaom.com/?pushpress=hub'/>
		<item>
		<title>We Are At the Mercy of Those Social Networks</title>
		<link>http://gigaom.com/collaboration/we-are-at-the-mercy-of-those-social-networks/</link>
		<comments>http://gigaom.com/collaboration/we-are-at-the-mercy-of-those-social-networks/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 16:00:26 +0000</pubDate>
		<dc:creator>Aliza Sherman</dc:creator>
				<category><![CDATA[Apps]]></category>
		<category><![CDATA[social media]]></category>
		<category><![CDATA[Tips & Tricks]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[LinkedIn]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[social network]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://webworkerdaily.com/?p=35389</guid>
		<description><![CDATA[Last week, Twitter went down. Again. And yet we all gnash our teeth, wring our hands, cry foul, shake our fists at the sky, then breathe a quick sigh of relief once the Fail Whale is gone and our Twitterstream flows again.<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=35389&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><a href="http://webworkerdaily.files.wordpress.com/2010/07/twitter-_-over-capacity.jpg"><img title="Twitter _ Over capacity" src="http://webworkerdaily.files.wordpress.com/2010/07/twitter-_-over-capacity.jpg?w=300&h=204" alt="fail whale" hspace="10" width="300" height="204" class=" alignleft"></a>Last week, Twitter went down. Again. We’ve all been there before. Many times before. And yet we all gnash our teeth, wring our hands, cry foul, shake our fists at the sky, maybe hop over to Facebook for a spell, then breathe a quick sigh of relief once the Fail Whale is gone and our Twitterstream flows again. Why do we do this to ourselves? Why are we putting our brand assets, communications and marketing messages, customer interactions and other intellectual property into the hands of others?</p>
<p>Your websites are probably on servers owned by a hosting company that guarantees you “no downtime” because they have (ostensibly) an intricate system of backups to keep your site up 24/7. <a href="http://facebook.com/" target="_blank">Facebook</a>, <a href="http://twitter.com" target="_blank">Twitter</a>, <a href="http://linkedin.com" target="_blank">LinkedIn</a> and the rest have zero contractual obligation to you to stay online. Yes, they have good reasons to not go down. But what will we do if they do? It isn’t as if we have many other major choices of social networks where we can disseminate our messages on a massive scale.</p>
<p>Sure we can hop from Twitter to Facebook, but what if Facebook also goes down? I don’t see a mass exodus to MySpace happening. Maybe we’ll hunker down in our niche networks or micronetworks like <a href="http://sprouter.com" target="_blank">Sprouter</a> or <a href="http://www.biznik.com" target="_blank">BizNik</a> or a <a href="http://ning.com" target="_blank">Ning</a> community waiting out the storm. Maybe we’ll check in furiously on <a href="http://foursquare.com" target="_blank">Foursquare</a>, <a href="http://gowalla.com" target="_blank">Gowalla</a>, <a href="http://whrrl.com" target="_blank">Whrrl</a> and the like, hoping someone notices that we’re still alive. Maybe we’ll sit in our blog and send out an email blast inviting people to join us for some conversation in the comments.</p>
<h3>What Are We to Do?</h3>
<p>If you’ve ever used <a href="http://secondlife.com" target="_blank">Second Life</a> for business, you’ve probably faced chronic downtime on a network where you’ve have put creative energies and efforts into building up a storefront or holding a major event, only for the Linden Lab servers to go wonky and you’ve lost sales or had your event ruined. With Second Life, those of us who were entrenched in making it a viable marketing and commerce play for our companies would curse the company that we loved for creating the platform but hated for putting our ventures at risk. Then again, it has never been Linden Lab’s fault that we’ve decided to depend on the servers of a single company for major business transactions.</p>
<h3>We Are at Fault</h3>
<p>What are we thinking? We wouldn’t build our company headquarters on somebody else’s land that they owned without a contract, some guidelines, guarantees and stipulations. And yet we spend hundreds, thousands, tens of thousands of dollars creating assets and putting them on somebody else’s servers — and not even companies that are in the business of keeping things their servers up 24/7. They are in the business of getting you to be on their networks, because the more numbers they gain, the more powerful they become.</p>
<p>Our tolerance for their outages just goes to show how dependent we are on them. We think of these moments as par for the course because we are on the “cutting edge” and dealing with “new technologies.”  We’ve been mesmerized by the promise of exponential reach. We’ve been hypnotized by the potential numbers. We’ve been sold a bill of goods and come out of these moments of outage when some of our marketing and customer service efforts come to a screeching halt, wipe the sweat from our brows, smile feebly, put out our hands and say “Please sir, may I have some more?”</p>
<h3>Can We Stop this Madness?</h3>
<p>Unfortunately, no. We’re too far gone. We’re in this thing too deep. We’re intoxicated by those moments when we get some genuinely impressive results with our Twitter outreach or our Facebook engagement, and we salivate at the possibility of more of that good stuff. We’re hooked.</p>
<p>So if we can’t stop it, what <em>can</em> we do? Here’s my advice:<strong><br></strong></p>
<ul><li><strong>Don’t replace your stable marketing tactics. </strong>Look at social networks and social media marketing as an augmentation of your traditional marketing, not a replacement. Don’t give up the rest of your outreach and marketing efforts.</li>
<li><strong>Have a contingency plan. </strong>Downtime on the big networks is inevitable. If you can’t be real-time on Twitter or Facebook, where will you go and where can your customers find you?</li>
<li><strong>Support niche networks.</strong> Yes, Twitter and Facebook are huge, but they’re not the only places offering the same kind of messaging capabilities. Set up shop in a smaller network and support their efforts to be the next Twitter or Facebook. They’ll love you for it and give you the best darned customer service, because they want and need you.</li>
</ul><p>And keep in mind this mantra: <strong>Don’t put all your eggs in one basket.</strong> It’s an oldie, but a goodie.</p>
<p><em>What are you doing to better distribute your social media presence to safeguard against the Fail Whale?</em></p>
<p><em>Fail Whale screenshot from twitter.com</em></p>
<p><strong>Related GigaOM Pro content (sub. req.):</strong> <a title="Can Enterprise Privacy Survive Social Networking?" href="http://pro.gigaom.com/2010/03/can-enterprise-privacy-survive-social-networking/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_content=alizasherman&amp;utm_campaign=intext&amp;utm_term=35389+we-are-at-the-mercy-of-those-social-networks">Can  Enterprise Privacy Survive Social Networking?</a></p>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=35389&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://gigaom.com/collaboration/we-are-at-the-mercy-of-those-social-networks/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
	

		<media:content url="http://0.gravatar.com/avatar/21760d5d265f4c1cbf10cf67b8627cb9?s=96&#38;d=retro&#38;r=PG" medium="image">
			<media:title type="html">alizasherman</media:title>
		</media:content>

		<media:content url="http://webworkerdaily.files.wordpress.com/2010/07/twitter-_-over-capacity.jpg?w=300" medium="image">
			<media:title type="html">Twitter _ Over capacity</media:title>
		</media:content>
	</item>
		<item>
		<title>4 Tips For Dealing With App Outages</title>
		<link>http://gigaom.com/collaboration/4-tips-for-dealing-with-app-outages/</link>
		<comments>http://gigaom.com/collaboration/4-tips-for-dealing-with-app-outages/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 17:00:16 +0000</pubDate>
		<dc:creator>Thursday Bram</dc:creator>
				<category><![CDATA[How Do You Work?]]></category>
		<category><![CDATA[How-To]]></category>
		<category><![CDATA[How-to (hack, pack, & backpack)]]></category>
		<category><![CDATA[Locations & Services]]></category>
		<category><![CDATA[Software Apps]]></category>
		<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[Outage]]></category>

		<guid isPermaLink="false">http://webworkerdaily.com/?p=24929</guid>
		<description><![CDATA[By our nature, web workers are dependent on online tools to do our work. Sometimes those tools become inaccessible, though. For example, recently a hosting outage took down 37signals&#8217; Basecamp, an app that many web-based workers depend on heavily. These outages can quickly become crises. How [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=24929&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><a href="http://webworkerdaily.files.wordpress.com/2009/12/2595122656_5230f05f30.jpg"><img  title="2595122656_5230f05f30" src="http://webworkerdaily.files.wordpress.com/2009/12/2595122656_5230f05f30.jpg?w=300&h=210" alt="" width="300" height="210" class=" alignleft" /></a>By our nature, web workers are dependent on online tools to do our work. Sometimes those tools become inaccessible, though. For example, recently a hosting outage <a href="http://productblog.37signals.com/products/2009/11/the-basecamp-outage-slowdown-today.html">took down 37signals&#8217; Basecamp</a>, an app that many web-based workers depend on heavily.</p>
<p>These outages can quickly become crises. How do you know what step to take next on a project if the project is entirely managed on a site that is currently down? How do you get in touch with a client if you usually only communicate through that same project management tool? You may not be able to work quite as fast without your tools, but these tips can help you keep the situation from escalating.<span id="more-24929"></span></p>
<ol>
<li><strong>Have an alternative method of communication for clients and co-workers.</strong> It may seem obvious that it&#8217;s important to have multiple methods of communication, but it&#8217;s worth going beyond just having an email address for the people you work with. Depending on just what tools have gone down, there&#8217;s a possibility that an email server has gone down as well. Having a phone number or another form of communication available &#8212; even being able to send a message through a social networking tool &#8212; may be necessary to be able to get through to the folks you need to talk to.</li>
<li><strong>Have a backup of project data.</strong> All your project information is in the cloud, right? Even if the service goes down for a little while, you&#8217;ll be fine, right? Not necessarily. There are plenty of scenarios that end with you having to recreate your project from scratch (as could happen if the app doesn&#8217;t come back up in time, or it goes bust). Having a backup of your information can offer extra peace of mind.</li>
<li><strong>Choose a tool to keep working.</strong> Many outages are open-ended, because it can be tough to tell exactly what is necessary to bring an application back online.If you&#8217;ve got deadlines, waiting around for something to happen is not the best option. Ideally, there may be some aspect of your project that you can work on without logging in at all. If that&#8217;s not the case, there are a couple of options: consult your backup documentation or your client to see what would be most practical to work on in the mean time.</li>
<li><strong>Discuss a new deadline.</strong> If you&#8217;re in a situation where you really can&#8217;t proceed with a project &#8212; maybe the only copies of important files are inaccessible &#8212; you may quickly realize that your current deadlines just aren&#8217;t going to be doable. If that&#8217;s the case, talk to your client or manager as soon as you can and explain the situation. If you aren&#8217;t sure how much of an extension you&#8217;ll need (a typical situation if you don&#8217;t know when your tools will be available again or if you&#8217;ll have to rebuild the project from your backup), make that clear so that you&#8217;ll have grounds for future discussions, if need be.</li>
</ol>
<p>Unfortunately, the best methods for dealing with any kind of application outage require some prep work while your most important tools are still up &#8212; getting contact information for a client who can&#8217;t respond to the only email address you have isn&#8217;t going to move things along. In the worst-case scenario, when an outage has caught you entirely by surprise, it may be difficult to come up with a next step that will actually help you with the work. The best option may be just trying to get in touch with your client or co-worker and check what can be done at all. In the event that you can&#8217;t reach anyone, you may just have to wait out the outage and deal with the repercussions down the road.</p>
<p><em>What do you do when your web apps go down?</em></p>
<p>Image by Flickr user <a href="http://www.flickr.com/photos/adityavm/2595122656/">p4inkiller</a></p>
<p><strong>Related research and analysis from GigaOM Pro:</strong><br />Subscriber content. <a href="http://pro.gigaom.com/?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=24929+4-tips-for-dealing-with-app-outages&utm_content=thursdayb">Sign up for a free trial</a>.</p><ul><li><a href="http://pro.gigaom.com/2010/08/vmwares-cloudy-ambitions-can-it-repeat-hypervisor-success/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_campaign=waterfall?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=24929+4-tips-for-dealing-with-app-outages&utm_content=thursdayb">VMware&#8217;s Cloudy Ambitions: Can It Repeat Hypervisor&nbsp;Success?</a></li><li><a href="http://pro.gigaom.com/2010/07/infrastructure-overview-q2-2010/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_campaign=waterfall?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=24929+4-tips-for-dealing-with-app-outages&utm_content=thursdayb">Infrastructure Overview, Q2&nbsp;2010</a></li><li><a href="http://pro.gigaom.com/2010/06/private-cloud-implementation-guide/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_campaign=waterfall?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=24929+4-tips-for-dealing-with-app-outages&utm_content=thursdayb">Defining Internal Cloud Options: From Appistry to&nbsp;VMware</a></li></ul><img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=24929&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://gigaom.com/collaboration/4-tips-for-dealing-with-app-outages/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/470632d6bb46d029737d70c057dc75f5?s=96&#38;d=retro&#38;r=PG" medium="image">
			<media:title type="html">Thursday Bram</media:title>
		</media:content>

		<media:content url="http:///2009/12/2595122656_5230f05f30.jpg?w=300" medium="image">
			<media:title type="html">2595122656_5230f05f30</media:title>
		</media:content>
	</item>
		<item>
		<title>Service Outages &#8212; It&#039;s All About the Response</title>
		<link>http://gigaom.com/collaboration/service-outages-its-all-about-the-response/</link>
		<comments>http://gigaom.com/collaboration/service-outages-its-all-about-the-response/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 20:00:08 +0000</pubDate>
		<dc:creator>Scott Blitstein</dc:creator>
				<category><![CDATA[CNN Startups]]></category>
		<category><![CDATA[NYT Startups]]></category>
		<category><![CDATA[Software Apps]]></category>
		<category><![CDATA[SYN Feature Enterprise]]></category>
		<category><![CDATA[apology]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[toodledo]]></category>

		<guid isPermaLink="false">http://webworkerdaily.com/?p=14304</guid>
		<description><![CDATA[As we come to rely more and more on web-based applications and services, we&#8217;ve all probably had an instance when our favorite experienced some sort of outage. While I think we are generally patient with brief hiccups and such, what would happen if a web service [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=14304&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>As we come to rely more and more on web-based applications and services, we&#8217;ve all probably had an instance when our favorite experienced some sort of outage.  While I think we are generally patient with brief hiccups and such, what would happen if a web service you relied on was down for 16 hours? How should the developers handle the situation?</p>
<p>In what has to be a developer&#8217;s worst nightmare, last week a &#8220;perfect storm&#8221; of events led to just that for task management service <a title="Toodledo - Home" href="http://toodledo.com">Toodledo</a>.  Thankfully, after what I am sure was a very long day for the Toodledo team, they were able to bring things back online and with no data loss.</p>
<p>As a user of Toodledo, I was impressed with the outstanding job they did not only recovering our data but for the way they communicated with us during what was really an unthinkable situation.  Was it an inconvenience to be without the service? Absolutely it was. But in what really should be a case study in how to respond to such an experience, the folks at Toodledo provided frequent updates and explanations during the outage and a <a title="Toodledo - And we're back.." href="http://www.toodledo.com/forums/1/2182/0/and-were-back-from-a-very-prolonged-outage.html">thorough debrief</a> after the fact.</p>
<p><span id="more-14304"></span></p>
<p>I suggest you take a few minutes to read through the 10 or so pages of user comments and responses to their explanation there.  It is full of appreciation and understanding from users for being spoken to honestly and treated with respect.  Rather than leaving in droves, more than a few people have suggested that they have upgraded from free to paid accounts because of the way that the situation was handled.</p>
<p>So what did they do right?  Here are five steps on how to deal with your customers during (and after) a service outage.</p>
<ol>
<li>
<div>Give us a descriptive error page and lead us to a forum where you are discussing the issue. Let us know there is an issue and that you are actively working on resolving it, especially if it is above and beyond something brief or minor.</div>
</li>
<li>
<div>Make updates regularly. We know that taking the time to write an update is keeping you from the actual &#8220;fixing&#8221; of things, but we&#8217;re scared about our stuff and want to know what is happening.</div>
</li>
<li>
<div>When it&#8217;s fixed, tell us what happened.  We&#8217;re probably still a bit angry and feeling inconvenienced but we&#8217;ve had &#8220;stuff&#8221; happen in our lives, too, and will likely empathize.  Keep in mind, we may not be as technical as you, so give us the details in terms we understand.  Keep the jargon to a minimum.</div>
</li>
<li>
<div>Acknowledge that the outage was an inconvenience, and don&#8217;t minimize the effect it had on us.  We use your service because it helps us and provides a benefit.  When it is down, we lose that.  I think that this is particularly important.</div>
</li>
<li>
<div>Tell us what is being done to keep the issue from happening again.</div>
</li>
</ol>
<p>Despite everyone&#8217;s best intentions and planning, outages are going to happen.  How it is handled and how you respond to your customers will define our response.</p>
<p><em>What do you expect from a provider during or after an outage?  Tell us in the comments about your experiences.</em></p>
<p><strong>Related research and analysis from GigaOM Pro:</strong><br />Subscriber content. <a href="http://pro.gigaom.com/?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=14304+service-outages-its-all-about-the-response&utm_content=scottblitz">Sign up for a free trial</a>.</p><ul><li><a href="http://pro.gigaom.com/2011/03/why-ipad-2-will-lead-consumers-into-the-post-pc-era/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_campaign=waterfall?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=14304+service-outages-its-all-about-the-response&utm_content=scottblitz">Why iPad 2 Will Lead Consumers Into the Post-PC&nbsp;Era</a></li><li><a href="http://pro.gigaom.com/2011/03/the-near-term-evolution-of-social-commerce/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_campaign=waterfall?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=14304+service-outages-its-all-about-the-response&utm_content=scottblitz">The Near-Term Evolution of Social&nbsp;Commerce</a></li><li><a href="http://pro.gigaom.com/2011/02/content-farms-the-players-the-benefits-the-risks/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_campaign=waterfall?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=14304+service-outages-its-all-about-the-response&utm_content=scottblitz">Content Farms: The Players, The Benefits, The&nbsp;Risks</a></li></ul><img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=14304&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://gigaom.com/collaboration/service-outages-its-all-about-the-response/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/916644ba552abe1d9794c3e8631d493d?s=96&#38;d=retro&#38;r=PG" medium="image">
			<media:title type="html">scottblitz</media:title>
		</media:content>
	</item>
	</channel>
</rss>
