<?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: The Case Against the Zero Inbox</title>
	<atom:link href="http://www.2time-sys.com/2008/06/09/the-case-against-the-zero-inbox/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.2time-sys.com/2008/06/09/the-case-against-the-zero-inbox/</link>
	<description>The World&#039;s Best Resource for Time Management 2.0</description>
	<lastBuildDate>Sat, 28 Jan 2012 15:44:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Summy</title>
		<link>http://www.2time-sys.com/2008/06/09/the-case-against-the-zero-inbox/#comment-546</link>
		<dc:creator>Summy</dc:creator>
		<pubDate>Sat, 21 Jun 2008 00:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.2time-sys.com/2008/06/09/the-case-against-the-zero-inbox/#comment-546</guid>
		<description>The email inbox with 16,000 messages isn&#039;t the problem as long as 
1) the tasks that are in them are tracked elsewhere
2) the information in the email is easy to reference. 

Then the person is just using their inbox as a storage devise. New email represents an item to be addressed- easy to see that. Old emails are just stored there. The key is to not mark read messages as unread then you&#039;ll get a logistical mess. 

IOn the ideal world i agree the inbox should be empty- &lt;a href=&quot;http://www.successmakingmachine.com/2008/05/09/keep-your-inbox-empty/&quot; rel=&quot;nofollow&quot;&gt;Let’s Fight: Why Don’t You Keep Your Inbox Empty?&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>The email inbox with 16,000 messages isn&#8217;t the problem as long as<br />
1) the tasks that are in them are tracked elsewhere<br />
2) the information in the email is easy to reference. </p>
<p>Then the person is just using their inbox as a storage devise. New email represents an item to be addressed- easy to see that. Old emails are just stored there. The key is to not mark read messages as unread then you&#8217;ll get a logistical mess. </p>
<p>IOn the ideal world i agree the inbox should be empty- <a href="http://www.successmakingmachine.com/2008/05/09/keep-your-inbox-empty/" rel="nofollow">Let’s Fight: Why Don’t You Keep Your Inbox Empty?</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Barnes</title>
		<link>http://www.2time-sys.com/2008/06/09/the-case-against-the-zero-inbox/#comment-437</link>
		<dc:creator>Stephen Barnes</dc:creator>
		<pubDate>Tue, 10 Jun 2008 03:07:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.2time-sys.com/2008/06/09/the-case-against-the-zero-inbox/#comment-437</guid>
		<description>QUOTE:

Instead, emails with the following attributes are the ones that cause me the most trouble:

1) they require some further thought before I decide what to do

2) they have important information that must be stored

3) they must be scheduled into my calendar for a convenient future moment of time

4) they have data that must be added to a list of items

5) they need to be married to some other information before action is possible (this category is especially troublesome!)

RESPONSE

Francis - you are right on the money here. At Orla in Australia we figured this out and built a product which squarely addresses this issue. All the other (respected) commentators are effectively shuffling the deck chairs on the Titanic. Solving the email problem is not hard at all, when you know how and have the tools to get the job done.

Cheers</description>
		<content:encoded><![CDATA[<p>QUOTE:</p>
<p>Instead, emails with the following attributes are the ones that cause me the most trouble:</p>
<p>1) they require some further thought before I decide what to do</p>
<p>2) they have important information that must be stored</p>
<p>3) they must be scheduled into my calendar for a convenient future moment of time</p>
<p>4) they have data that must be added to a list of items</p>
<p>5) they need to be married to some other information before action is possible (this category is especially troublesome!)</p>
<p>RESPONSE</p>
<p>Francis &#8211; you are right on the money here. At Orla in Australia we figured this out and built a product which squarely addresses this issue. All the other (respected) commentators are effectively shuffling the deck chairs on the Titanic. Solving the email problem is not hard at all, when you know how and have the tools to get the job done.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>

