{"id":839,"date":"2011-05-23T08:19:16","date_gmt":"2011-05-23T15:19:16","guid":{"rendered":"http:\/\/masteryourworkday.com\/?p=839"},"modified":"2011-05-23T08:19:16","modified_gmt":"2011-05-23T15:19:16","slug":"most-tasks-do-not-have-deadlines-excerpt-from-new-third-edition-of-outlook-book","status":"publish","type":"post","link":"https:\/\/www.michaellinenberger.com\/blog\/most-tasks-do-not-have-deadlines-excerpt-from-new-third-edition-of-outlook-book\/","title":{"rendered":"Most Tasks Do Not have Deadlines: Excerpt from New Third Edition of Outlook Book"},"content":{"rendered":"<p>May 23, 2011<\/p>\n<p>One thing <a href=\"http:\/\/masteryourworkday.com\/using-myn-with-getting-things-done%C2%AE-gtd%C2%AE\" target=\"_blank\">GTD (David Allen)<\/a> and I agree on is that nearly all tasks you put on your task list should be Next Actions. Using next action tasks leads to this fact: most next action tasks on your list do not have firm deadlines&#8212;they are intermediate steps to larger outcomes and it&#8217;s the larger outcomes that have the true deadlines.<\/p>\n<p>Here is an excerpt from my new <a href=\"http:\/\/www.michaellinenberger.com\/BookTWC.html\" target=\"_blank\">Third Edition of Total Workday Control Using Microsoft Outlook<\/a> about this topic (page 75):<\/p>\n<blockquote><p>Somewhere during the history of task management training, someone created a rule that says, \u201cIf you do not assign a due date to a task it won\u2019t get done.\u201d That rule sounds good, doesn\u2019t it? It sounds so proactive. That is why nearly all automated task systems include a due date field. But as I mentioned in the Introduction, this is not a good rule. Why? Because the way the rule is usually used, which is to set artificial due dates on most tasks, it is an attempt to trick yourself, and you are not so easily tricked. It reminds me of the people I once knew who set their wristwatch ahead ten minutes thinking it would help them be on time to meetings. In reality, it<!--more--> only worked for a couple days and then the person just mentally adjusted and started being late to meetings again. You do the same with artificial due dates; you just start to ignore them.<\/p>\n<p>Also mentioned in the Introduction is that artificial due dates can actually lead to more missed deadlines, because as you start to skip deadlines that you know are false, you suffer from the \u201ccry wolf\u201d phenomenon. Since most of your tasks have fake due dates you get used to skipping them, and then you may not recognize a true due date when you see it, and you may skip it. Like Little Red Riding Hood, you get eaten alive, but in this case by missed deadlines.<\/p>\n<p>That does not mean you should not apply a true deadline to those tasks that really have them, particularly those imposed from the outside (from your client or boss for example); there are appropriate times to set true deadlines. But you will not be using the Outlook Due Date field to do so; you will use other approaches. I will show you how to do that just ahead. For now, note that the kinds of tasks you should put on your Now Tasks list are small, next-step or next-action tasks. These are small actions toward larger goals, and these kinds of intermediate-step tasks usually do not have hard deadlines; so please don\u2019t set them artificially. Instead, use the next technique: set a start date.<\/p><\/blockquote>\n<p>So putting a due date on all or most tasks is just not a realistic strategy. I go on to emphasize in the next pages of the book why the start date is a powerful (and realistic) way to manage tasks, and why <em>all <\/em>tasks should have a start date assigned. And then show other ways to set deadlines.<\/p>\n<p>Michael<\/p>\n","protected":false},"excerpt":{"rendered":"<p>May 23, 2011 One thing GTD (David Allen) and I agree on is that nearly all tasks you put on your task list should be Next Actions. Using next action tasks leads to this fact: most next action tasks on &hellip; <a href=\"https:\/\/www.michaellinenberger.com\/blog\/most-tasks-do-not-have-deadlines-excerpt-from-new-third-edition-of-outlook-book\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-839","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/posts\/839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/comments?post=839"}],"version-history":[{"count":0,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/posts\/839\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/media?parent=839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/categories?post=839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/tags?post=839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}