<?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:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Tip of the Week: Try Listing Problems Instead of Next Actions</title>
	<atom:link href="http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/</link>
	<description></description>
	<lastBuildDate>Fri, 25 May 2012 04:51:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Patrick Allmond</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58560</link>
		<dc:creator><![CDATA[Patrick Allmond]]></dc:creator>
		<pubDate>Sun, 19 Aug 2007 12:55:40 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58560</guid>
		<description><![CDATA[Boy I am a day late and dollar short.

The only thing I&#039;d suggest is a change in terminology. Problems will tend to put a negative spin on things for you and those you work with. Instead try using the words &quot;challenge&quot; or &quot;issue&quot;. It will still apply to software and most other subjects as well. It may seem trivial but the actual words you use will affect your attitude when working with the item.

Patrick]]></description>
		<content:encoded><![CDATA[<p>Boy I am a day late and dollar short.</p>
<p>The only thing I&#8217;d suggest is a change in terminology. Problems will tend to put a negative spin on things for you and those you work with. Instead try using the words &#8220;challenge&#8221; or &#8220;issue&#8221;. It will still apply to software and most other subjects as well. It may seem trivial but the actual words you use will affect your attitude when working with the item.</p>
<p>Patrick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My Get Things Done List &#187; Blog Archive &#187; Problems or actions, it's still a list [What's the next action]</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58559</link>
		<dc:creator><![CDATA[My Get Things Done List &#187; Blog Archive &#187; Problems or actions, it's still a list [What's the next action]]]></dc:creator>
		<pubDate>Wed, 08 Aug 2007 04:04:15 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58559</guid>
		<description><![CDATA[[...] Daily published an interesting article. A programmer decided he would not list his next actions but his problems. While reading the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Daily published an interesting article. A programmer decided he would not list his next actions but his problems. While reading the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Listing Problems Instead of Next Actions</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58558</link>
		<dc:creator><![CDATA[Listing Problems Instead of Next Actions]]></dc:creator>
		<pubDate>Mon, 16 Jul 2007 10:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58558</guid>
		<description><![CDATA[[...] at Web Worker Daily » Blog Archive Tip of the Week: Try Listing Problems Instead of Next Actions «, the question is asked, &#8220;can this be applied to more than just [...]]]></description>
		<content:encoded><![CDATA[<p>[...] at Web Worker Daily » Blog Archive Tip of the Week: Try Listing Problems Instead of Next Actions «, the question is asked, &#8220;can this be applied to more than just [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Padraig O'Morain</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58557</link>
		<dc:creator><![CDATA[Padraig O'Morain]]></dc:creator>
		<pubDate>Sun, 10 Jun 2007 09:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58557</guid>
		<description><![CDATA[A value I can see to this approach is that I think I sometimes put off doing next actions because at some level I&#039;m hung up about the problem it&#039;s meant to solve. By making the problems explicit I might be able to stop fooling myself. I&#039;ll try this and let you know how I get on!]]></description>
		<content:encoded><![CDATA[<p>A value I can see to this approach is that I think I sometimes put off doing next actions because at some level I&#8217;m hung up about the problem it&#8217;s meant to solve. By making the problems explicit I might be able to stop fooling myself. I&#8217;ll try this and let you know how I get on!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Cornell</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58556</link>
		<dc:creator><![CDATA[Matthew Cornell]]></dc:creator>
		<pubDate>Mon, 14 May 2007 12:26:39 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58556</guid>
		<description><![CDATA[Nice article. I&#039;ve been thinking about how lean programming techniques merge with GTD, and the idea of early vs. late decisions is interesting. On the one hand, deciding action when things show up is a very deep central concept in GTD. On the other hand, putting off excessive project planning is also there...

Regarding problems, you&#039;ve probably heard that &quot;every problem should be a project&quot; - see &lt;a href=&quot;http://ideamatt.blogspot.com/2006/02/why-every-problem-should-be-gtd.html&quot; rel=&quot;nofollow&quot;&gt;Why every problem should be a GTD project&lt;/a&gt;.]]></description>
		<content:encoded><![CDATA[<p>Nice article. I&#8217;ve been thinking about how lean programming techniques merge with GTD, and the idea of early vs. late decisions is interesting. On the one hand, deciding action when things show up is a very deep central concept in GTD. On the other hand, putting off excessive project planning is also there&#8230;</p>
<p>Regarding problems, you&#8217;ve probably heard that &#8220;every problem should be a project&#8221; &#8211; see <a href="http://ideamatt.blogspot.com/2006/02/why-every-problem-should-be-gtd.html" rel="nofollow">Why every problem should be a GTD project</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Productivity links for May 8th</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58555</link>
		<dc:creator><![CDATA[Productivity links for May 8th]]></dc:creator>
		<pubDate>Wed, 09 May 2007 00:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58555</guid>
		<description><![CDATA[[...] Web Worker Daily &#187; Blog Archive Tip of the Week: Try Listing Problems Instead of Next Actions ... - &#8220;Postponing decisions on what action to take allows you to optimize the action at the time you do it.&#8221; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Web Worker Daily &raquo; Blog Archive Tip of the Week: Try Listing Problems Instead of Next Actions &#8230; &#8211; &#8220;Postponing decisions on what action to take allows you to optimize the action at the time you do it.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-05-08</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58554</link>
		<dc:creator><![CDATA[links for 2007-05-08]]></dc:creator>
		<pubDate>Tue, 08 May 2007 07:20:41 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58554</guid>
		<description><![CDATA[[...] Web Worker Daily » Blog Archive Tip of the Week: Try Listing Problems Instead of Next Actions « &#8220;Postponing decisions on what action to take allows you to optimize the action at the time you do it.&#8221; (tags: GTD lifehacks organization productivity self-improvement) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Web Worker Daily » Blog Archive Tip of the Week: Try Listing Problems Instead of Next Actions « &#8220;Postponing decisions on what action to take allows you to optimize the action at the time you do it.&#8221; (tags: GTD lifehacks organization productivity self-improvement) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Veltman</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58553</link>
		<dc:creator><![CDATA[Paul Veltman]]></dc:creator>
		<pubDate>Tue, 01 May 2007 21:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58553</guid>
		<description><![CDATA[I like the idea of keeping a list of problems, but would not throw away the &#039;Next Actions&#039; list yet.

The &#039;Next Actions&#039; are a list of thought-through actions designed to solve problems. All the thinking has been done, and the widgets just need to be cranked.

To replace this with a list of problems which still need to be solved or thought about seems to undo the usefulness of this approach, and might be better described as &#039;Getting Things Thunk About&#039; rather than &#039; Getting Things Done&#039;.

One is geared towards Action, the other geared towards Purpose and Direction.

These need to be kept distinct, and as previous commentators have said, the Weekly Review of the &#039;Projects&#039; list already provides room for this thinking and processing.

PV]]></description>
		<content:encoded><![CDATA[<p>I like the idea of keeping a list of problems, but would not throw away the &#8216;Next Actions&#8217; list yet.</p>
<p>The &#8216;Next Actions&#8217; are a list of thought-through actions designed to solve problems. All the thinking has been done, and the widgets just need to be cranked.</p>
<p>To replace this with a list of problems which still need to be solved or thought about seems to undo the usefulness of this approach, and might be better described as &#8216;Getting Things Thunk About&#8217; rather than &#8216; Getting Things Done&#8217;.</p>
<p>One is geared towards Action, the other geared towards Purpose and Direction.</p>
<p>These need to be kept distinct, and as previous commentators have said, the Weekly Review of the &#8216;Projects&#8217; list already provides room for this thinking and processing.</p>
<p>PV</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: raincoaster</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58552</link>
		<dc:creator><![CDATA[raincoaster]]></dc:creator>
		<pubDate>Tue, 01 May 2007 09:44:36 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58552</guid>
		<description><![CDATA[Actually, it&#039;s a damn useful perspective shift, moving from &quot;next action&quot; to &quot;next issue to face.&quot; I teach personal growth courses to people in crisis, and circumstances change for them so quickly that sometimes the identified next action is impossible or inappropriate by the time it&#039;s supposed to happen.

Hey, for grocery lists for those on a tight budget, it makes no sense to write &quot;go to store&quot; but it makes plenty of sense to write &quot;need breakfast cereal, entrees, milk for a week...&quot; then buy what&#039;s on sale instead of specifics you stuck on there days ago. This is the kind of flexibility that the shift can provide.]]></description>
		<content:encoded><![CDATA[<p>Actually, it&#8217;s a damn useful perspective shift, moving from &#8220;next action&#8221; to &#8220;next issue to face.&#8221; I teach personal growth courses to people in crisis, and circumstances change for them so quickly that sometimes the identified next action is impossible or inappropriate by the time it&#8217;s supposed to happen.</p>
<p>Hey, for grocery lists for those on a tight budget, it makes no sense to write &#8220;go to store&#8221; but it makes plenty of sense to write &#8220;need breakfast cereal, entrees, milk for a week&#8230;&#8221; then buy what&#8217;s on sale instead of specifics you stuck on there days ago. This is the kind of flexibility that the shift can provide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://gigaom.com/collaboration/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58551</link>
		<dc:creator><![CDATA[Richard]]></dc:creator>
		<pubDate>Tue, 01 May 2007 04:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.com/2007/04/30/tip-of-the-week-try-listing-problems-instead-of-next-actions/#comment-58551</guid>
		<description><![CDATA[As a programmer myself, I kinda combine the methods.  Initially, I&#039;ll tag an action with &quot;bug&quot; or &quot;feature&quot; in my list, and then when it&#039;s closer to being worked on I&#039;ll change it to an action, if I have a specific solution in mind.

Also, those bugs etc really don&#039;t need contexts...I&#039;m fairly sure I know where I&#039;ll be when I do them ;)]]></description>
		<content:encoded><![CDATA[<p>As a programmer myself, I kinda combine the methods.  Initially, I&#8217;ll tag an action with &#8220;bug&#8221; or &#8220;feature&#8221; in my list, and then when it&#8217;s closer to being worked on I&#8217;ll change it to an action, if I have a specific solution in mind.</p>
<p>Also, those bugs etc really don&#8217;t need contexts&#8230;I&#8217;m fairly sure I know where I&#8217;ll be when I do them ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

