<?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: Eight Easy Ways To Be More Productive</title>
	<atom:link href="http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/feed/" rel="self" type="application/rss+xml" />
	<link>http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/</link>
	<description>Usability, software and user experience design.</description>
	<pubDate>Fri, 05 Dec 2008 07:26:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Justin</title>
		<link>http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-231</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Thu, 02 Oct 2008 14:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-231</guid>
		<description>Thanks, Jesse. I've been very busy. Glad you liked it.

As for CMS', have you looked at Drupal?</description>
		<content:encoded><![CDATA[<p>Thanks, Jesse. I&#8217;ve been very busy. Glad you liked it.</p>
<p>As for CMS&#8217;, have you looked at Drupal?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-230</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Thu, 02 Oct 2008 04:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-230</guid>
		<description>Excellent. I see this website has gone into the world of cobwebs and stale crackers, but I still have to say that I enjoyed reading this entry. Its all very true. I like the wiki idea, but wiki's tend to err on the side of a total lack of initial structure. I arrived at this site from oddmuse.org, in my quest for a decent CMS to both organize my writing chronologically, and categorically... but the average wiki is too boilerplate for me. In an effort to be productive, I'm dealing with an imperfect starting point, and seeking something ideal. Some mix of wiki and blog would be more ideal than either of the two.

You have one, or many 'chronological views' of the content, but none of the content is inseparable from the temporality of the blog view. Underneath, its just a wiki, but on the surface, it 'looks like' a blog. Something like the recent changes page of most wiki's, but with less focus on revision history, and more focus on original/relevant content. I think I may have to end up coding this myself. So much for borrowing a wheel, for the sake of productivity.</description>
		<content:encoded><![CDATA[<p>Excellent. I see this website has gone into the world of cobwebs and stale crackers, but I still have to say that I enjoyed reading this entry. Its all very true. I like the wiki idea, but wiki&#8217;s tend to err on the side of a total lack of initial structure. I arrived at this site from oddmuse.org, in my quest for a decent CMS to both organize my writing chronologically, and categorically&#8230; but the average wiki is too boilerplate for me. In an effort to be productive, I&#8217;m dealing with an imperfect starting point, and seeking something ideal. Some mix of wiki and blog would be more ideal than either of the two.</p>
<p>You have one, or many &#8216;chronological views&#8217; of the content, but none of the content is inseparable from the temporality of the blog view. Underneath, its just a wiki, but on the surface, it &#8216;looks like&#8217; a blog. Something like the recent changes page of most wiki&#8217;s, but with less focus on revision history, and more focus on original/relevant content. I think I may have to end up coding this myself. So much for borrowing a wheel, for the sake of productivity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-172</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Mon, 10 Dec 2007 02:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-172</guid>
		<description>I forgot to ask, what's your organization structure for your personal wiki? What are the major sections/pages you use to organize it?</description>
		<content:encoded><![CDATA[<p>I forgot to ask, what&#8217;s your organization structure for your personal wiki? What are the major sections/pages you use to organize it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-171</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Mon, 10 Dec 2007 02:45:53 +0000</pubDate>
		<guid isPermaLink="false">http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-171</guid>
		<description>A highly productive colleague once shared with me his "one-touch" philosophy: "Touch a piece of paper only once." He swore that he would only touch papers, mail, work, documents on his desk once. Each time he touched something it would get done, filed or trashed. 

I think this is draconian, but it has some merits for email. For me, the best time to respond to an email is when you first look at it. 

The three exceptions to this for me are:

 (1) It requires actual work/research. (It gets scheduled.)
 (2) It requires thought. (This may not require work, but may require some intellectual energy to figure out what to do/how to respond thoughtfully.)
 (3) You were fooled by the title into thinking the email was urgent; it's not. The sender gets penalized by moving to the very bottom of the queue.</description>
		<content:encoded><![CDATA[<p>A highly productive colleague once shared with me his &#8220;one-touch&#8221; philosophy: &#8220;Touch a piece of paper only once.&#8221; He swore that he would only touch papers, mail, work, documents on his desk once. Each time he touched something it would get done, filed or trashed. </p>
<p>I think this is draconian, but it has some merits for email. For me, the best time to respond to an email is when you first look at it. </p>
<p>The three exceptions to this for me are:</p>
<p> (1) It requires actual work/research. (It gets scheduled.)<br />
 (2) It requires thought. (This may not require work, but may require some intellectual energy to figure out what to do/how to respond thoughtfully.)<br />
 (3) You were fooled by the title into thinking the email was urgent; it&#8217;s not. The sender gets penalized by moving to the very bottom of the queue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeannie</title>
		<link>http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-170</link>
		<dc:creator>Jeannie</dc:creator>
		<pubDate>Wed, 05 Dec 2007 02:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://missingfeatures.com/2007/12/03/eight-easy-ways-to-be-more-productive/#comment-170</guid>
		<description></description>
		<content:encoded><![CDATA[<br />
]]></content:encoded>
	</item>
</channel>
</rss>
