<?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: GTD Seminar</title>
	<atom:link href="http://poojanblog.com/blog/2009/05/gtd-seminar/feed/" rel="self" type="application/rss+xml" />
	<link>http://poojanblog.com/blog/2009/05/gtd-seminar/</link>
	<description>Requests for comment</description>
	<lastBuildDate>Sat, 14 Jan 2012 01:55:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: mdwsmith</title>
		<link>http://poojanblog.com/blog/2009/05/gtd-seminar/comment-page-1/#comment-2276</link>
		<dc:creator>mdwsmith</dc:creator>
		<pubDate>Sun, 17 May 2009 07:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://poojanblog.com/blog/2009/05/gtd-seminar/#comment-2276</guid>
		<description>Hi Poojan,
Great writing about some compelling topics within GTD.  I&#039;ve been studying GTD too, but I&#039;ve never been to a live conference (lots of audio though) and indeed, the horizons of focus &#039;altitude&#039; idea came from David&#039;s work consulting for aerospace corps.

One thing in your post that caught my eye is this: You say that you would like to automate linking projects to their actions.  Even this is unnecessary--in the DavidCo podcast, there&#039;s a great interview between Kelly Forrister and David Allen where they address this very point.  David says that we should never worry about linking projects to NEXT actions--this is done in our minds during the weekly review.  The &#039;then I need to, then I need to...&#039; ad hoc project planning should go onto a mindmap or other project support document, not on the action list.  If you do this, there is no need to link next actions to the project they drive forward.
Kind Regards,
Matthew Smith</description>
		<content:encoded><![CDATA[<p>Hi Poojan,<br />
Great writing about some compelling topics within GTD.  I&#8217;ve been studying GTD too, but I&#8217;ve never been to a live conference (lots of audio though) and indeed, the horizons of focus &#8216;altitude&#8217; idea came from David&#8217;s work consulting for aerospace corps.</p>
<p>One thing in your post that caught my eye is this: You say that you would like to automate linking projects to their actions.  Even this is unnecessary&#8211;in the DavidCo podcast, there&#8217;s a great interview between Kelly Forrister and David Allen where they address this very point.  David says that we should never worry about linking projects to NEXT actions&#8211;this is done in our minds during the weekly review.  The &#8216;then I need to, then I need to&#8230;&#8217; ad hoc project planning should go onto a mindmap or other project support document, not on the action list.  If you do this, there is no need to link next actions to the project they drive forward.<br />
Kind Regards,<br />
Matthew Smith</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://poojanblog.com/blog/2009/05/gtd-seminar/comment-page-1/#comment-2237</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 16 May 2009 01:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://poojanblog.com/blog/2009/05/gtd-seminar/#comment-2237</guid>
		<description>&quot;GTD isnâ€™t for everyone.&quot;
I have a theory a person&#039;s productivity method marry up to Myers-Briggs test results.</description>
		<content:encoded><![CDATA[<p>&#8220;GTD isnâ€™t for everyone.&#8221;<br />
I have a theory a person&#8217;s productivity method marry up to Myers-Briggs test results.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

