<?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: Looking at those monsters in the closet</title>
	<atom:link href="http:///2009/09/22/looking-at-those-monsters-in-the-closet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/</link>
	<description>The Hub for All Things GTD</description>
	<lastBuildDate>Wed, 10 Mar 2010 17:55:12 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jesse Wilson</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3210</link>
		<dc:creator>Jesse Wilson</dc:creator>
		<pubDate>Wed, 07 Oct 2009 17:39:08 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3210</guid>
		<description>I&#039;m finding two problems with my next action lists cause my eyes to glaze over when I look at them.

1) Too often, when I go to do a next action, I find out it will take much more effort, and it explodes into a project. Should I have planned ahead more thoroughly? Should I just transfer it to the projects list, plan, and identify a next action from there? How then can I keep projects from exploding into subprojects and subsubprojects?

2) I skip over too many next action items, because I have other projects with approaching deadlines. Should I just toss these low-priority action items in a tickler file or on my calendar to look at later?</description>
		<content:encoded><![CDATA[<p>I&#8217;m finding two problems with my next action lists cause my eyes to glaze over when I look at them.</p>
<p>1) Too often, when I go to do a next action, I find out it will take much more effort, and it explodes into a project. Should I have planned ahead more thoroughly? Should I just transfer it to the projects list, plan, and identify a next action from there? How then can I keep projects from exploding into subprojects and subsubprojects?</p>
<p>2) I skip over too many next action items, because I have other projects with approaching deadlines. Should I just toss these low-priority action items in a tickler file or on my calendar to look at later?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3159</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Thu, 24 Sep 2009 18:50:03 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3159</guid>
		<description>Bruce:
