{"id":3642,"date":"2016-03-24T13:29:54","date_gmt":"2016-03-24T20:29:54","guid":{"rendered":"http:\/\/www.michaellinenberger.com\/blog\/?p=3642"},"modified":"2016-03-24T13:29:54","modified_gmt":"2016-03-24T20:29:54","slug":"the-right-way-to-set-start-dates-with-tasks-in-myn","status":"publish","type":"post","link":"https:\/\/www.michaellinenberger.com\/blog\/the-right-way-to-set-start-dates-with-tasks-in-myn\/","title":{"rendered":"The Right Way to Set Start Dates with Tasks in MYN"},"content":{"rendered":"

March 24, 2016<\/strong><\/p>\n

Perhaps the most powerful and unique thing about the MYN task system<\/a> is the way it uses start dates<\/em> to schedule tasks and to sort tasks. The use of start dates is what separates MYN from my simpler 1MTD system, and from virtually every other task system out there. It\u2019s what makes MYN so effective.<\/p>\n

But sometimes people get confused about how best to use start dates in MYN. So I want to talk about the right way to use them, so that you can get nimble with them and really get control of your workday.<\/p>\n

Start Date Is really a Consideration<\/em> Date<\/strong><\/p>\n

Recall, with MYN Outlook configurations, a task is hidden until its start date arrives. Given that, the start date you enter for a new task should either be the date you want to first start doing<\/em> the task, or the date you first want to start considering<\/em> the task, whichever is sooner<\/em>. With that in mind, for most new tasks when you receive them, entering a start date of today<\/em> makes sense. That\u2019s because most new tasks have at least a little urgency around them and so you\u2019d like to place them in view right away to allow you to find the best time to fit them in\u2014as soon as you can.<\/p>\n

But of course, if you put all<\/em> new tasks in plain view, your task list will soon get very big and it can become unmanageable. You and others will think up tasks faster than you can complete them. And that\u2019s why we have size limits<\/a> in MYN\u2014to prevent the list from becoming uselessly large. So, you need to find strategies to shorten your list, and one<\/em> way to do that is to defer tasks to the future that just don\u2019t make sense to think about right now. So you set the start date to the future for some tasks, thus hiding them and shortening your list a bit.<\/p>\n

Don\u2019t Confuse a Start Date with a Deadline<\/strong><\/p>\n

The confusion that many people have when doing this is that they confuse a start date with a deadline. Many people state in my classes \u201cI want to see, right in my main list, all tasks with future start dates so I can think about them before they are due.\u201d I point out to those people that the start date is not equal to the deadline. So if you know you will want to start thinking about a task early, ahead of its deadline, set the start date well before the true deadline. That way the task will pop up in your list in time to consider it and start working on it. Then, the best way to show the true deadline<\/em> is to type it right in the subject line like: DUE April 15 Submit Taxes<\/em>. Clearly, in this specific example, the start date on this task should be way ahead of that deadline so you can see it early and start working on it.<\/p>\n

FRESH Prioritization <\/strong><\/p>\n

There is another way start dates are used in MYN. Once a start date arrives and a task is in your list, the role of the start date completely changes. At that point, its role is to show you how old the task is, and sort the older ones lower, per FRESH Prioritization<\/a>. This is a great way to automatically highlight tasks that have more energy and to automatically place old dead tasks in a less prominent position in your list, particular when working in a long Opportunity Now section (the medium priority). Follow the FRESH Prioritization<\/a> link to learn more.<\/p>\n

However, sometimes people object to this too. They say they want the older tasks to sort higher<\/em> in the list not lower. They state: \u201cIf something\u2019s old, doesn\u2019t it mean I\u2019ve been irresponsible about doing it and so shouldn\u2019t I have those positioned higher in my list?\u201d But when somebody brings this up I ask them the following questions: \u201cThink of your email inbox. Would you want new emails to go to the bottom of the inbox, and your oldest email to be at the top? After all, the older mail is being neglected, right?\u201d Of course the answer is no. And that\u2019s because newer emails tend to have more relevance and tend to need more attention. And that\u2019s true with tasks. Because priorities change, old tasks tend to lose importance. But of course not all<\/em> of them do, and if you spot an old task that seems too far down in your list, you can always promote it to the top of your list by changing its start date today.<\/p>\n

Defer to Review\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/strong><\/p>\n

The best<\/em> way to keep your daily list reasonably small in size is to aggressively move things to the Over the Horizon (low priority) section. But when that section accumulates over 75 items it will be hard to review each week. That\u2019s where start dates come in. You can hide low priority tasks that don\u2019t need review every week by using Defer to Review with future start dates\u2014ones that are appropriate for the differing review cycles of each low priority task. This works great to keep your visible task count short and to allow you to only focus on the tasks you need to. Defer to Review is a longer topic so I leave that for your study<\/a>.<\/p>\n

So that\u2019s it, that\u2019s how to use start dates in the MYN system. It\u2019s a very powerful feature that tens of thousands of people have found makes managing tasks much easier and much more powerful.<\/p>\n

Michael<\/p>\n","protected":false},"excerpt":{"rendered":"

March 24, 2016 Perhaps the most powerful and unique thing about the MYN task system is the way it uses start dates to schedule tasks and to sort tasks. The use of start dates is what separates MYN from my … Continue reading →<\/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-3642","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\/3642","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=3642"}],"version-history":[{"count":5,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/posts\/3642\/revisions"}],"predecessor-version":[{"id":3647,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/posts\/3642\/revisions\/3647"}],"wp:attachment":[{"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/media?parent=3642"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/categories?post=3642"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.michaellinenberger.com\/blog\/wp-json\/wp\/v2\/tags?post=3642"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}