<?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: System Obituary</title>
	<atom:link href="http://www.dancingmango.com/blog/2007/06/04/system-obituary/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dancingmango.com/blog/2007/06/04/system-obituary/</link>
	<description>It's all about the human experience</description>
	<lastBuildDate>Fri, 12 Mar 2010 10:50:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Web Worker Daily &#187; Blog Archive Tip of the Week: Focusing with a Tombstone &#171;</title>
		<link>http://www.dancingmango.com/blog/2007/06/04/system-obituary/comment-page-1/#comment-29082</link>
		<dc:creator>Web Worker Daily &#187; Blog Archive Tip of the Week: Focusing with a Tombstone &#171;</dc:creator>
		<pubDate>Thu, 07 Jun 2007 18:00:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancingmango.com/blog/2007/06/04/system-obituary/#comment-29082</guid>
		<description>[...] Tip of the Week: Focusing with a&#160;Tombstone Here&#8217;s an interesting little productivity idea from dancingmango: when you&#8217;re trying to understand the successes and failures of a system, have the current users of the system write a tombstone or obituary for it. For example, I recently gave up on a particular shareware to-do application, with results that might be summarized this way: [...]</description>
		<content:encoded><![CDATA[<p>[...] Tip of the Week: Focusing with a&nbsp;Tombstone Here&#8217;s an interesting little productivity idea from dancingmango: when you&#8217;re trying to understand the successes and failures of a system, have the current users of the system write a tombstone or obituary for it. For example, I recently gave up on a particular shareware to-do application, with results that might be summarized this way: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dancingmango &#187; It&#8217;s not what you&#8217;ve done, it&#8217;s what you&#8217;ve acheived</title>
		<link>http://www.dancingmango.com/blog/2007/06/04/system-obituary/comment-page-1/#comment-28777</link>
		<dc:creator>dancingmango &#187; It&#8217;s not what you&#8217;ve done, it&#8217;s what you&#8217;ve acheived</dc:creator>
		<pubDate>Wed, 06 Jun 2007 05:47:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancingmango.com/blog/2007/06/04/system-obituary/#comment-28777</guid>
		<description>[...] This is a good way to assess where you are going in life.  It’s not so much what you’ve done, it’s more about what you’ve achieved.  Great, so you’ve written a marketing plan, you are an expert in Java, .net and Ruby on Rails.  But what have you actually achieved?  What did that marketing plan result in delivering?  Who did you delight with the applications you built in Java, .net or Ruby on Rails?  What value have you personally contributed to the world?  What would your epitaph be? [...]</description>
		<content:encoded><![CDATA[<p>[...] This is a good way to assess where you are going in life.  It’s not so much what you’ve done, it’s more about what you’ve achieved.  Great, so you’ve written a marketing plan, you are an expert in Java, .net and Ruby on Rails.  But what have you actually achieved?  What did that marketing plan result in delivering?  Who did you delight with the applications you built in Java, .net or Ruby on Rails?  What value have you personally contributed to the world?  What would your epitaph be? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
