<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Waiting-For Considered Dangerous. Let&#8217;s Break It Together.</title>
	<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/</link>
	<description></description>
	<pubDate>Thu, 20 Nov 2008 07:22:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: Jon</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-868</link>
		<pubDate>Wed, 03 Jan 2007 05:14:07 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-868</guid>
					<description>@Skeeter:

Taking the filter down to the action level is indeed helpful and is planned for one of the next releases. Thanks for the input on the date fields. Some minimal wording is allowed (like &quot;tomorrow&quot;) but it could be better.

@Clive Walters:

Thank you for the suggestions. Recurring items are on the maybe list at the moment, but may be upgraded soon. Direct links to files would be great and is on the brainstorming list.</description>
		<content:encoded><![CDATA[<p>@Skeeter:</p>
<p>Taking the filter down to the action level is indeed helpful and is planned for one of the next releases. Thanks for the input on the date fields. Some minimal wording is allowed (like &#8220;tomorrow&#8221;) but it could be better.</p>
<p>@Clive Walters:</p>
<p>Thank you for the suggestions. Recurring items are on the maybe list at the moment, but may be upgraded soon. Direct links to files would be great and is on the brainstorming list.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-856</link>
		<pubDate>Tue, 02 Jan 2007 14:12:36 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-856</guid>
					<description>@Bushford:

I agree that an inventory of items that are expected from others is necessary and that after an action is taken to check on that item, something still needs to exist to track that open loop. I just don't keep those items in a &quot;waiting for&quot; context, because they are not actions and &quot;waiting for&quot; isn't really a context in my opinion. This sort of hits at the difference between lists of actions and lists in general (like goals, inbox prompts, and in my case waiting-for items). Given Actiontastic's strong slant toward the physical action items, I have been looking at ways to augment this while still keeping the app focused. One of the next updates will address this.</description>
		<content:encoded><![CDATA[<p>@Bushford:</p>
<p>I agree that an inventory of items that are expected from others is necessary and that after an action is taken to check on that item, something still needs to exist to track that open loop. I just don&#8217;t keep those items in a &#8220;waiting for&#8221; context, because they are not actions and &#8220;waiting for&#8221; isn&#8217;t really a context in my opinion. This sort of hits at the difference between lists of actions and lists in general (like goals, inbox prompts, and in my case waiting-for items). Given Actiontastic&#8217;s strong slant toward the physical action items, I have been looking at ways to augment this while still keeping the app focused. One of the next updates will address this.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Clive Walters</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-830</link>
		<pubDate>Mon, 01 Jan 2007 18:15:07 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-830</guid>
					<description>2 points for a new user like me (having used KinklessGTD):
a. allow note on action to include link(s) to file(s) involved in the action (eg drag the icon onto the note section) - so double click on a file icon and I am there in the app's doc (again!)
b. REPEAT/RECUR facility - the first to chalk it up as a new action again once the check box is ticked, the second to initiate after set time *since* the check box ticked.
PS: dates are good - but they often conflict with sorting lists as offered already. EG- There might be two actions dated today - but one is essential for knock on items - the other a low priority single one. Both have the same contrext - how to highlight to reflect need?</description>
		<content:encoded><![CDATA[<p>2 points for a new user like me (having used KinklessGTD):<br />
a. allow note on action to include link(s) to file(s) involved in the action (eg drag the icon onto the note section) - so double click on a file icon and I am there in the app&#8217;s doc (again!)<br />
b. REPEAT/RECUR facility - the first to chalk it up as a new action again once the check box is ticked, the second to initiate after set time *since* the check box ticked.<br />
PS: dates are good - but they often conflict with sorting lists as offered already. EG- There might be two actions dated today - but one is essential for knock on items - the other a low priority single one. Both have the same contrext - how to highlight to reflect need?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Skeeter</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-597</link>
		<pubDate>Sat, 30 Dec 2006 07:28:17 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-597</guid>
					<description>Two things.... no three...

1. When looking at contexts, why do actions from paused or future start date project show up in my actions for a context. If the project is on hold, why don't the action inherit that pause or start date?

2. I'd like to put a start date like &quot;3 days&quot; or &quot;next week&quot; and have it translate that to a date for me.

3. Just started playing with this app. Looks nice, simple, and well designed. Kudos.</description>
		<content:encoded><![CDATA[<p>Two things&#8230;. no three&#8230;</p>
<p>1. When looking at contexts, why do actions from paused or future start date project show up in my actions for a context. If the project is on hold, why don&#8217;t the action inherit that pause or start date?</p>
<p>2. I&#8217;d like to put a start date like &#8220;3 days&#8221; or &#8220;next week&#8221; and have it translate that to a date for me.</p>
<p>3. Just started playing with this app. Looks nice, simple, and well designed. Kudos.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bushford</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-592</link>
		<pubDate>Fri, 29 Dec 2006 23:32:14 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-592</guid>
					<description>Hi Jon,
I don't agree on the way you suggest to treat delegated actions... 

It just doesn't work in practice.

If I am waiting for someone else to do something in order for a project to move forward, this indeed requires me to chase the person, so &quot;Send James e-mail reminder about his draft proposal&quot; is useful, but it doesn't really help me moving forward the project.  I can send the e-mail, but I still don't have James' draft.  And after sending it, I need to log another action for me to check my inbox for a response? This isn't very efficient.

The only thing that makes the project move forward is for James to &quot;E-mail me the draft proposal&quot;.  That's what I want to see on my Waiting for... list, so I can take whatever action is suitable or convenient.  In any case, until James e-mails me the proposal, the project is incomplete, the loop stays open.

The missing dimension in Actiontastic is that of the &quot;delegate&quot; or &quot;actor&quot;, apart from Context and Project. A third view, with same UI as the other two. That should do the trick, I think.

I have been using NoteBook (CircusPonies) to do GTD, but am hitting its limits.  Currently I am trying out kGTD for OmniOutline r, but it doesn't do the delegation well either.  Actiontastic looks great and I am looking forward to the next release (with delegation features :-))</description>
		<content:encoded><![CDATA[<p>Hi Jon,<br />
I don&#8217;t agree on the way you suggest to treat delegated actions&#8230; </p>
<p>It just doesn&#8217;t work in practice.</p>
<p>If I am waiting for someone else to do something in order for a project to move forward, this indeed requires me to chase the person, so &#8220;Send James e-mail reminder about his draft proposal&#8221; is useful, but it doesn&#8217;t really help me moving forward the project.  I can send the e-mail, but I still don&#8217;t have James&#8217; draft.  And after sending it, I need to log another action for me to check my inbox for a response? This isn&#8217;t very efficient.</p>
<p>The only thing that makes the project move forward is for James to &#8220;E-mail me the draft proposal&#8221;.  That&#8217;s what I want to see on my Waiting for&#8230; list, so I can take whatever action is suitable or convenient.  In any case, until James e-mails me the proposal, the project is incomplete, the loop stays open.</p>
<p>The missing dimension in Actiontastic is that of the &#8220;delegate&#8221; or &#8220;actor&#8221;, apart from Context and Project. A third view, with same UI as the other two. That should do the trick, I think.</p>
<p>I have been using NoteBook (CircusPonies) to do GTD, but am hitting its limits.  Currently I am trying out kGTD for OmniOutline r, but it doesn&#8217;t do the delegation well either.  Actiontastic looks great and I am looking forward to the next release (with delegation features :-))
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Oliver Nielsen</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-492</link>
		<pubDate>Wed, 20 Dec 2006 18:30:47 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-492</guid>
					<description>I'd love to be able to prioritize my projects, move them around, and maybe make some projects sub-projects of parent projects. Simply something like:

A hierarchy in projects listing, with folders.

Dragging the order of projects. Higher in the list yields a larger font, og maybe just a darker font color. So the bottom project becomes light grey text.</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to be able to prioritize my projects, move them around, and maybe make some projects sub-projects of parent projects. Simply something like:</p>
<p>A hierarchy in projects listing, with folders.</p>
<p>Dragging the order of projects. Higher in the list yields a larger font, og maybe just a darker font color. So the bottom project becomes light grey text.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-376</link>
		<pubDate>Wed, 06 Dec 2006 04:43:23 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-376</guid>
					<description>@Everyone:

Thanks for the input on the dates. I am working on the basic date pieces for nearest possible release -- 0.8.3 or 0.8.4.</description>
		<content:encoded><![CDATA[<p>@Everyone:</p>
<p>Thanks for the input on the dates. I am working on the basic date pieces for nearest possible release &#8212; 0.8.3 or 0.8.4.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Steve</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-374</link>
		<pubDate>Mon, 04 Dec 2006 05:26:12 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-374</guid>
					<description>How about forcing some projects or contexts to bring up items for review every x days? This is what inbox does and I think it is a good idea.</description>
		<content:encoded><![CDATA[<p>How about forcing some projects or contexts to bring up items for review every x days? This is what inbox does and I think it is a good idea.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Nick</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-373</link>
		<pubDate>Mon, 04 Dec 2006 03:36:12 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-373</guid>
					<description>I like the idea of dates, but hate calendars. They always distract me with all the empty boxes artificial structures and multiple items in other boxes. What makes more sense to me is a list of dates viewable by action or project so that I only need to see relevant information.</description>
		<content:encoded><![CDATA[<p>I like the idea of dates, but hate calendars. They always distract me with all the empty boxes artificial structures and multiple items in other boxes. What makes more sense to me is a list of dates viewable by action or project so that I only need to see relevant information.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Oskar L-B</title>
		<link>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-372</link>
		<pubDate>Mon, 04 Dec 2006 00:46:40 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/11/30/waiting-for-considered-dangerous-lets-break-it-together/#comment-372</guid>
					<description>I strongly second the 'remind me in x days' suggestion. With a full calendar choice available as a fold-out option, of course. 

All options on the table, just make the simplest ones the preferred. (See: Mac OS X's standard Save Panel layout.)</description>
		<content:encoded><![CDATA[<p>I strongly second the &#8216;remind me in x days&#8217; suggestion. With a full calendar choice available as a fold-out option, of course. </p>
<p>All options on the table, just make the simplest ones the preferred. (See: Mac OS X&#8217;s standard Save Panel layout.)
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
