<?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"
	>
<channel>
	<title>Comments on: Anatomy Of A Failure: Lessons Learned</title>
	<atom:link href="http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/</link>
	<description>Startup and Technology News</description>
	<pubDate>Fri, 05 Sep 2008 05:37:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Applying "The Tipping Point" Principles to Mobile Internet Strategy &#124; Achieve Market Leadership</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2452188</link>
		<dc:creator>Applying "The Tipping Point" Principles to Mobile Internet Strategy &#124; Achieve Market Leadership</dc:creator>
		<pubDate>Mon, 01 Sep 2008 01:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2452188</guid>
		<description>[...] to Esme Vos, I saw this thoughtful  post-mortem on the demise of Meetro.com, and realized it was an interesting test of the tipping point [...]</description>
		<content:encoded><![CDATA[<p>[...] to Esme Vos, I saw this thoughtful  post-mortem on the demise of Meetro.com, and realized it was an interesting test of the tipping point [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ghpljtecf zjwx</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2379672</link>
		<dc:creator>ghpljtecf zjwx</dc:creator>
		<pubDate>Thu, 19 Jun 2008 09:37:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2379672</guid>
		<description>hkcvtebdw xdsqpw aqkfdht svtwex nljk lgbzixew ikqbcp</description>
		<content:encoded><![CDATA[<p>hkcvtebdw xdsqpw aqkfdht svtwex nljk lgbzixew ikqbcp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: One User a Day</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2331092</link>
		<dc:creator>One User a Day</dc:creator>
		<pubDate>Tue, 27 May 2008 16:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2331092</guid>
		<description>Seven days after this post, Kleiner's picks Whrrl for the Killer iPhone App fund. Whrrl is based on location, which was the same reason that Meetro went belly-up.  We'll see what Kleiner, the iPhone, and Whrrl have up their sleeves.</description>
		<content:encoded><![CDATA[<p>Seven days after this post, Kleiner&#8217;s picks Whrrl for the Killer iPhone App fund. Whrrl is based on location, which was the same reason that Meetro went belly-up.  We&#8217;ll see what Kleiner, the iPhone, and Whrrl have up their sleeves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Walsh</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2330402</link>
		<dc:creator>Paul Walsh</dc:creator>
		<pubDate>Tue, 27 May 2008 10:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2330402</guid>
		<description>I like to see people articulate their failures, thanks Mike. If we see this type of post again, could we ask the CEO to share his lessons with respect to the people-mistakes - i.e. business related and not just product focused. 

This posts is more meaningful to people focused on this type of product. If I'm honest, anyone with good mobile experience will know that reliance on Carriers is almost detrimental to any business - at least that's understood in Europe - especially in the UK, where mobile is more advanced than most countries. LBS has never taken off as it's prohibitively expensive to use the data from Carriers. The next best thing is Google's database - it's not readily available but it's easy to hack and I hear it'll be given for free quite soon.</description>
		<content:encoded><![CDATA[<p>I like to see people articulate their failures, thanks Mike. If we see this type of post again, could we ask the CEO to share his lessons with respect to the people-mistakes - i.e. business related and not just product focused. </p>
<p>This posts is more meaningful to people focused on this type of product. If I&#8217;m honest, anyone with good mobile experience will know that reliance on Carriers is almost detrimental to any business - at least that&#8217;s understood in Europe - especially in the UK, where mobile is more advanced than most countries. LBS has never taken off as it&#8217;s prohibitively expensive to use the data from Carriers. The next best thing is Google&#8217;s database - it&#8217;s not readily available but it&#8217;s easy to hack and I hear it&#8217;ll be given for free quite soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: THINK / Musings :: Compacting connections</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2328584</link>
		<dc:creator>THINK / Musings :: Compacting connections</dc:creator>
		<pubDate>Mon, 26 May 2008 16:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2328584</guid>
		<description>[...] article by the founder of Meetro about what he learned from his startup experience. &#160; Intrigued by the [...]</description>
		<content:encoded><![CDATA[<p>[...] article by the founder of Meetro about what he learned from his startup experience. &nbsp; Intrigued by the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RenaLId.com :: Revue du Geoweb de la semaine</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2327355</link>
		<dc:creator>RenaLId.com :: Revue du Geoweb de la semaine</dc:creator>
		<pubDate>Mon, 26 May 2008 06:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2327355</guid>
		<description>[...] de l&#8217;échec d&#8217;une startup autour de la géolocalisation Baliz-Media a remonté un article de TechCrunch qui relate les déboirs d&#8217;un créateur d&#8217;une startup, Meetro, service communautaire [...]</description>
		<content:encoded><![CDATA[<p>[...] de l&#8217;échec d&#8217;une startup autour de la géolocalisation Baliz-Media a remonté un article de TechCrunch qui relate les déboirs d&#8217;un créateur d&#8217;une startup, Meetro, service communautaire [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ralph Buchfelder</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2322812</link>
		<dc:creator>Ralph Buchfelder</dc:creator>
		<pubDate>Fri, 23 May 2008 22:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2322812</guid>
		<description>oops. forgot to say that i'm a geographer - but none of our users except for some sophisticated and savvy uses the maps themselves...</description>
		<content:encoded><![CDATA[<p>oops. forgot to say that i&#8217;m a geographer - but none of our users except for some sophisticated and savvy uses the maps themselves&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ralph Buchfelder</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2322784</link>
		<dc:creator>Ralph Buchfelder</dc:creator>
		<pubDate>Fri, 23 May 2008 22:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2322784</guid>
		<description>Paul, thanks for sharing this with us!

After having read through your comments, i'd like to sum what's been negatively addressed by most of you:
- lack of market research
- offer solutions for real problems / need at the customer's side
- gather some evolved management, partners and experiences internationally
- missing business case/ revenue i.e. idea before technology
- location is just a feature, not a product

Well, this is general saying as consultants do. But even in 2008 if you did everything of the above alright you would be facing Paul's drawbacks. 
In particular - at early-stage you won't find that much data about potential usage and revenues. And hell, everybody wants to come along with Myspace, no?
Furthermore I don't want some experienced guys get into my boat (we are doing location-aware apps too) and let them tell me the same old story as back then in 1999. I can almost raise this knowledge in 6-12 months on my very own when dealing with these beloved "location-aware circumstances". In the end I will find myself stuck in deep water just as the big CEOs out there.. the big difference:..what i cannot do is mixed financing :/

For the [location specific] rest, Paul's issues come handy.

By the way: Anyone, tell me how to make it absolutely viral ;) ...and yeah, give me an exclusive free access to that huge Google GSM Cell-ID Databases or i will have to wait for carriers or crowdsourcing (Yahoo Zone Tag, Celldb.org, gsmloc.org, cellspotting.com, opencellid.org...) to make my day!

Fore those of you who like the buzz around location based services (lbs)...

Hype vs.Reality of Location-Based Services - LBS at the end of 2001
http://lbs360.directionsmag.com/articles/index.php?article_id=144

LBS: Turning Corners in 2003
http://lbs360.directionsmag.com/articles/index.php?article_id=296

The Outlook for Location-based Services – 2006 and Beyond
http://www.directionsmag.com/article.php?article_id=2111&#38;trv=1

I will do the 2009 edition of these articles ;)</description>
		<content:encoded><![CDATA[<p>Paul, thanks for sharing this with us!</p>
<p>After having read through your comments, i&#8217;d like to sum what&#8217;s been negatively addressed by most of you:<br />
- lack of market research<br />
- offer solutions for real problems / need at the customer&#8217;s side<br />
- gather some evolved management, partners and experiences internationally<br />
- missing business case/ revenue i.e. idea before technology<br />
- location is just a feature, not a product</p>
<p>Well, this is general saying as consultants do. But even in 2008 if you did everything of the above alright you would be facing Paul&#8217;s drawbacks.<br />
In particular - at early-stage you won&#8217;t find that much data about potential usage and revenues. And hell, everybody wants to come along with Myspace, no?<br />
Furthermore I don&#8217;t want some experienced guys get into my boat (we are doing location-aware apps too) and let them tell me the same old story as back then in 1999. I can almost raise this knowledge in 6-12 months on my very own when dealing with these beloved &#8220;location-aware circumstances&#8221;. In the end I will find myself stuck in deep water just as the big CEOs out there.. the big difference:..what i cannot do is mixed financing :/</p>
<p>For the [location specific] rest, Paul&#8217;s issues come handy.</p>
<p>By the way: Anyone, tell me how to make it absolutely viral <img src='http://www.techcrunch.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> &#8230;and yeah, give me an exclusive free access to that huge Google GSM Cell-ID Databases or i will have to wait for carriers or crowdsourcing (Yahoo Zone Tag, Celldb.org, gsmloc.org, cellspotting.com, opencellid.org&#8230;) to make my day!</p>
<p>Fore those of you who like the buzz around location based services (lbs)&#8230;</p>
<p>Hype vs.Reality of Location-Based Services - LBS at the end of 2001<br />
<a href="http://lbs360.directionsmag.com/articles/index.php?article_id=144" rel="nofollow">http://lbs360.directionsmag.co.....cle_id=144</a></p>
<p>LBS: Turning Corners in 2003<br />
<a href="http://lbs360.directionsmag.com/articles/index.php?article_id=296" rel="nofollow">http://lbs360.directionsmag.co.....cle_id=296</a></p>
<p>The Outlook for Location-based Services – 2006 and Beyond<br />
<a href="http://www.directionsmag.com/article.php?article_id=2111&amp;trv=1" rel="nofollow">http://www.directionsmag.com/a.....&amp;trv=1</a></p>
<p>I will do the 2009 edition of these articles <img src='http://www.techcrunch.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Eisenstadt</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2318595</link>
		<dc:creator>Marc Eisenstadt</dc:creator>
		<pubDate>Thu, 22 May 2008 12:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2318595</guid>
		<description>...oops seems the comma got either mis-typed or mis-parsed into the URL in the previous posting... of course it's www.clustrmaps.com</description>
		<content:encoded><![CDATA[<p>&#8230;oops seems the comma got either mis-typed or mis-parsed into the URL in the previous posting&#8230; of course it&#8217;s <a href="http://www.clustrmaps.com" rel="nofollow">http://www.clustrmaps.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Eisenstadt</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2318585</link>
		<dc:creator>Marc Eisenstadt</dc:creator>
		<pubDate>Thu, 22 May 2008 12:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2318585</guid>
		<description>Thanks Paul - useful stuff *EVEN IF* (a) it self-promotes Lefora (which itself looks like a fantastic and timely product, incidentally) and (b) it doesn't dig as deeply as some posters would have wanted.

Personally, I just wanted to add some related experiences we had with BuddySpace, a geolocation-meets-Jabber-IM tool that gained some traction briefly in the early 2000's (!), at least in the open source / research arena.  The dual problems of "First I had the download pain, and now I'm the only one of my friends using it, so I can't be bothered" were of course significant and stifling, *BUT* they were also treatable.  To circumvent the download pain, we eventually moved to a more modern all-AJAX style, with Google Maps integration, that has resurfaced as "MSG" (see http://msg.open.ac.uk )... of course Google Talk and others handle this niche beautifully, though without (yet) the map integration.   More importantly, to circumvent the "I'm the only one using it" problem, we found that enterprise-wide rollout could be so effective (instant critical mass), but only if we worked with organizations to give them CUSTOM maps (e.g. office maps), so everyone could 'see at a glance' where their colleages were and their online statuses.

Even so, this could well have been more of a 'feature' than a 'product', just like Meetro, and having it as academic open source meant much less pressure to create a viable business model (not zero pressure, incidentally, just LESS of it).

There's also the 'idea' vs 'execution' issue: Last year I heard a nice talk by Rashmi Sinha (of Slideshare) in which she repeated a well-known mantra that "ideas are a dime a dozen, but EXECUTION separates the winners from the losers".  It's hard to do the controlled experiment: how do you know that the execution was "great enough", even with all the awesome work that went into your obviously cool product?  A nagging thought for all of us!

On a final note, I'm keeping the geolocation banner alive with a separate startup, www.clustrmaps.com, a geolocation hit counter widget which does one thing simply, showing impossibly many visitors in an impossibly small space, all impossibly fast - creating a nice 'gestalt'.  Check it out - fits well with Lefora! ;-)   Best of luck, too....

-Marc</description>
		<content:encoded><![CDATA[<p>Thanks Paul - useful stuff *EVEN IF* (a) it self-promotes Lefora (which itself looks like a fantastic and timely product, incidentally) and (b) it doesn&#8217;t dig as deeply as some posters would have wanted.</p>
<p>Personally, I just wanted to add some related experiences we had with BuddySpace, a geolocation-meets-Jabber-IM tool that gained some traction briefly in the early 2000&#8217;s (!), at least in the open source / research arena.  The dual problems of &#8220;First I had the download pain, and now I&#8217;m the only one of my friends using it, so I can&#8217;t be bothered&#8221; were of course significant and stifling, *BUT* they were also treatable.  To circumvent the download pain, we eventually moved to a more modern all-AJAX style, with Google Maps integration, that has resurfaced as &#8220;MSG&#8221; (see <a href="http://msg.open.ac.uk" rel="nofollow">http://msg.open.ac.uk</a> )&#8230; of course Google Talk and others handle this niche beautifully, though without (yet) the map integration.   More importantly, to circumvent the &#8220;I&#8217;m the only one using it&#8221; problem, we found that enterprise-wide rollout could be so effective (instant critical mass), but only if we worked with organizations to give them CUSTOM maps (e.g. office maps), so everyone could &#8217;see at a glance&#8217; where their colleages were and their online statuses.</p>
<p>Even so, this could well have been more of a &#8216;feature&#8217; than a &#8216;product&#8217;, just like Meetro, and having it as academic open source meant much less pressure to create a viable business model (not zero pressure, incidentally, just LESS of it).</p>
<p>There&#8217;s also the &#8216;idea&#8217; vs &#8216;execution&#8217; issue: Last year I heard a nice talk by Rashmi Sinha (of Slideshare) in which she repeated a well-known mantra that &#8220;ideas are a dime a dozen, but EXECUTION separates the winners from the losers&#8221;.  It&#8217;s hard to do the controlled experiment: how do you know that the execution was &#8220;great enough&#8221;, even with all the awesome work that went into your obviously cool product?  A nagging thought for all of us!</p>
<p>On a final note, I&#8217;m keeping the geolocation banner alive with a separate startup, <a href="http://www.clustrmaps.com" rel="nofollow">http://www.clustrmaps.com</a>, a geolocation hit counter widget which does one thing simply, showing impossibly many visitors in an impossibly small space, all impossibly fast - creating a nice &#8216;gestalt&#8217;.  Check it out - fits well with Lefora! <img src='http://www.techcrunch.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />   Best of luck, too&#8230;.</p>
<p>-Marc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Holt</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317629</link>
		<dc:creator>Andrew Holt</dc:creator>
		<pubDate>Thu, 22 May 2008 05:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317629</guid>
		<description>Good luck in all your future ventures Paul, and thanks for the write-up. I have first hand experience how frustrating it can be to move on from a really good idea and have a lot of IP got to waste.

At least you were always the most entertaining guy at TC parties :).</description>
		<content:encoded><![CDATA[<p>Good luck in all your future ventures Paul, and thanks for the write-up. I have first hand experience how frustrating it can be to move on from a really good idea and have a lot of IP got to waste.</p>
<p>At least you were always the most entertaining guy at TC parties :).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryce</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317514</link>
		<dc:creator>Bryce</dc:creator>
		<pubDate>Thu, 22 May 2008 04:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317514</guid>
		<description>it's interesting, because I was actually a tester for meetro, and really enjoyed the interface and how I could use all my clients on it. However, I actually DID live in Idaho, and that was the part where I lost interest and just didn't continue with it. 

Good luck in the future.</description>
		<content:encoded><![CDATA[<p>it&#8217;s interesting, because I was actually a tester for meetro, and really enjoyed the interface and how I could use all my clients on it. However, I actually DID live in Idaho, and that was the part where I lost interest and just didn&#8217;t continue with it. </p>
<p>Good luck in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Powell</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317466</link>
		<dc:creator>Andy Powell</dc:creator>
		<pubDate>Thu, 22 May 2008 03:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317466</guid>
		<description>Paul, thanks for sharing your experience.  As others said above, your analysis surprised me because it was nearly all product-oriented and not organizationally-oriented. That angle would be interesting as well -- was it mainly the product, as you suggest, or were there other major factors?  In any case, I wish you all the best in your future endeavors.  Don't be deterred by the armchair quarterbacks.

Michael, this is the type of material that keeps me coming back to TechCrunch.</description>
		<content:encoded><![CDATA[<p>Paul, thanks for sharing your experience.  As others said above, your analysis surprised me because it was nearly all product-oriented and not organizationally-oriented. That angle would be interesting as well &#8212; was it mainly the product, as you suggest, or were there other major factors?  In any case, I wish you all the best in your future endeavors.  Don&#8217;t be deterred by the armchair quarterbacks.</p>
<p>Michael, this is the type of material that keeps me coming back to TechCrunch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SmartGuy</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317184</link>
		<dc:creator>SmartGuy</dc:creator>
		<pubDate>Wed, 21 May 2008 22:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317184</guid>
		<description>Dude, the product was useful, you just didn't get it viral. After you moved to Palo Alto, you should have engaged one of the viral experts in area, given him a big fraction of your company, and gotten your product out of millions of people. After all, 75% of something is better than 100% of nothing.</description>
		<content:encoded><![CDATA[<p>Dude, the product was useful, you just didn&#8217;t get it viral. After you moved to Palo Alto, you should have engaged one of the viral experts in area, given him a big fraction of your company, and gotten your product out of millions of people. After all, 75% of something is better than 100% of nothing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EvilLaugh</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317069</link>
		<dc:creator>EvilLaugh</dc:creator>
		<pubDate>Wed, 21 May 2008 21:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2317069</guid>
		<description>Whatever.  Another hero with ideas of self-aggrandizement and...a...dumb...idea.  Following the mis-adventures of the Meetro HQ team (remember bowling nights?) was a hell of a lot more entertaining and useful than the product.

And the 'google is about to buy us' rumor started by these guys?  Genius.

Remember the movie startup.com?  As painful to watch as it was to read this and you could see the ultimate outcome a mile away.  Anybody legit tech business who met either eGov or meetro could have told them that this what was going to happen to the.</description>
		<content:encoded><![CDATA[<p>Whatever.  Another hero with ideas of self-aggrandizement and&#8230;a&#8230;dumb&#8230;idea.  Following the mis-adventures of the Meetro HQ team (remember bowling nights?) was a hell of a lot more entertaining and useful than the product.</p>
<p>And the &#8216;google is about to buy us&#8217; rumor started by these guys?  Genius.</p>
<p>Remember the movie startup.com?  As painful to watch as it was to read this and you could see the ultimate outcome a mile away.  Anybody legit tech business who met either eGov or meetro could have told them that this what was going to happen to the.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Échec d’une startup en LBS : Leçons à retenir &#124; BALIZ-MEDIA.com</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316923</link>
		<dc:creator>Échec d’une startup en LBS : Leçons à retenir &#124; BALIZ-MEDIA.com</dc:creator>
		<pubDate>Wed, 21 May 2008 20:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316923</guid>
		<description>[...] de Meetro, un réseau social basé sur la géolocalisation, offre dans un long billet publié sur Techcrunch (en anglais) une réflexion enrichissante sur le contexte et les raisons qui ont mené son projet [...]</description>
		<content:encoded><![CDATA[<p>[...] de Meetro, un réseau social basé sur la géolocalisation, offre dans un long billet publié sur Techcrunch (en anglais) une réflexion enrichissante sur le contexte et les raisons qui ont mené son projet [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Schlenker</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316886</link>
		<dc:creator>Steve Schlenker</dc:creator>
		<pubDate>Wed, 21 May 2008 19:51:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316886</guid>
		<description>One observation, Paul.  Sometimes it makes sense to see what is being done outside of the US to see if there are learnings you can take to a US based company

  Circa 2001 there was a company in Cambridge UK called Apama.  Great technology for mobile location tracking - basically they could simultaneously track several hundred thousand cell phones and determine who was the closest to you fitting certain pre-determined characteristics that were along the lines of social networking / on-line dating (age, gender, availability, etc).  They in turn were trying to copy what had been successful with some similar applications in Korea, but with weaker technology and focused on smaller numbes of cell phones (application for meeting people in bars and restaurants).

  Apama found out very quickly that Western consumers were really not that interested in mobile location-based dating or location-based communications - this was very much a Southeast Asian cultural pattern.

 So they morphed their great technology into a trading platform (what stocks are closest to your target strike price to) and ended up shelving the mobile business and selling it for a nice valuation as an algorithmic trading platform.

 My point is simple - while Meetro may have been an early player in the US, there were other examples elsewhere in the world.  By 2006 you could have contacted the founder/CEO of Apama (John Bates) and had a good chat over his learnings, which you in turn could have applied into perhaps refocusing your business in a way that would have had a happier ending.

 It is very easy to look at what is happening in the US technology space in isolation, but in certain sectors, particularly mobile applications, one must have a broader worldview or you are discarding a lot of valuable experience, which is another way of saying you will need to spend more of your limited external funding than you otherwise need to on things not directly leading to sustainable cash flow.</description>
		<content:encoded><![CDATA[<p>One observation, Paul.  Sometimes it makes sense to see what is being done outside of the US to see if there are learnings you can take to a US based company</p>
<p>  Circa 2001 there was a company in Cambridge UK called Apama.  Great technology for mobile location tracking - basically they could simultaneously track several hundred thousand cell phones and determine who was the closest to you fitting certain pre-determined characteristics that were along the lines of social networking / on-line dating (age, gender, availability, etc).  They in turn were trying to copy what had been successful with some similar applications in Korea, but with weaker technology and focused on smaller numbes of cell phones (application for meeting people in bars and restaurants).</p>
<p>  Apama found out very quickly that Western consumers were really not that interested in mobile location-based dating or location-based communications - this was very much a Southeast Asian cultural pattern.</p>
<p> So they morphed their great technology into a trading platform (what stocks are closest to your target strike price to) and ended up shelving the mobile business and selling it for a nice valuation as an algorithmic trading platform.</p>
<p> My point is simple - while Meetro may have been an early player in the US, there were other examples elsewhere in the world.  By 2006 you could have contacted the founder/CEO of Apama (John Bates) and had a good chat over his learnings, which you in turn could have applied into perhaps refocusing your business in a way that would have had a happier ending.</p>
<p> It is very easy to look at what is happening in the US technology space in isolation, but in certain sectors, particularly mobile applications, one must have a broader worldview or you are discarding a lot of valuable experience, which is another way of saying you will need to spend more of your limited external funding than you otherwise need to on things not directly leading to sustainable cash flow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: www.ryankuder.com</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316798</link>
		<dc:creator>www.ryankuder.com</dc:creator>
		<pubDate>Wed, 21 May 2008 19:06:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316798</guid>
		<description>&lt;strong&gt;When Companies Die&#8230;...&lt;/strong&gt;

Paul Bragiel from Meetro posted a detailed post-mortem on the demise of Meetro.  Meetro is, er&#8230;was, a location service that would figure out where you are and introduce you to people nearby.  Brightkite is currently working in this space and se...</description>
		<content:encoded><![CDATA[<p><strong>When Companies Die&#8230;&#8230;</strong></p>
<p>Paul Bragiel from Meetro posted a detailed post-mortem on the demise of Meetro.  Meetro is, er&#8230;was, a location service that would figure out where you are and introduce you to people nearby.  Brightkite is currently working in this space and se&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anatoly</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316781</link>
		<dc:creator>Anatoly</dc:creator>
		<pubDate>Wed, 21 May 2008 18:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316781</guid>
		<description>Wow David K. Thats a little harsh, I could take a similar attitude towards your comment. 

I find comments like this above really amusing, because they have really nothing much to say. Its the commenters version of "move along, nothing to see here".

Here's the comment I want to see from such a commenter: "".</description>
		<content:encoded><![CDATA[<p>Wow David K. Thats a little harsh, I could take a similar attitude towards your comment. </p>
<p>I find comments like this above really amusing, because they have really nothing much to say. Its the commenters version of &#8220;move along, nothing to see here&#8221;.</p>
<p>Here&#8217;s the comment I want to see from such a commenter: &#8220;&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gumption</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316674</link>
		<dc:creator>Gumption</dc:creator>
		<pubDate>Wed, 21 May 2008 18:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316674</guid>
		<description>&lt;strong&gt;The Challenges of Location-Based Social Networking...&lt;/strong&gt;

Meetro, the location-aware instant messaging application - and company - has failed (or as my entrepreneur friends often like to say in such cases, it has "run out of runway"). Peter sent me a link to an inspiring TechCrunch guest post by Paul Bragie...</description>
		<content:encoded><![CDATA[<p><strong>The Challenges of Location-Based Social Networking&#8230;</strong></p>
<p>Meetro, the location-aware instant messaging application - and company - has failed (or as my entrepreneur friends often like to say in such cases, it has &#8220;run out of runway&#8221;). Peter sent me a link to an inspiring TechCrunch guest post by Paul Bragie&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David K.</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316659</link>
		<dc:creator>David K.</dc:creator>
		<pubDate>Wed, 21 May 2008 18:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316659</guid>
		<description>I find these "post-mortems" for failed start-ups quite amusing.  It's like one final shot at validating a failure because, god knows, they didn't REALLY fail!  

Same scenario in this article:  "If we had done a, b and c instead of x, y and z, THEN we would have been successful...and happy...and driving around in our new Teslas.  And oh, by the way...we really COULD HAVE fixed things, but by then we were so busy on our much cooler new projects, we just didn't care."

It's the start-up's version of, "move along, nothing to see here" that attempts to absolve those who blew the money of any guilt.

Here's the article I want to see from the former CEO of a failed startup:  "EPIC FAIL.  The end."</description>
		<content:encoded><![CDATA[<p>I find these &#8220;post-mortems&#8221; for failed start-ups quite amusing.  It&#8217;s like one final shot at validating a failure because, god knows, they didn&#8217;t REALLY fail!  </p>
<p>Same scenario in this article:  &#8220;If we had done a, b and c instead of x, y and z, THEN we would have been successful&#8230;and happy&#8230;and driving around in our new Teslas.  And oh, by the way&#8230;we really COULD HAVE fixed things, but by then we were so busy on our much cooler new projects, we just didn&#8217;t care.&#8221;</p>
<p>It&#8217;s the start-up&#8217;s version of, &#8220;move along, nothing to see here&#8221; that attempts to absolve those who blew the money of any guilt.</p>
<p>Here&#8217;s the article I want to see from the former CEO of a failed startup:  &#8220;EPIC FAIL.  The end.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddie</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316642</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Wed, 21 May 2008 18:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316642</guid>
		<description>I'm surprised nobody has mentioned Fire Eagle (http://developer.yahoo.com/fireeagle) yet.  This is a user location broker that lets users update their current location so that trusted applications can use it.  This separates the tasks of importing users' location from the tasks of mining those locations in a location-aware application.</description>
		<content:encoded><![CDATA[<p>I&#8217;m surprised nobody has mentioned Fire Eagle (http://developer.yahoo.com/fireeagle) yet.  This is a user location broker that lets users update their current location so that trusted applications can use it.  This separates the tasks of importing users&#8217; location from the tasks of mining those locations in a location-aware application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316550</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 21 May 2008 17:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316550</guid>
		<description>Paul,

Thanks for sharing....it's hard to do when a venture didn't turn out as planned.  I'm always amazed at the number of "experts" who come out with their mean-spirited critiques.....wish they had the cojones to identify themselves (and let us all know how many times they had actually started a business!

I want to shout out to #26; who I think makes a great point that the common interest comes first - then the location and "finder".  Of course this is easy for me to say as I am starting a business based on knowing where millions of passionate, like-minded people will be...people who WANT to find each other.  So ideas such as Meetro will be a terrific add-on for me.</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>Thanks for sharing&#8230;.it&#8217;s hard to do when a venture didn&#8217;t turn out as planned.  I&#8217;m always amazed at the number of &#8220;experts&#8221; who come out with their mean-spirited critiques&#8230;..wish they had the cojones to identify themselves (and let us all know how many times they had actually started a business!</p>
<p>I want to shout out to #26; who I think makes a great point that the common interest comes first - then the location and &#8220;finder&#8221;.  Of course this is easy for me to say as I am starting a business based on knowing where millions of passionate, like-minded people will be&#8230;people who WANT to find each other.  So ideas such as Meetro will be a terrific add-on for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blah</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316381</link>
		<dc:creator>blah</dc:creator>
		<pubDate>Wed, 21 May 2008 16:37:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316381</guid>
		<description>Thanks for the post, Paul. Definitely good for any startup to hear just the experience of living a full life cycle of (most) startups.

And to see that there is life after startup death is so important to hear. Makes you fear it less.

The 1st 2 comments stunk. If you didn't get anything out of it, that's cool. But why say that you didn't. How does that benefit anything?

Anyway, props to Paul for not going quietly.</description>
		<content:encoded><![CDATA[<p>Thanks for the post, Paul. Definitely good for any startup to hear just the experience of living a full life cycle of (most) startups.</p>
<p>And to see that there is life after startup death is so important to hear. Makes you fear it less.</p>
<p>The 1st 2 comments stunk. If you didn&#8217;t get anything out of it, that&#8217;s cool. But why say that you didn&#8217;t. How does that benefit anything?</p>
<p>Anyway, props to Paul for not going quietly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Edic</title>
		<link>http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316240</link>
		<dc:creator>Martin Edic</dc:creator>
		<pubDate>Wed, 21 May 2008 15:57:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcrunch.com/2008/05/20/anatomy-of-a-failure-lessons-learned/#comment-2316240</guid>
		<description>I can sum this up in a lot more concise manner:
Impossible to scale, no revenue model (he doesn't even mention revenue!).
I wish you'd start asking these companies how they are going to make money.
And think about this- with geo-location on iPhone couldn't you easily build something similar and have an instant installed base of users?

Businesses are not businesses unless they make money (That's the IRS speaking, not me).</description>
		<content:encoded><![CDATA[<p>I can sum this up in a lot more concise manner:<br />
Impossible to scale, no revenue model (he doesn&#8217;t even mention revenue!).<br />
I wish you&#8217;d start asking these companies how they are going to make money.<br />
And think about this- with geo-location on iPhone couldn&#8217;t you easily build something similar and have an instant installed base of users?</p>
<p>Businesses are not businesses unless they make money (That&#8217;s the IRS speaking, not me).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.128 seconds -->
