<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.11.5 (http://www.squarespace.com/) on Thu, 02 Sep 2010 18:32:17 GMT--><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rss="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:cc="http://web.resource.org/cc/"><rss:channel rdf:about="http://www.markforster.net/blog/"><rss:title>Mark Forster's Blog</rss:title><rss:link>http://www.markforster.net/blog/</rss:link><rss:description>Get Everything Done: All About Time Management and Personal Organisation</rss:description><dc:language>en-GB</dc:language><dc:date>2010-09-02T18:32:17Z</dc:date><admin:generatorAgent rdf:resource="http://www.squarespace.com/">Squarespace Site Server v5.11.5 (http://www.squarespace.com/)</admin:generatorAgent><rss:items><rdf:Seq><rdf:li rdf:resource="http://www.markforster.net/blog/2010/8/16/procrastination.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/4/30/time-management-when-retired-update.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/4/21/time-management-when-retired.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/4/6/qlockwork-v-2.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/3/10/italian-version-of-do-it-tomorrow-now-on-sale.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/2/10/a-couple-of-options-for-dwm.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/2/8/is-dwm-closer-to-dit-or-af.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/2/5/day-7.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/2/4/day-6.html"/><rdf:li rdf:resource="http://www.markforster.net/blog/2010/2/4/repetitive-nature-of-work.html"/></rdf:Seq></rss:items></rss:channel><rss:item rdf:about="http://www.markforster.net/blog/2010/8/16/procrastination.html"><rss:title>Procrastination</rss:title><rss:link>http://www.markforster.net/blog/2010/8/16/procrastination.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-08-16T20:47:17Z</dc:date><dc:subject></dc:subject><content:encoded><![CDATA[<p>Good article by Mark McGuinness on <a href="http://lateralaction.com/articles/procrastination/">overcoming procrastination</a> - and not just because he quotes me!</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/4/30/time-management-when-retired-update.html"><rss:title>Time management when retired - update</rss:title><rss:link>http://www.markforster.net/blog/2010/4/30/time-management-when-retired-update.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-04-30T15:09:37Z</dc:date><dc:subject></dc:subject><content:encoded><![CDATA[<p>I think it&#8217;s time to write an update on how my new system for retirees (and non-retirees) is getting on. I&#8217;ve had quite a ride with it because my original idea didn&#8217;t work out, but further experimentation has resulted in something which I think is going to work very well.</p>
<p>Basically it is a system which combines the best bits of DIT, the AFs and DWM:</p>
<ol>
<li>Like DIT it is based on one day&#8217;s work, but it incorporates several improvements to make it more flexible.</li>
<li>Like AF it dismisses stuff which you aren&#8217;t prepared to do, but does so much more directly.</li>
<li>Like AF4 it works on a &#8220;backlog&#8221; and a &#8220;current&#8221; list, but ensures that this is related to one day&#8217;s work.</li>
<li>Like DWM stuff which isn&#8217;t done within a certain number of days gets dismissed, but without the endless page turning.</li>
<li>And best of all it puts the screws on very quickly with the important stuff, while allowing the urgent less important stuff to flow quickly.</li>
</ol>
<p>If you can imagine DIT with the problem solved of what to do when you don&#8217;t finish all today&#8217;s tasks, you&#8217;ll be pretty close.</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/4/21/time-management-when-retired.html"><rss:title>Time management when retired</rss:title><rss:link>http://www.markforster.net/blog/2010/4/21/time-management-when-retired.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-04-21T07:43:42Z</dc:date><dc:subject>Articles Resistance Principle Systems</dc:subject><content:encoded><![CDATA[<p>I had a vision of what it would be like when I retired - I would basically just potter around all day doing the things I enjoyed doing. I would take lots of long walks and visit lots of interesting places. I would at last have time to learn a musical instrument, would perfect my French, Spanish and German, and read loads of books.</p>
<p>Some of that&#8217;s happened, but the sense of unlimited time available for what I want to do has so far eluded me. In fact I am so busy most of the time I don&#8217;t know how I ever fitted full-time, or even part-time, work into my day. I&#8217;m not saying this is necessarily a bad thing - just not what I&#8217;d envisaged.</p>
<p>One of the problems is that I don&#8217;t seem to be able to switch my mind off inventing time management systems. I&#8217;m always getting brilliant ideas, and when I get a brilliant idea I want to try it out. And if I&#8217;m trying it out then I want to tell other people about it, and discuss it with them and get them to try it out too. So before I know it, I&#8217;m doing almost as much work for nothing as I was previously doing for money.</p>
<p>The above is just a preamble to saying that I have now come up with yet another new time management system. It is however very different in the way it works from the Autofocus and DWM systems which I have introduced over the last sixteen months or so. About all it has in common with them is that it uses one long list.</p>
<p>What it does do however is what the Autofocus systems aimed to do, but never quite achieved, which is to autofocus - to zoom in on the things which really matter while not neglecting the mundane but essential tasks which are part of everyone&#8217;s lives. So I&#8217;ve actually started to get moving with the walks, the music, the languages, the trips and the books. And I may even be able to find time without too much difficultly for that fund raising project which my church seems keen to get me involved in.</p>
<p>How does it work? It&#8217;s too early to go into detail, but it is basically a new way of combining some of the time management principles which I have worked on over the years, plus some new ideas.</p>
<p>More soon.</p>
<p>P.S. I almost forgot to say that I think it will work just as well for those who are not retired!</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/4/6/qlockwork-v-2.html"><rss:title>Qlockwork v. 2</rss:title><rss:link>http://www.markforster.net/blog/2010/4/6/qlockwork-v-2.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-04-06T14:21:09Z</dc:date><dc:subject></dc:subject><content:encoded><![CDATA[<p>A couple of years ago, <a href="http://www.markforster.net/blog/2006/12/7/qlockwork.html">I blogged</a> about a useful program called Qlockwork, which keeps track automatically of your computer use.</p>
<p>I&#8217;ve been notified by the publishers of the program that there is now a Version 2 which can be downloaded on 30-day free trial<a href="http://www.qlockwork.com/v2features.html"> from their site</a>.</p>
]]></content:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/3/10/italian-version-of-do-it-tomorrow-now-on-sale.html"><rss:title>Italian version of "Do It Tomorrow" now on sale</rss:title><rss:link>http://www.markforster.net/blog/2010/3/10/italian-version-of-do-it-tomorrow-now-on-sale.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-03-10T08:59:43Z</dc:date><dc:subject></dc:subject><content:encoded><![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:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/2/10/a-couple-of-options-for-dwm.html"><rss:title>A couple of options for DWM</rss:title><rss:link>http://www.markforster.net/blog/2010/2/10/a-couple-of-options-for-dwm.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-02-10T15:37:03Z</dc:date><dc:subject>DWM</dc:subject><content:encoded><![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:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/2/8/is-dwm-closer-to-dit-or-af.html"><rss:title>Is DWM closer to DIT or AF?</rss:title><rss:link>http://www.markforster.net/blog/2010/2/8/is-dwm-closer-to-dit-or-af.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-02-08T16:43:09Z</dc:date><dc:subject>Autofocus DWM Do It Tomorrow</dc:subject><content:encoded><![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:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/2/5/day-7.html"><rss:title>Day 7</rss:title><rss:link>http://www.markforster.net/blog/2010/2/5/day-7.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-02-05T21:56:12Z</dc:date><dc:subject></dc:subject><content:encoded><![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:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/2/4/day-6.html"><rss:title>Day 6</rss:title><rss:link>http://www.markforster.net/blog/2010/2/4/day-6.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-02-04T22:01:49Z</dc:date><dc:subject></dc:subject><content:encoded><![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:encoded></rss:item><rss:item rdf:about="http://www.markforster.net/blog/2010/2/4/repetitive-nature-of-work.html"><rss:title>Repetitive nature of work</rss:title><rss:link>http://www.markforster.net/blog/2010/2/4/repetitive-nature-of-work.html</rss:link><dc:creator>Mark Forster</dc:creator><dc:date>2010-02-04T15:56:26Z</dc:date><dc:subject>DWM Productivity Systems</dc:subject><content:encoded><![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:encoded></rss:item></rdf:RDF>