<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Seven Problems with a Someday/Maybe List — and Ways to Correct Them</title>
	<atom:link href="http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/feed/" rel="self" type="application/rss+xml" />
	<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/</link>
	<description>Thinking beyond productivity</description>
	<lastBuildDate>Thu, 10 Feb 2011 09:54:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: What You Should Do When Your Internet&#8217;s Out &#124; Lifehacker Australia</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-7383</link>
		<dc:creator>What You Should Do When Your Internet&#8217;s Out &#124; Lifehacker Australia</dc:creator>
		<pubDate>Tue, 14 Apr 2009 21:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-7383</guid>
		<description>[...] excuse to stop sighing at your tasks and take that floating, telekinetic look. What&#8217;s hanging around your someday/maybe list and needs attention? What two-minute tasks are blocked only by your mental hang-ups, and which [...]</description>
		<content:encoded><![CDATA[<p>[...] excuse to stop sighing at your tasks and take that floating, telekinetic look. What&#8217;s hanging around your someday/maybe list and needs attention? What two-minute tasks are blocked only by your mental hang-ups, and which [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GTD Dictionary: Someday/Maybe - Practical advice on personal development, productivity and GTD</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-3140</link>
		<dc:creator>GTD Dictionary: Someday/Maybe - Practical advice on personal development, productivity and GTD</dc:creator>
		<pubDate>Wed, 12 Nov 2008 16:09:28 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-3140</guid>
		<description>[...] have an interest in). However, it&#8217;s worth noting that the someday/maybe list isn&#8217;t for fantasies. Many guys I know would love to be Premiership footballers but realism and practicality has to [...]</description>
		<content:encoded><![CDATA[<p>[...] have an interest in). However, it&#8217;s worth noting that the someday/maybe list isn&#8217;t for fantasies. Many guys I know would love to be Premiership footballers but realism and practicality has to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Managing a Someday/Maybe list with Viira &#124; The BlackBerry GTD Blog</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-3010</link>
		<dc:creator>Managing a Someday/Maybe list with Viira &#124; The BlackBerry GTD Blog</dc:creator>
		<pubDate>Mon, 03 Nov 2008 19:55:53 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-3010</guid>
		<description>[...] pitfalls (like turning it into a procrastination list). Andre from Tools for Thought has posted a great article on dealing with some of the challenges and how to overcome them - an excellent read!   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] pitfalls (like turning it into a procrastination list). Andre from Tools for Thought has posted a great article on dealing with some of the challenges and how to overcome them &#8211; an excellent read!   Share and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why I Went Back to a Digital Organizer</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-2147</link>
		<dc:creator>Why I Went Back to a Digital Organizer</dc:creator>
		<pubDate>Fri, 26 Sep 2008 16:06:17 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-2147</guid>
		<description>[...] a row gives them pause, prompting them to either redefine the task, get rid of it or move it to the Someday/Maybe list. On a digital system, it&#8217;s easier to gloss over undone items, since they stay on your list [...]</description>
		<content:encoded><![CDATA[<p>[...] a row gives them pause, prompting them to either redefine the task, get rid of it or move it to the Someday/Maybe list. On a digital system, it&#8217;s easier to gloss over undone items, since they stay on your list [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EMM</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-1380</link>
		<dc:creator>EMM</dc:creator>
		<pubDate>Fri, 29 Aug 2008 14:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-1380</guid>
		<description>I generally have problems with the timeframe descriptions for the various levels in GTD. I combine visions and life purpose as one level. I have a personal statement of purpose that is really the life portion or 50K level that I review on the solstices and equinoxes. I also have well defined goals some of which are multiple decades long. The time lines of what the various levels are do not work well for me because I have projects that will take decades or even more than one lifetime and next actions that can take years. Because they are active I need to review them and also keep in mind the big picture of where that action falls in the overall scheme of things.

Below the goals level are the areas of responsibility. For me they are the logical divisions under which projects happen. I group mine in ways that make sense to me but may not follow GTD perfectly. I have focus areas of health, house, each species of animal, each major hobby and so on. 

Projects are things under that and then next actions move projects along. 

My big someday maybe list is grouped by areas of focus with all the projects for that area underneath and then a lot of those have my next actions defined. Projects themselves may not be very complex, just long or dependent on other actions or projects. 

A current example is a goal of making historically accurate garments for myself. A project under that is make a Moy gown, but projects under that one are things like weave the fabric (which has to start after I learn to weave on the new loom bought because it can do the type of fabric I want where my older loom could not) but I can&#039;t weave until I spin the yarn and I can&#039;t spin the yarn until I find the fleeces that match the archeological records. I&#039;ve been checking wool for several years and it&#039;s only this year that I finally am getting enough of the right type to be able to sell what I need too for my customers and still have some left over for me. 

So it&#039;s not a complicated pert or gantt chart type project just a long term one.  My current next action is to find 15 pounds of wool that meets the specific requirements for that item. I&#039;ve got 3 pounds located and every year I check the wool as I skirt fleeces to find more. 

A similar project I am in the middle of took 6 years to weave the fabric. Now I&#039;m getting the courage up to cut it and start sewing. :-) I figure I&#039;ve got another year or 2 on that one as I decided that I need to make a test case of the item out of commercial fabric before I cut into my handmade stuff so I added a whole &#039;nother project in front of it that I wasn&#039;t originally planning on. 

That happens a lot to me so I just document the original project on the someday maybe list and move the new one to active and go on. And that&#039;s also why I review the whole list weekly, to be sure I&#039;ve got everything and am keeping the perspective I need about why I am doing this particular project now. Also I can more easily see that if I do project A that I hadn&#039;t thought of doing now it will teach me a skill I need or set me up for projects H, I and J which in turn will make it a lot easier to do project M and N. They may not be strictly dependent projects in the traditional project management sense but they are related and linked projects.</description>
		<content:encoded><![CDATA[<p>I generally have problems with the timeframe descriptions for the various levels in GTD. I combine visions and life purpose as one level. I have a personal statement of purpose that is really the life portion or 50K level that I review on the solstices and equinoxes. I also have well defined goals some of which are multiple decades long. The time lines of what the various levels are do not work well for me because I have projects that will take decades or even more than one lifetime and next actions that can take years. Because they are active I need to review them and also keep in mind the big picture of where that action falls in the overall scheme of things.</p>
<p>Below the goals level are the areas of responsibility. For me they are the logical divisions under which projects happen. I group mine in ways that make sense to me but may not follow GTD perfectly. I have focus areas of health, house, each species of animal, each major hobby and so on. </p>
<p>Projects are things under that and then next actions move projects along. </p>
<p>My big someday maybe list is grouped by areas of focus with all the projects for that area underneath and then a lot of those have my next actions defined. Projects themselves may not be very complex, just long or dependent on other actions or projects. </p>
<p>A current example is a goal of making historically accurate garments for myself. A project under that is make a Moy gown, but projects under that one are things like weave the fabric (which has to start after I learn to weave on the new loom bought because it can do the type of fabric I want where my older loom could not) but I can&#8217;t weave until I spin the yarn and I can&#8217;t spin the yarn until I find the fleeces that match the archeological records. I&#8217;ve been checking wool for several years and it&#8217;s only this year that I finally am getting enough of the right type to be able to sell what I need too for my customers and still have some left over for me. </p>
<p>So it&#8217;s not a complicated pert or gantt chart type project just a long term one.  My current next action is to find 15 pounds of wool that meets the specific requirements for that item. I&#8217;ve got 3 pounds located and every year I check the wool as I skirt fleeces to find more. </p>
<p>A similar project I am in the middle of took 6 years to weave the fabric. Now I&#8217;m getting the courage up to cut it and start sewing. :-) I figure I&#8217;ve got another year or 2 on that one as I decided that I need to make a test case of the item out of commercial fabric before I cut into my handmade stuff so I added a whole &#8216;nother project in front of it that I wasn&#8217;t originally planning on. </p>
<p>That happens a lot to me so I just document the original project on the someday maybe list and move the new one to active and go on. And that&#8217;s also why I review the whole list weekly, to be sure I&#8217;ve got everything and am keeping the perspective I need about why I am doing this particular project now. Also I can more easily see that if I do project A that I hadn&#8217;t thought of doing now it will teach me a skill I need or set me up for projects H, I and J which in turn will make it a lot easier to do project M and N. They may not be strictly dependent projects in the traditional project management sense but they are related and linked projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andre</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-1374</link>
		<dc:creator>Andre</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-1374</guid>
		<description>&lt;i&gt;I find if I don’t put the next actions on the list when I think of them that I spend a lot of time working and defining them again. Especially for really long term items, the next actions may be complex or require specific characteristics. If I’ve spent the time to think about it I need to capture that thought or I’ll have to do it again. And when the completion of a next action can take years I need all the info about what I was doing and looking for available&lt;/i&gt;

Your long-term projects are apparently just that -- long-term projects, rather them Someday/Maybes. In GTD parlance, these would be 30,000-ft. or 40,000-ft. perspectives, spanning years rather than months. Assuming your project was to start a vineyard, you might have &quot;Monitor climate change for conditions XYZ,&quot; then migrate everything else to a 40,000-ft. list. I keep a separate, short list of these projects on lists with those elevations has headings, rather than on my weekly-reviewed project list. I review these long-term goals quarterly, or on an as-needed basis.

You&#039;re working out the right level of detail necessary to get the project off your mind. Many projects can be unstuck by working out the very next action; some require a little more brainstorming and coordination, like a mind map or an outline; a few are complex enough to require rigorous advance planning, with heavyweight tools like PERT or Gantt charts. The degree of planning needs to scale with the complexity of the project, so it sounds like you&#039;re on the right path.</description>
		<content:encoded><![CDATA[<p><i>I find if I don’t put the next actions on the list when I think of them that I spend a lot of time working and defining them again. Especially for really long term items, the next actions may be complex or require specific characteristics. If I’ve spent the time to think about it I need to capture that thought or I’ll have to do it again. And when the completion of a next action can take years I need all the info about what I was doing and looking for available</i></p>
<p>Your long-term projects are apparently just that &#8212; long-term projects, rather them Someday/Maybes. In GTD parlance, these would be 30,000-ft. or 40,000-ft. perspectives, spanning years rather than months. Assuming your project was to start a vineyard, you might have &#8220;Monitor climate change for conditions XYZ,&#8221; then migrate everything else to a 40,000-ft. list. I keep a separate, short list of these projects on lists with those elevations has headings, rather than on my weekly-reviewed project list. I review these long-term goals quarterly, or on an as-needed basis.</p>
<p>You&#8217;re working out the right level of detail necessary to get the project off your mind. Many projects can be unstuck by working out the very next action; some require a little more brainstorming and coordination, like a mind map or an outline; a few are complex enough to require rigorous advance planning, with heavyweight tools like PERT or Gantt charts. The degree of planning needs to scale with the complexity of the project, so it sounds like you&#8217;re on the right path.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J-Mo</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-1373</link>
		<dc:creator>J-Mo</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-1373</guid>
		<description>Personally, I use a paper journal for these types of things.  I think it&#039;s just the way my mind works, as I&#039;m a writer.

Rather than crossing things off/deleting, I just read back through the journal and the seeds of ideas from time to time. Sometimes, full projects grow from these seeds, sometimes not, but I have them available to me, should I decide to return to them later.

Jen M.</description>
		<content:encoded><![CDATA[<p>Personally, I use a paper journal for these types of things.  I think it&#8217;s just the way my mind works, as I&#8217;m a writer.</p>
<p>Rather than crossing things off/deleting, I just read back through the journal and the seeds of ideas from time to time. Sometimes, full projects grow from these seeds, sometimes not, but I have them available to me, should I decide to return to them later.</p>
<p>Jen M.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EMM</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-1372</link>
		<dc:creator>EMM</dc:creator>
		<pubDate>Thu, 28 Aug 2008 14:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-1372</guid>
		<description>I find if I don&#039;t put the next actions on the list when I think of them that I spend a lot of time working and defining them again. Especially for really long term items, the next actions may be complex or require specific characteristics. If I&#039;ve spent the time to think about it I need to capture that thought or I&#039;ll have to do it again. And when the completion of a next action can take years I need all the info about what I was doing and looking for available

Which plays into the fact that there are hardly any true maybe projects on my someday maybe list. They are pretty much all projects I am committed to doing or finishing or moving along but they are also ones that will take a long time or I haven&#039;t got all the pieces yet. 

Also a lot of projects are weather based so the right conditions may happen almost any time but also not happen for several years, hence the need to review them regularly. 

And a further group of projects have next actions that will take months or years to complete and the next action on my todo list under that context is actually spend x amount of time doing y. I have one project that has been active and working for 11 years now. One single next action took 6 years to complete working on it at least monthly and most of the time weekly. Another I am working on now I&#039;ve been working on the next action for it for 4 years so far and figure I&#039;ve got a few more years to go before I&#039;ll be done. The whole project is probably going to be a 20 year project before it&#039;s done.</description>
		<content:encoded><![CDATA[<p>I find if I don&#8217;t put the next actions on the list when I think of them that I spend a lot of time working and defining them again. Especially for really long term items, the next actions may be complex or require specific characteristics. If I&#8217;ve spent the time to think about it I need to capture that thought or I&#8217;ll have to do it again. And when the completion of a next action can take years I need all the info about what I was doing and looking for available</p>
<p>Which plays into the fact that there are hardly any true maybe projects on my someday maybe list. They are pretty much all projects I am committed to doing or finishing or moving along but they are also ones that will take a long time or I haven&#8217;t got all the pieces yet. </p>
<p>Also a lot of projects are weather based so the right conditions may happen almost any time but also not happen for several years, hence the need to review them regularly. </p>
<p>And a further group of projects have next actions that will take months or years to complete and the next action on my todo list under that context is actually spend x amount of time doing y. I have one project that has been active and working for 11 years now. One single next action took 6 years to complete working on it at least monthly and most of the time weekly. Another I am working on now I&#8217;ve been working on the next action for it for 4 years so far and figure I&#8217;ve got a few more years to go before I&#8217;ll be done. The whole project is probably going to be a 20 year project before it&#8217;s done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andre</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-1363</link>
		<dc:creator>Andre</dc:creator>
		<pubDate>Wed, 27 Aug 2008 15:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-1363</guid>
		<description>I&#039;d file away the details of the subsequent project in a project support folder, then create calendar entry to review it at the designated time. I only review long-term projects on either a quarterly or as-needed basis (when new information may require a change of plan), rather than weekly. I also don&#039;t put next actions on my Someday/Maybe list; only outcomes. I generally only plan out the details of a project when it&#039;s active, or I&#039;ll put the top-of-mind details on a thumbnail project plan, which I either file away or add to a Google Notebook.</description>
		<content:encoded><![CDATA[<p>I&#8217;d file away the details of the subsequent project in a project support folder, then create calendar entry to review it at the designated time. I only review long-term projects on either a quarterly or as-needed basis (when new information may require a change of plan), rather than weekly. I also don&#8217;t put next actions on my Someday/Maybe list; only outcomes. I generally only plan out the details of a project when it&#8217;s active, or I&#8217;ll put the top-of-mind details on a thumbnail project plan, which I either file away or add to a Google Notebook.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EMM</title>
		<link>http://tools-for-thought.com/2008/08/22/seven-problems-with-a-somedaymaybe-list-%e2%80%94-and-ways-to-correct-them/#comment-1362</link>
		<dc:creator>EMM</dc:creator>
		<pubDate>Wed, 27 Aug 2008 13:48:18 +0000</pubDate>
		<guid isPermaLink="false">http://tools-for-thought.com/?p=427#comment-1362</guid>
		<description>How do you handle dependent projects or ones with next actions separated in time by years or decades?

Part of why my someday maybe list is so huge is there are bunches of projects that can&#039;t be started until some other project  is done and also ones whose next actions will happen over the course of years or decades not days or weeks.</description>
		<content:encoded><![CDATA[<p>How do you handle dependent projects or ones with next actions separated in time by years or decades?</p>
<p>Part of why my someday maybe list is so huge is there are bunches of projects that can&#8217;t be started until some other project  is done and also ones whose next actions will happen over the course of years or decades not days or weeks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

