I'm still somewhat a newbie to GTD, but you asked for feedback - so here you go. It's amazing how theoretically productive one can be while heading in the completely opposite direction of a solution, isn't it? The logical exception would be for an action that can't occur in your current context for some reason. "Context" could be where you are, what you're doing, etc. DA even indicates that there are times when you shouldn't do 2-minute actions, like if there are a bunch of them and you're doing your Weekly Review. It's probably good GTD practice to have some idea of how long a task might take. DA talks about this. If you're waiting for a doctor to call you in, you can call your mom to ask what dish you need to bring to Christmas (assuming you can have a short conversation with your mom ), but it might not make sense to call somebody to have a long phone meeting to hash out the particulars of a software project. But I agree that's not a "context" - unless you subdivide your contexts into "Phone - Short", "Phone - Long", etc. And that begins to violate the "as complicated as required, but not more" GTD principle. Urgent tasks that must be done today go on the calendar. In fact, anything with a hard due date goes on the calendar. DA refers to this as "hard landscape". The issue is when due dates get arbitrarily assigned to things that don't actually have due dates, and you "numb out" to the due dates. Due dates are only for things that will blow up if they don't happen on or by a particular date.