<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.9.3 (http://www.squarespace.com/) on Sun, 21 Mar 2010 23:55:05 GMT--><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><title>Mark Forster's Blog</title><subtitle>Blog</subtitle><id>http://www.markforster.net/blog/</id><link rel="alternate" type="application/xhtml+xml" href="http://www.markforster.net/blog/"/><link rel="self" type="application/atom+xml" href="http://www.markforster.net/blog/atom.xml"/><updated>2010-03-10T09:08:36Z</updated><generator uri="http://www.squarespace.com/" version="Squarespace Site Server v5.9.3 (http://www.squarespace.com/)">Squarespace</generator><entry><title>Italian version of "Do It Tomorrow" now on sale</title><id>http://www.markforster.net/blog/2010/3/10/italian-version-of-do-it-tomorrow-now-on-sale.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/3/10/italian-version-of-do-it-tomorrow-now-on-sale.html"/><author><name>Mark Forster</name></author><published>2010-03-10T08:59:43Z</published><updated>2010-03-10T08:59:43Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p><a href="http://www.sangiovannis.com/ita/41_do-it-tomorrow----------fallo-domani.htm"><span class="full-image-block ssNonEditable"><span><img src="http://www.markforster.net/storage/DIT%20Italian%20Cover.png?__SQUARESPACE_CACHEVERSION=1268211968831" alt="" /></span></span></a></p>
<p>The Italian version of &#8220;Do It Tomorrow&#8221; published by Sangiovanni&#8217;s is now on sale (price <span class="testorosso_dettpro"> &euro; 15.95). You can read more details (in Italian) and order <a href="http://www.sangiovannis.com/ita/41_do-it-tomorrow----------fallo-domani.htm">by clicking here</a>.<br /></span></p>
]]></content></entry><entry><title>A couple of options for DWM</title><category term="DWM"/><id>http://www.markforster.net/blog/2010/2/10/a-couple-of-options-for-dwm.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/10/a-couple-of-options-for-dwm.html"/><author><name>Mark Forster</name></author><published>2010-02-10T15:37:03Z</published><updated>2010-02-10T15:37:03Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>Here are a couple of options which I have been trying out for DWM, which have the aim of ensuring that you can keep the important stuff moving. You can use both of them at the same time if you wish:</p>
<p>1) <em>The Current Initiative</em>.</p>
<p>This is similar to the Current Initiative in DIT and is designed to be &#8220;The thing that you do first every day&#8221;. The idea is to select one project to which you want to give special treatment for a while.</p>
<p>The method is to write the selected project in BLOCK CAPS on your list. Every day when you start work on your list, your starting point is that project. You must do some work on it before moving on to any other task. Apart from these rules, you treat it like any other recurring task.</p>
<p>Once you have completed the project or got it sufficiently up and running, you can select a new Current Initiative.</p>
<p>2) <em>Next Pass Mark-Up.</em></p>
<p>At present when you scan through the list you can either pass by a task or do some work on it. The &#8220;Next Pass Mark-Up&#8221; adds one further thing you can do, which is to mark the task up for action on the next pass through the list.</p>
<p>You then <em>must</em> take some action on that task on the next pass, unless it is physically impossible to do so.</p>
<p>Unlike the Current Initiative, under which a project remains Current Initiative until another one is chosen, the Next Pass Mark-Up does not remain with the task if it is re-entered.</p>
<p>This is <em>not</em> intended to be a method of prioritising tasks, and therefore tasks can only be given this designation as they are considered for action during a normal pass through the list.</p>
<p>The mark-up should be used very sparingly, otherwise the list may be slowed down and resistance increased.</p>
<p>The recommended method of marking a task for this purpose is to draw a small circle in front of it:</p>
<p>○ Call Bill Smith</p>
<p>This can then be filled in when you start work on the task, so that your current place on the list is marked (like the normal dot):</p>
<p>● Call Bill Smith</p>
<p>And finally the task is crossed out in the normal way when you finish working on it:</p>
<p><span style="text-decoration: line-through;">● Call Bill Smith</span></p>
]]></content></entry><entry><title>Is DWM closer to DIT or AF?</title><category term="Autofocus"/><category term="DWM"/><category term="Do It Tomorrow"/><id>http://www.markforster.net/blog/2010/2/8/is-dwm-closer-to-dit-or-af.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/8/is-dwm-closer-to-dit-or-af.html"/><author><name>Mark Forster</name></author><published>2010-02-08T16:43:09Z</published><updated>2010-02-08T16:43:09Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p><em style="font-size: 90%;">Please note: This post assumes a knowledge of both the &#8220;Do It Tomorrow&#8221; (DIT) and the Day-Week-Month (DWM) time management systems. If you don&#8217;t have this knowledge please don&#8217;t bother to read it!</em></p>
<p>One thing that&#8217;s becoming increasingly clear to me as I work the new DWM system is that it is not just close to DIT, but actually <em>is</em> DIT.</p>
<p>To see this, let&#8217;s examine the statistics which I published in my previous post on February 5th:</p>
<p>Feb 6. 0 (36)</p>
<p>Feb 7. 0 (46)</p>
<p>Feb 8. 0 (50)</p>
<p>Feb 9. 0 (40)</p>
<p>Feb 10. 1 (43)</p>
<p>Feb 11. 16 (62)</p>
<p>Feb 12. 25 (42)</p>
<p>Remember that in DIT you enter all tasks by default under tomorrow&#8217;s date with the idea that you take action on them tomorrow. There are however two important exceptions to this. One is that you can enter urgent tasks &#8220;below the line&#8221; so that they are done today instead of tomorrow. The other is that you can allow yourself to get behind by 4 or 5 days. If you get further behind than that you are supposed to audit your commitments.</p>
<p>If you look more closely at the statistics qyoted above you can see that DWM has kept completely to these principles, except that it has moved the entry point one week into the future. February 12 was where tasks for &#8220;tomorrow&#8221; were added, and February 11th was today&#8217;s list. February 10 consisted of one task which had got behind one day. The 17 tasks shown as already completed on February 12 were the equivalent of DIT&#8217;s urgent tasks entered &#8220;below the line&#8221; today.</p>
<p>Feb 6. 0 (36)</p>
<p>Feb 7. 0 (46)</p>
<p>Feb 8. 0 (50)</p>
<p>Feb 9. 0 (40)</p>
<p>Feb 10. 1 (43) = DIT&#8217;s &#8220;Behind by 1 day&#8221;</p>
<p>Feb 11. 16 (62) = DIT&#8217;s &#8220;Today&#8221;</p>
<p>Feb 12. 25 (42) = DIT&#8217;s &#8220;Tomorrow&#8221;</p>
<p>The only real changes to DIT, apart from the method of entry, are:</p>
<p>1) There is now no need to make a distinction between &#8220;same day&#8221; tasks and &#8220;everything else&#8221;.</p>
<p>2) The rather nebulous audit procedure in DIT has been changed into an automatic dismissal process.</p>
<p>I&#8217;m sure you will be asking &#8220;What about DWM&#8217;s 1-month entry point?&#8221;</p>
<p>Well, all the 1-month entry point is really doing is adding a pre-screening process to DIT. Instead of relying on the audit to weed out unnecessary tasks, there is now a process by which anything can be added to the list but is weeded out automatically if it no action is taken on it within one month. It also means that anything that gets on the 1-week list has had at least some preliminary action taken on it. There will of course come a time when unactioned 1-month entries co-exist on the same page as new 1-week entry tasks, but there is unlikely to be much confusion between them.</p>
]]></content></entry><entry><title>Day 7</title><id>http://www.markforster.net/blog/2010/2/5/day-7.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/5/day-7.html"/><author><name>Mark Forster</name></author><published>2010-02-05T21:56:12Z</published><updated>2010-02-05T21:56:12Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>I&#8217;ve now been working DWM for a complete week and it&#8217;s still working extremely well for me. I don&#8217;t intend to publish another summary for at least a week unless something happens worth reporting.</p>
<p>Here are the stats for the pages I&#8217;ve used so far:</p>
<p>Feb 6. 0 (36)</p>
<p>Feb 7. 0 (46)</p>
<p>Feb 8. 0 (50)</p>
<p>Feb 9. 0 (40)</p>
<p>Feb 10. 1 (43)</p>
<p>Feb 11. 16 (62)</p>
<p>Feb 12. 25 (42)</p>
<p>&#8212;&#8212;&#8212;&#8212;</p>
<p>Feb 28. 18 (99)</p>
<p>Mar 1. 5 (27)</p>
<p>Mar 2. 5 (33)</p>
<p>Mar 3. 5 (11)</p>
<p>Mar 4. 29 (47)</p>
<p>Mar 5. 6 (18)</p>
<p>Totals: 105 (554)</p>
]]></content></entry><entry><title>Day 6</title><id>http://www.markforster.net/blog/2010/2/4/day-6.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/4/day-6.html"/><author><name>Mark Forster</name></author><published>2010-02-04T22:01:49Z</published><updated>2010-02-04T22:01:49Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>All still going well with DWM. I don&#8217;t remember enjoying working any of my previous systems as much as this one.</p>
<p>I&#8217;ve now completed all the actions for the first three pages: Feb 6, 7 and 8 and there is only one left on Feb 9, so I don&#8217;t think I will have any tasks being dismissed until Wednesday next week at the earliest.</p>
]]></content></entry><entry><title>Repetitive nature of work</title><category term="DWM"/><category term="Productivity"/><category term="Systems"/><id>http://www.markforster.net/blog/2010/2/4/repetitive-nature-of-work.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/4/repetitive-nature-of-work.html"/><author><name>Mark Forster</name></author><published>2010-02-04T15:56:26Z</published><updated>2010-02-04T15:56:26Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>The new DWM system is throwing up some interesting new perspectives. One that has struck me quite forcibly is the repetitive nature of most of my work. Previous time management systems have tended to disguise the number of times that one re-enters the same task on the list.</p>
<p>But DWM separates out re-entered tasks from new tasks, and rather to my surprise I discovered that the number of new tasks that I&#8217;m putting on the list is decidedly in the minority. For example, yesterday I re-entered 43 tasks and only added 11 new tasks.</p>
<p>This reinforces a point I have often made, which is that good systems are all important in being well-organised. If the majority of tasks are repetitious, then making sure that those tasks are being carried out as efficiently as possible will bring about huge time savings.</p>
]]></content></entry><entry><title>Day 5</title><category term="DWM"/><id>http://www.markforster.net/blog/2010/2/3/day-5.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/3/day-5.html"/><author><name>Mark Forster</name></author><published>2010-02-03T23:56:05Z</published><updated>2010-02-03T23:56:05Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>I haven&#8217;t been around much today because of some outside engagements, but nevertheless the new DWM system has proved its worth. Everything I needed to get done has got done, and quite a bit more. My pages for Feb 6th and Feb 7th have now got no unactioned tasks on them, so I won&#8217;t be in danger of any tasks being dismissed until next Monday.</p>
<p>The real crunch of course will come in eighteen days time when the original 1-month page becomes the 1-week page. Until then it is really impossible to judge the system properly.</p>
<p>In the meantime, I keep feeling more and more that the system is very psychologically powerful. I don&#8217;t think that I&#8217;ve felt quite so motivated and in control of my time with any of my previous systems.</p>
]]></content></entry><entry><title>Provisional name for new system</title><category term="DWM"/><id>http://www.markforster.net/blog/2010/2/3/provisional-name-for-new-system.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/3/provisional-name-for-new-system.html"/><author><name>Mark Forster</name></author><published>2010-02-03T12:27:31Z</published><updated>2010-02-03T12:27:31Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>It&#8217;s a bit unsatisfactory referring to the new system as DIT2/AF5 so I&#8217;ve decided to refer to it from now, until we come up a better, by the provisional name &#8220;The Day/Week/Month Time Management System&#8221;, for short &#8220;DWM&#8221;.</p>
]]></content></entry><entry><title>Day 4 Stats</title><category term="DWM"/><id>http://www.markforster.net/blog/2010/2/3/day-4-stats.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/3/day-4-stats.html"/><author><name>Mark Forster</name></author><published>2010-02-03T00:44:55Z</published><updated>2010-02-03T00:44:55Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>Day 4 has gone even better than Days 1-3, in spite of my broadband connection failing late this afternoon which is why I&#8217;m writing this at 12.45 am. I&#8217;m beginning to appreciate the power of this system.</p>
<p>Here are the stats as they are now:</p>
<p>Feb 6. 0 (36)</p>
<p>Feb 7. 1 (46)</p>
<p>Feb 8. 8 (50)</p>
<p>Feb 9. 23 (39)</p>
<p>Feb 28. 25 (99)</p>
<p>Mar 1. 6 (27)</p>
<p>Mar 2. 14 (31)</p>
<p>Totals: 77 (328)</p>
]]></content></entry><entry><title>Day 3 Stats</title><category term="DWM"/><id>http://www.markforster.net/blog/2010/2/1/day-3-stats.html</id><link rel="alternate" type="text/html" href="http://www.markforster.net/blog/2010/2/1/day-3-stats.html"/><author><name>Mark Forster</name></author><published>2010-02-01T18:52:48Z</published><updated>2010-02-01T18:52:48Z</updated><content type="html" xml:lang="en-GB"><![CDATA[<p>I&#8217;ve been working my new system now for three days. So here are the statistics as at the end of Day 3 for each active page that I have now. The first figure is the number of task remaining unactioned on the page. The second figure (in brackets) is the total number on the page.</p>
<p>Feb 6.&nbsp; 2 (36)</p>
<p>Feb 7. 10 (46)</p>
<p>Feb 8.&nbsp; 23 (40)</p>
<p>Feb 28. 27 (99)</p>
<p>Mar 1. 4 (24)</p>
<p>Totals: 66 (244)</p>
<p>Bear in mind that because of the short month, Feb 28 was open to new entries for two days.</p>
]]></content></entry></feed>