<?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; failure</title>
	<atom:link href="http://www.mathewingram.com/work/tag/failure/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>Twitter failure: Call the irony squad</title>
		<link>http://www.mathewingram.com/work/2008/04/21/twitter-failure-call-the-irony-squad/</link>
		<comments>http://www.mathewingram.com/work/2008/04/21/twitter-failure-call-the-irony-squad/#comments</comments>
		<pubDate>Mon, 21 Apr 2008 15:16:02 +0000</pubDate>
		<dc:creator>Mathew</dc:creator>
				<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Social networks]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[failure]]></category>
		<category><![CDATA[social]]></category>

		<guid isPermaLink="false">http://www.mathewingram.com/work/?p=2357</guid>
		<description><![CDATA[Update 2: Via a Twitter post from Engtech (which I found on FriendFeed), I came across a suggestion from this guy about how to re-enable your Twitter cache. I tried it and it seems to have worked. And now &#8212; finally &#8212; there is a Twitter blog post about the difficulties (hat tip to Frederic [...]]]></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%2F2008%2F04%2F21%2Ftwitter-failure-call-the-irony-squad%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.mathewingram.com%2Fwork%2F2008%2F04%2F21%2Ftwitter-failure-call-the-irony-squad%2F&amp;source=mathewi&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><b>Update 2:</b></p>
<p>Via <a href="http://twitter.com/engtech/statuses/793752674">a Twitter post</a> from Engtech (which I found on FriendFeed), I came across a suggestion from <a href="http://cdevroe.com/notes/twitter-sorta-down/">this guy</a> about how to re-enable your Twitter cache. I tried it and it seems to have worked. And now &#8212; finally &#8212; there is <a href="http://blog.twitter.com/2008/04/weekend-web-weirdness.html">a Twitter blog post</a> about the difficulties (hat tip to <a href="http://twitter.com/fredericl/statuses/793777966">Frederic</a> from The Last Podcast).</p>
<p><b>Update:</b></p>
<p>There&#8217;s a yellow box at the top of the home page for Twitter users that says:</p>
<blockquote><p>&#8220;Due to some cache changes we made Friday, you may not be seeing all updates in your timeline (don&#8217;t worry, they&#8217;re still there!). Thank you for your patience while we fix this issue.&#8221;</p></blockquote>
<p>As Nav notes, this is <a href="http://twitter.com/scrawledinwax/statuses/793712614">the equivalent of</a> flowers after a fight. I think we could use a bit more than that.</p>
<p><b>Original post:</b></p>
<p>MG Siegler of ParisLemon and VentureBeat (and my rival for number nine slot on the Techmeme 100) is <a href="http://www.parislemon.com/2008/04/twitter-fail-day-3-communications.html">keeping the pressure on</a> Twitter about the system&#8217;s recent problems &#8212; intermittent dropping of people&#8217;s messages, etc. &#8212; and so he should. For a service that is supposed to be all about real-time communication, the Twitter gang have been doing very little of that about their own issues. People continue to complain on the Twitter <a href="http://getsatisfaction.com/twitter/topics/web_not_posting_tweets_from_people_i_follow">customer-response forum</a>, and have gotten little response.</p>
<p><span id="more-2357"></span></p>
<p>The last update from the team on the forum is almost two days old, and says that the problem resulted from a caching fix &#8212; which ironically was supposed to make the system more robust and faster, but seems to have opened a black hole into which people&#8217;s Twitter posts randomly fall. The last post on the Twitter blog is <a href="http://blog.twitter.com/">from five days ago</a>, and it&#8217;s about how great Twitter is for helping that guy get out of jail in Egypt. It&#8217;s a good thing he&#8217;s not there right now, because he&#8217;d be out of luck. The last Twitter <a href="http://twitter.com/twitter_status">status message</a> is from two days ago.</p>
<p>As MG notes, one of the big problems with this particular Twitter outage is that it isn&#8217;t really an outage at all &#8212; it&#8217;s just a seemingly random disappearance of posts, which makes it difficult to tell whether there&#8217;s even an issue at all, as I mentioned in <a href="http://www.mathewingram.com/work/2008/04/20/social-apps-and-the-attention-factor/">my earlier post</a> on the weekend. How many people are thinking &#8220;Oh well, maybe my friends are just too busy to respond to my posts.&#8221; That could push them away from Twitter gradually, I think. If you&#8217;re basing your business model on being a viral communications app, you had better communicate. </p>
<p>And that goes for <a href="http://twitter.com/help/aboutus">the Twitter team</a> as well &#8212; I&#8217;m sure they&#8217;re busy fixing things, but they should be out there communicating it. And as MG and others <a href="http://jeffnolan.com/wp/2008/04/21/twitter-withdrawals/">have pointed out</a>, this is a particularly bad time for Twitter to be failing: the massive Web 2.0 conference starts tomorrow.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mathewingram.com/work/2008/04/21/twitter-failure-call-the-irony-squad/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Fiddling while the music industry burned</title>
		<link>http://www.mathewingram.com/work/2008/01/12/fiddling-while-the-music-industry-burned/</link>
		<comments>http://www.mathewingram.com/work/2008/01/12/fiddling-while-the-music-industry-burned/#comments</comments>
		<pubDate>Sat, 12 Jan 2008 19:07:13 +0000</pubDate>
		<dc:creator>Mathew</dc:creator>
				<category><![CDATA[Media]]></category>
		<category><![CDATA[Music]]></category>
		<category><![CDATA[failure]]></category>
		<category><![CDATA[industry]]></category>

		<guid isPermaLink="false">http://www.mathewingram.com/work/2008/01/12/fiddling-while-the-music-industry-burned/</guid>
		<description><![CDATA[There&#8217;s a nice overview of the music industry&#8217;s dilemma in the current issue of The Economist. Nothing that surprising, but some worthwhile points &#8212; including a telling anecdote to start the piece, in which one of the major record labels has an epiphany about where the CD business is going: &#8220;At the end of the [...]]]></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%2F2008%2F01%2F12%2Ffiddling-while-the-music-industry-burned%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.mathewingram.com%2Fwork%2F2008%2F01%2F12%2Ffiddling-while-the-music-industry-burned%2F&amp;source=mathewi&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>There&#8217;s a nice overview of the music industry&#8217;s dilemma in the current issue of The Economist. Nothing that surprising, but some worthwhile points &#8212; including a telling anecdote to start <a href="http://economist.com/business/displaystory.cfm?story_id=10498664">the piece</a>, in which one of the major record labels has an epiphany about where the CD business is going:</p>
<blockquote><p>&#8220;At the end of the session the EMI bosses thanked them for their comments and told them to help themselves to a big pile of CDs sitting on a table. But none of the teens took any of the CDs, even though they were free. â€œThat was the moment we realised the game was completely up,â€ says a person who was there.&#8221;</p></blockquote>
<p>There are also some numbers, of the kind that should make many a label stop and think, if they aren&#8217;t already:</p>
<blockquote><p>&#8220;The volume of physical albums sold dropped by 19% in 2007 from the year before&#8230; For the first half of 2007, sales of music on CD and other physical formats fell by 6% in Britain, by 9% in Japan, France and Spain, by 12% in Italy, 14% in Australia and 21% in Canada.&#8221;</p></blockquote>
<p>And some perceptive points about the slippery slope that the major labels find themselves on at the moment:</p>
<blockquote><p>1. &#8220;Because sales of CDs are tumbling, big retailers such as Wal-Mart are cutting the amount of shelf-space they give to music, which in turn accelerates the decline.&#8221;</p>
<p>2. &#8220;Artists are receiving far less marketing and promotional support than before, which could prompt them to seek alternatives.&#8221;</p>
<p>3. &#8220;Record companies face such hostile conditions that their backers, whether private equity or corporations, are loth to spend the sums required to move into the bits of the music industry that are thriving, such as touring and merchandising.&#8221;</p></blockquote>
<p>But perhaps the best point in the piece is the observation that the industry could have saved itself a lot of the pain it has seen over the past several years, and likely become stronger to boot, if it had shown <a href="http://www.cincomsmalltalk.com/blog/blogView?showComments=true&#038;printTitle=The_Importance_of_Being_Agile&#038;entry=3377584142">more flexibility</a> when digital music first became a reality, instead of deciding to sue everything that moved and call that a strategy. Now, they could be too far down the slippery slope to irrelevance to recover.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mathewingram.com/work/2008/01/12/fiddling-while-the-music-industry-burned/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Learning from Kiko&#8217;s failure</title>
		<link>http://www.mathewingram.com/work/2006/08/18/learning-from-kikos-failure/</link>
		<comments>http://www.mathewingram.com/work/2006/08/18/learning-from-kikos-failure/#comments</comments>
		<pubDate>Fri, 18 Aug 2006 04:25:54 +0000</pubDate>
		<dc:creator>Mathew</dc:creator>
				<category><![CDATA[Web2.0]]></category>
		<category><![CDATA[failure]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[kiko]]></category>
		<category><![CDATA[startups]]></category>

		<guid isPermaLink="false">http://www.mathewingram.com/work/2006/08/18/learning-from-kikos-failure/</guid>
		<description><![CDATA[Just a short post to note something that I think every current or prospective Web 2.0 startup should probably read &#8212; or actually, several things, all of which are related to the demise of Kiko, an AJAX-driven online calendar that got its start in Paul Graham&#8217;s YCombinator summer camp for geeks. Kiko has effectively shut [...]]]></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%2F08%2F18%2Flearning-from-kikos-failure%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.mathewingram.com%2Fwork%2F2006%2F08%2F18%2Flearning-from-kikos-failure%2F&amp;source=mathewi&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Just a short post to note something that I think every current or prospective Web 2.0 startup should probably read &#8212; or actually, several things, all of which are related to <a href="http://www.techcrunch.com/2006/08/16/ajax-calendar-kikocom-goes-on-ebay-offers-to-delete-accounts/">the demise of Kiko</a>, an AJAX-driven online calendar that got its start in Paul Graham&#8217;s YCombinator summer camp for geeks. Kiko has effectively shut down and has put itself up for sale on eBay. The first thing worth reading is <a href="http://onstartups.com/Home/tabid/3339/articleType/ArticleView/articleId/800/Hindsight20LessonsFromAFailedWeb20Startup.aspx">a post</a> at the blog On Startups, which looks for lessons in the failure of the well-regarded calendar app.</p>
<p>The post&#8217;s lessons are not exactly rocket surgery, so to speak, but they are worth reading nevertheless &#8212; including &#8220;Google is the new Microsoft&#8221; and &#8220;Have a plan B.&#8221; Equally interesting and worthwhile, ironically (since he is critical of the On Startups post), is a post by <a href="http://www.height1percent.com/articles/2006/08/18/actual-lessons-from-kiko">one of the members</a> of the Kiko design team, who posted a comment to the On Startup blog with a link to his own version of the company&#8217;s demise. Richard White&#8217;s lessons go a little farther than the simplistic &#8220;Don&#8217;t take on Google&#8221; &#8212; he notes that the day <a href="http://calendar.google.com">Google&#8217;s calendar</a> launched was actually one of the highest traffic days for Kiko, because all the stories mentioned it.</p>
<p>Among other things, Richard (whose post has a comment from Narendra Rocherolle of competitor 30boxes) notes that Kiko lost its focus at a crucial time and thus its launch was delayed &#8212; allowing 30boxes and Google to grab more of the spotlight &#8212; and that the team tried to make the app a little too feature-rich. Kiko co-founder Justin Tan also has <a href="http://jkanstyle.com/2006/08/17/actual-lessons-from-kiko/">a post-mortem</a> in which he mentions staying focused, and argues that an online calendar is a worthwhile thing to have and not necessarily doomed to failure (Don Dodge <a href="http://dondodge.typepad.com/the_next_big_thing/2006/08/hindsight_20_le.html">disagrees</a>). All in all, definitely worth reading.</p>
<p><b>Update:</b></p>
<p>Paul Graham has his own thoughts on Kiko&#8217;s demise, which boil down to <a href="http://paulgraham.infogami.com/blog/kiko">&#8220;don&#8217;t fight Google&#8221;</a>, but David at Signal vs. Noise <a href="http://37signals.com/svn/archives2/google_does_not_render_resistance_futile.php">disagrees</a>, and Scott Karp of Publishing 2.0 says that if Google is the next Microsoft then that&#8217;s actually <a href="http://publishing2.com/2006/08/18/if-google-is-the-new-microsoft-thats-precisely-why-they-shouldnt-be-feared/">a good thing</a>. Umair at Bubblegeneration says <a href="http://www.bubblegeneration.com/2006/08/industry-note-put-your-20-where-your.cfm">not to cry</a> for Kiko.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mathewingram.com/work/2006/08/18/learning-from-kikos-failure/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