I would try to use a project list for your list of subsequent next actions and refer to it when you get the &quot;actual&quot; next action done - it keeps your next action list clearer but allows you to hold further points of action elsewhere without being concerned that you might forget them.  I am trying a system of using 1 record card per project to allow me to list a number of actions related to the project without cluttering my real next action list.  However, I am in the very early stages with it so am not yet certain how this will play out...
I hope that this is helpful.</description>
		<content:encoded><![CDATA[<p>Bruce:<br />
I would try to use a project list for your list of subsequent next actions and refer to it when you get the &#8220;actual&#8221; next action done &#8211; it keeps your next action list clearer but allows you to hold further points of action elsewhere without being concerned that you might forget them.  I am trying a system of using 1 record card per project to allow me to list a number of actions related to the project without cluttering my real next action list.  However, I am in the very early stages with it so am not yet certain how this will play out&#8230;<br />
I hope that this is helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Diaz</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3158</link>
		<dc:creator>Bruce Diaz</dc:creator>
		<pubDate>Thu, 24 Sep 2009 16:24:20 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3158</guid>
		<description>I have a tactical question re: level of detail on the task list.  The example above talked about &quot;Rewrite the report&quot; as an appropriate next action vs &quot;Book Meeting&quot;.  My challenge is my list gets too detailed / cumbersome because I think of all sorts of subsequent tasks (e.g., &quot;Book Meeting&quot;) and put them on my list in advance.  this results in my list getting very long and burdonsome.  Would it be preferred to ONLY list the next action (e.g., &quot;rewrite the report&quot;) and trust that I will remember / add subsequent steps once the fuirst step is complete?  Is that the preferred technique?</description>
		<content:encoded><![CDATA[<p>I have a tactical question re: level of detail on the task list.  The example above talked about &#8220;Rewrite the report&#8221; as an appropriate next action vs &#8220;Book Meeting&#8221;.  My challenge is my list gets too detailed / cumbersome because I think of all sorts of subsequent tasks (e.g., &#8220;Book Meeting&#8221;) and put them on my list in advance.  this results in my list getting very long and burdonsome.  Would it be preferred to ONLY list the next action (e.g., &#8220;rewrite the report&#8221;) and trust that I will remember / add subsequent steps once the fuirst step is complete?  Is that the preferred technique?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Muralidharan Jayaram</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3155</link>
		<dc:creator>Muralidharan Jayaram</dc:creator>
		<pubDate>Thu, 24 Sep 2009 05:41:04 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3155</guid>
		<description>Even if you do weekly reviews without fail, you will still have a huge list, if you do not act upon them. 

Over period of time you will have giant lists of next actions, and projects that will drain your energy. 

You cannot afford to forget why you made the list in the first place-to act upon it.</description>
		<content:encoded><![CDATA[<p>Even if you do weekly reviews without fail, you will still have a huge list, if you do not act upon them. </p>
<p>Over period of time you will have giant lists of next actions, and projects that will drain your energy. </p>
<p>You cannot afford to forget why you made the list in the first place-to act upon it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lynn O'Connor</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3154</link>
		<dc:creator>Lynn O'Connor</dc:creator>
		<pubDate>Thu, 24 Sep 2009 03:58:36 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3154</guid>
		<description>About a month ago I faced it, my lists were getting &quot;stale,&quot; I was not paying careful attention to them. Oh I&#039;d do some mini review a few times a week, but it was &quot;in one ear and out the other.&quot; I considered this a technical problem (what I consider most of my problems), and when I have a technical problem, I look for a technical solution. 

I knew I had to take every item on my lists (collection again), review it for currency etc, and then put it elsewhere. If my eyes were fuzzing over on Vitalist which I&#039;d used for a few years, it was time for a change. I needed something new, a novel visual experience. I began using Omnifocus,  and my technical solution has worked like a charm. Furthermore, its a cool program. Now for the icing on the cake --I have a new seminar of doctoral students starting up. I now include time management/organizational training part of the curriculum for my third year students. At our first seminar meeting I handed out a copy of D. Allen Getting Things Done to each student, and told them to read the first section, for discussion last evening. Re-reading with a bunch of graduate students who think they are more burdened with work than anyone else in the world --perfect timing for me. Between that and Omnifocus, my lists look fresh, I remember some of those basic exercises I&#039;d forgotten about, and suddenly things are almost effortlessly getting done.</description>
		<content:encoded><![CDATA[<p>About a month ago I faced it, my lists were getting &#8220;stale,&#8221; I was not paying careful attention to them. Oh I&#8217;d do some mini review a few times a week, but it was &#8220;in one ear and out the other.&#8221; I considered this a technical problem (what I consider most of my problems), and when I have a technical problem, I look for a technical solution. </p>
<p>I knew I had to take every item on my lists (collection again), review it for currency etc, and then put it elsewhere. If my eyes were fuzzing over on Vitalist which I&#8217;d used for a few years, it was time for a change. I needed something new, a novel visual experience. I began using Omnifocus,  and my technical solution has worked like a charm. Furthermore, its a cool program. Now for the icing on the cake &#8211;I have a new seminar of doctoral students starting up. I now include time management/organizational training part of the curriculum for my third year students. At our first seminar meeting I handed out a copy of D. Allen Getting Things Done to each student, and told them to read the first section, for discussion last evening. Re-reading with a bunch of graduate students who think they are more burdened with work than anyone else in the world &#8211;perfect timing for me. Between that and Omnifocus, my lists look fresh, I remember some of those basic exercises I&#8217;d forgotten about, and suddenly things are almost effortlessly getting done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vivian</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3153</link>
		<dc:creator>Vivian</dc:creator>
		<pubDate>Thu, 24 Sep 2009 01:05:22 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3153</guid>
		<description>Thomas, I would love to hear more about your cleaned-up WR — I have the same tendency to try and do too much in one sitting!</description>
		<content:encoded><![CDATA[<p>Thomas, I would love to hear more about your cleaned-up WR — I have the same tendency to try and do too much in one sitting!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd V</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3152</link>
		<dc:creator>Todd V</dc:creator>
		<pubDate>Wed, 23 Sep 2009 19:42:34 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3152</guid>
		<description>Lists are also designed to help show the relationships that exist between each of the items in the list. As a result, the mind can often be steered by lists into categorizing, prioritizing, organizing rather than doing. 

Just taking a 3x5 card to look at each item one-at-a-time can be a big help to getting in action mode instead of thinking-mode when working your lists.</description>
		<content:encoded><![CDATA[<p>Lists are also designed to help show the relationships that exist between each of the items in the list. As a result, the mind can often be steered by lists into categorizing, prioritizing, organizing rather than doing. </p>
<p>Just taking a 3&#215;5 card to look at each item one-at-a-time can be a big help to getting in action mode instead of thinking-mode when working your lists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bert</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3151</link>
		<dc:creator>Bert</dc:creator>
		<pubDate>Wed, 23 Sep 2009 15:37:28 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3151</guid>
		<description>Just in time for Halloween.  Good advice.</description>
		<content:encoded><![CDATA[<p>Just in time for Halloween.  Good advice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Dall</title>
		<link>http://www.gtdtimes.com/2009/09/22/looking-at-those-monsters-in-the-closet/comment-page-1/#comment-3149</link>
		<dc:creator>Thomas Dall</dc:creator>
		<pubDate>Wed, 23 Sep 2009 12:08:32 +0000</pubDate>
		<guid isPermaLink="false">https://reports.davidco.com/admin1/gtdtimes/?p=2161#comment-3149</guid>
		<description>I was resisting my Weekly Review. It always took me hours.  Until it dawned on me that I had made my personal WR checklist too long, convolved and complicated (I love lists).  Now I&#039;ve cleaned it up and I&#039;ve found the energy to do the same for my projects and action lists too.  OmniFocus used to be a monster - now it&#039;s a sports car!</description>
		<content:encoded><![CDATA[<p>I was resisting my Weekly Review. It always took me hours.  Until it dawned on me that I had made my personal WR checklist too long, convolved and complicated (I love lists).  Now I&#8217;ve cleaned it up and I&#8217;ve found the energy to do the same for my projects and action lists too.  OmniFocus used to be a monster &#8211; now it&#8217;s a sports car!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
