<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>garyslinger.com Blog &#187; Time Management</title>
	<atom:link href="http://garyslinger.com/blog/index.php/category/time-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://garyslinger.com/blog</link>
	<description>Thoughts...</description>
	<lastBuildDate>Mon, 28 Dec 2009 04:04:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What is GTD?</title>
		<link>http://garyslinger.com/blog/2005/11/20/what-is-gtd/</link>
		<comments>http://garyslinger.com/blog/2005/11/20/what-is-gtd/#comments</comments>
		<pubDate>Sun, 20 Nov 2005 22:41:45 +0000</pubDate>
		<dc:creator>Gary Slinger</dc:creator>
				<category><![CDATA[GTD]]></category>
		<category><![CDATA[Time Management]]></category>

		<guid isPermaLink="false">http://garyslinger.com/blog/2005/11/20/what-is-gtd/</guid>
		<description><![CDATA[		 		 	
GTD is the acronym, and common nickname, for Getting Things Done, a time and personal organization management methodology, written by David Allen. The book of the subject can be found at Amazon here, David Allen’s company is here, and his own explanation of what GTD is can be found here.
I personally use the [...]]]></description>
			<content:encoded><![CDATA[<p><a rel="attachment" title="Getting Things Done" href="http://garyslinger.wordpress.com//?attachment_id=43">		 		 	</a></p>
<p>GTD is the acronym, and common nickname, for Getting Things Done, a time and personal organization management methodology, written by David Allen. The book of the subject can be found at Amazon <a href="http://www.amazon.com/gp/product/0142000280/104-8632197-6196715">here</a>, David Allen’s company is <a href="http://www.davidco.com/">here</a>, and his own explanation of what GTD is can be found <a href="http://www.davidco.com/what_is_gtd.php">here</a>.</p>
<p>I personally use the GTD methodology, with a few minor tweaks to my own circumstances and preferences, as is common to many practitioners of it. I use a Blackberry as my primary communications tool; it often becomes my always-available capture device (read the book…), as it is always with me. But, depending on the circumstances, I may also use a <a href="http://www.43folders.com/2004/09/03/introducing-the-hipster-pda/">HipsterPDA</a>, again, modified to my own purposes (which is the whole point of the hPDA), or <a href="http://www.microsoft.com/office/onenote/prodinfo/overview.mspx">Microsoft OneNote</a>, or <a href="http://www.mindjet.com/us/">MindJet MindManager</a> — the important thing, in GTD terms and techniques, is that no matter who I create actions or record information, everything ultimately ends up in one Inbox, for later processing. In my case, I use Microsoft Outlook, and the <a href="http://www.davidco.com/store/product.php?productid=16156&#038;cat=26&#038;page=1">NetCentrics GTD Add-In.<br />
</a><br />
The book retails for less than ten dollars. There are a multitude of sites, blogs and discussion groups around the web discussion the application of the methodology; you could read those without having read the book first, but the maximum benefit comes with the book. It’s an easy read, although actually implementing the processes for the first time may require you to set aside a weekend, or a series of evenings (everyone’s circumstances are different). If you only read one organizational management guide book, this would be the one I recommend.</p>
<p>The rest of the “<a href="http://garyslinger.wordpress.com/tag/time-management/gtd/">GTD</a>” category on this site will have comments about specific situations and scenarios relating to the implementation and use of GTD, and any relevant articles about the topic I see and recommend. The separate “<a href="http://garyslinger.wordpress.com/tag/time-management/">Time Management</a>” category will contain more general observations and links.</p>
<p>Check it out, let me know what you think &#8211; comments are always welcome.</p>
<p>(Sidebar: This is a backdated post. I’m actually writing it at 12:20 on November 20th. I want to put this into the early part of the GTD category as an explanatory post, as I intend to refer someone to this, and the whole category block. I’m also interested to see if the post, being backdated like this, turns up correctly in the RSS feed, if at all, as a basis for future knowledge).</p>
<p>Technorati Tags: <a href="http://technorati.com/tag/Time%20Management">Time Management</a>, <a href="http://technorati.com/tag/GTD">GTD</a></p>
]]></content:encoded>
			<wfw:commentRss>http://garyslinger.com/blog/2005/11/20/what-is-gtd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Myth of Multitasking</title>
		<link>http://garyslinger.com/blog/2005/11/13/the-myth-of-multitasking/</link>
		<comments>http://garyslinger.com/blog/2005/11/13/the-myth-of-multitasking/#comments</comments>
		<pubDate>Sun, 13 Nov 2005 07:00:40 +0000</pubDate>
		<dc:creator>Gary Slinger</dc:creator>
				<category><![CDATA[Time Management]]></category>

		<guid isPermaLink="false">http://garyslinger.com/blog/2005/11/13/the-myth-of-multitasking/</guid>
		<description><![CDATA[http://www.flickr.com/photos/timothymorgan/62139938/
I don&#8217;t know that I agree, but the picture amused me.
 
technorati tags: GTD
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.flickr.com/photos/timothymorgan/62139938/">http://www.flickr.com/photos/timothymorgan/62139938/</a></p>
<p>I don&#8217;t know that I agree, but the picture amused me.</p>
<p> </p>
<p>technorati tags: <a href="http://technorati.com/tag/GTD" rel="tag">GTD</a></p>
]]></content:encoded>
			<wfw:commentRss>http://garyslinger.com/blog/2005/11/13/the-myth-of-multitasking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>On GTD and “Conversational” Email</title>
		<link>http://garyslinger.com/blog/2005/11/08/on-gtd-and-%e2%80%9cconversational%e2%80%9d-email/</link>
		<comments>http://garyslinger.com/blog/2005/11/08/on-gtd-and-%e2%80%9cconversational%e2%80%9d-email/#comments</comments>
		<pubDate>Wed, 09 Nov 2005 00:21:33 +0000</pubDate>
		<dc:creator>Gary Slinger</dc:creator>
				<category><![CDATA[GTD]]></category>
		<category><![CDATA[Time Management]]></category>

		<guid isPermaLink="false">http://garyslinger.com/blog/2005/11/08/on-gtd-and-%e2%80%9cconversational%e2%80%9d-email/</guid>
		<description><![CDATA[Written for a friend of mine, who receives a lot of email that isn&#8217;t always actionable, but needs to be processed &#8220;right now&#8221;, and was suffering some overload as a result. 
Email Processing and GTD, Some Thoughts
Starting Assumptions/Perceptions/Facts:

Receives approximately 50      pieces of email direct to his inbox, per day, not [...]]]></description>
			<content:encoded><![CDATA[<p><em>Written for a friend of mine, who receives a lot of email that isn&#8217;t always actionable, but needs to be processed &#8220;right now&#8221;, and was suffering some overload as a result.</em> </p>
<h2 align="center"><strong>Email Processing and GTD, Some Thoughts</strong></h2>
<p>Starting Assumptions/Perceptions/Facts:</p>
<ul>
<li>Receives approximately 50      pieces of email direct to his inbox, per day, not counting mailing list      messages.</li>
<li>Gets overwhelmed with 20 4- and      5-way conversations in brief (10 minute) periods of time.</li>
<li>Isn’t doing formal weekly      reviews at present.</li>
</ul>
<p> It’s important to remember from the get go that GTD is a system that sets out some guiding principles, rather than being an absolute set of procedural rules that have to be followed.  Almost everyone that implements GTD, unless they actually work for the David Allen Company, are going to end up “tweaking” it somewhat, either modifying, removing or adding components, thoughts and methods, from other formal methodologies or from their own experiences, for their personal comfort and benefit.</p>
<p>That said, GTD is predicated on a couple of core elements:</p>
<ul>
<li>That <em>everything</em> goes into the trusted system, regardless of what      that system is (Outlook, 3&#215;5 cards, Moleskine, segments of toilet tissue      stuck to the wall, whatever), unless it can be dealt with in a 2-minute      “do it and lose it” moment.</li>
<li>That trusted system has to be      reviewed on a regularly scheduled basis.       This is summed up in the phrase “Weekly Review”, as that turns out      to be one of the most common, and “better” review frequencies.</li>
</ul>
<p> Dealing specifically with you, I think one of the first things that I suggest is differentiating your email as soon as you see it into one of two types:</p>
<ul>
<li>Conversational email, which is      the 4- and 5-way stuff referred to in my assumptions, based on our chats,      and which you have a service level responsibility to address as quickly as      possible, and</li>
<li>Non-conversational email –      everything else, that comes in directly to you, and can be dealt with in      the normal GTD process – do it, defer it, delegate it, or delete it.  </li>
</ul>
<p>As an aside – I’m completely not considering mailing list email – my (brief) view on that is that if it’s important, and needs participation, process it as part of your regular email processing.  If it’s informational only, put it somewhere out of sight, and refer to it as and when you have the spare bandwidth for this.<a></a></p>
<p>So, where are we?  My understanding is that you’d like to “work from zero” in the Inbox, which is a good principle to work to, but that you’re getting overwhelmed, somewhat, with the conversational email.  Turning email off and only processing it once an hour or so isn’t an option, because of your service level agreements.  My ideas are outlined below, but they rely on two extra Outlook tools:</p>
<ul>
<li>the Getting Things Done      Add-In.  Not everyone is comfortable      with this, but equally, a lot of people are, and I think it’s somewhat      underrated.  It <em>does</em> take a little bit of practice and getting used to, but      it’s actually a very good “straight” interpretation of the GTD principles,      IF you can accept using the Outlook Tasks interface.  Not everyone can…  An alternative is to implement the      equivalent of this yourself, using either the PDF that David Allen publishes,      or home-brew.  Consistency is going      to be important though.</li>
<li>Any of the readily available      desktop/email searches, emphasis on the email.  My current preference is the MSN Desktop      Search, but LookOut, Google or Yahoo variants are all going to work out      fine.</li>
</ul>
<p> So, specific recommendations – this is based on me thinking through “if I was in  position, how would I make this work?”.  These are ONLY suggestions, and I readily recommend ripping them apart and customising them to yourself, and even ignoring them completely if that’s appropriate to you.</p>
<ol>
<li>Have Outlook visible on a second monitor if possible, as a reduced size window if not, or check it regularly via Alt-Tab, new message popups, or the display “toast” feature.  You may want to do some more tweaking with your auto-preview and preview-pane options here – what has worked previously may need to be tweaked to deal with things in a GTD manner.</li>
<li>If new mail comes in and it’s conversational, deal with it.  Engage in the conversation, get information as needed, provide information and solutions as requested – that’s what they’re paying you for J</li>
<li>If you generate <em>Actions</em> as a result of those conversations, and you’re not going to do them right-away, remember you’re only a hot-key away from putting that task into Outlook – CTRL-SHIFT-K.</li>
<li>When you’ve finished your conversation emails, LEAVE THEM.  Just leave them in the Inbox.  They’re marked read.  Don’t worry about them.</li>
<li>While you’re flying through your Inbox dealing with the Conversational stuff, if you come across a Non-Conversational, LEAVE IT ALONE.  Leave it marked unread, and move on to the next message.  The only exception I’d make to this is if you get something that’s clearly instantly deletable – the announcement about a car with its lights left on (unless it’s yours!), the “donuts in the kitchen!” announcements, etc.</li>
<li>Plan a couple of “Process Email” tasks into your day.  I can’t recommend specific times and durations, because that’s going to be unique to you, but play around with it.  And then USE those times – process the unread mail in your Inbox – because it’s ALL non-conversational, REAL email to you.  One at a time, by the book – read it, and then delete it, defer it, delegate it, or do it.  Remember that you can still have your Rules setup to bypass this and alert you, me and the National Command Authority if necessary for messages from your wife, your boss or your bookie…  Remember, the idea is to get to a “trusted system” – put whatever safeties in place you need to make that happen.[i]</li>
<li>When you’re processing these non-conversational emails, you should also be moving them out of your Inbox as you process them:<br /> 
<ul>
<li>Delete – that’s obvious.</li>
<li> Delegate – use the Add-In button.  Forward the message where it needs to go, and if you need to, have it put a reminder on your calendar or task list.  Both options are there.  The Add-In will move it out of your Inbox.</li>
<li>Defer – put it on your calendar or your task list, whichever is appropriate.  The Add-In will move it out of your Inbox.</li>
<li>Do it – do whatever’s there, and then file or delete the message, or file the message for later reference.  One of the reasons I suggested the desktop/email search is to make filing easier – just put everything in the same archive folder.  Retrieve it using the search application.  By all means, put a GTD Project tag onto the email if appropriate.</li>
</ul>
<ul>     </ul>
</li>
<li>At the end of every day, go back to your Inbox, and move all those messages that are left into the archive folder – because all that’s left there now is those marked-as-read, conversational emails, right?</li>
<li>At the end of the day, consider doing a mini-review.  Have a look at your calendar for tomorrow – anything coming up you’d forgotten about, missed the reminder of, etc.?  Run through your task lists – anything showing a deadline, or anything that just makes you go “uh oh” when you see it, and make you want to pull it into the calendar, or even your Inbox?  (There’s a button in the Add-In that can instantly move anything you’ve processed out of the Inbox back TO the Inbox.  You can do this to reprocess it, if you want to.  It’s not recommended, but there are exceptions to every rule!).</li>
<li>The biggie.  At least once a week, if you’re going to do this, you’re going to have to find time to do a proper Review.  Scharff used to say “if you can’t Measure, you can’t Manage” – well, the GTD version of this is “if you don’t Review, you aren’t Getting Things Done”.  There are a number of checklists out there that include a LOT of things you can include in your Review, and I can send you one if you want, but at a fundamental level, you just need to know that everything you’ve put into your system is in a place that it’s going to get done – either the Calendar, or appropriate context-based Task items, and that you’re aware of what’s coming up.</li>
</ol>
<p>After that, possibly the hardest part of the concept, and one that needs some personalisation, is “working in contexts” – you have to be able to sit there and go “OK, I’m in the office.  I have no conversational emails to process, and I’ve processed my Inbox to empty.  I have three hours before my next time-based activity (the calendar stuff), so I’ll look at my tasks and see what I have in “@Office” and “@Computer” and see what’s appropriate to work on now.</p>
<p>If you find you have stuff on context lists that you’re consistently not doing or not getting to – take them off the context list and put them on the calendar.  Commit yourself to doing them in that time.</p>
<p>There’s no doubt that implementing time management methodologies, of any flavor, requires change both in perception and in the mechanics of how things are done on a day to day basis, and sometimes in the usage of tools.  Sometimes those changes are easy, and sometimes not so.  Experimentation is necessary, although there’s a trap of “too much experimentation” – the goal is for you to find a methods that works for you, is comfortable, and perhaps most importantly is EASY so that you keep doing it.</p>
<p>Everything before this is just my thoughts.  I hope they help.  Do let me know how you get on.</p>
<p>Gary<br />  2005-10-17</p>
<div>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;  </p>
<div>
<p>[i] Remember that one of the fundamentals of the GTD process is splitting out and differentiating between COLLECTION (the 3&#215;5’s, Outlook tasks or emails to yourself, post-its, whatever), PROCESSING (working through your Inbox(es) and getting Actions entered into your system, and DOING (when you pick an appropriate context and get on with it).</p>
<p> </p>
</div>
</div>
<p>Technorati Tags: <a href="http://technorati.com/tag/Time%20Management">Time Management</a>, <a href="http://technorati.com/tag/GTD">GTD</a></p>
]]></content:encoded>
			<wfw:commentRss>http://garyslinger.com/blog/2005/11/08/on-gtd-and-%e2%80%9cconversational%e2%80%9d-email/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GTD, Contexts, and “Break/Fix”</title>
		<link>http://garyslinger.com/blog/2005/11/02/gtd-contexts-and-%e2%80%9cbreakfix%e2%80%9d/</link>
		<comments>http://garyslinger.com/blog/2005/11/02/gtd-contexts-and-%e2%80%9cbreakfix%e2%80%9d/#comments</comments>
		<pubDate>Wed, 02 Nov 2005 20:38:10 +0000</pubDate>
		<dc:creator>Gary Slinger</dc:creator>
				<category><![CDATA[GTD]]></category>
		<category><![CDATA[Time Management]]></category>

		<guid isPermaLink="false">http://garyslinger.com/blog/2005/11/02/gtd-contexts-and-%e2%80%9cbreakfix%e2%80%9d/</guid>
		<description><![CDATA[In a discussion, the comment was made:  

&#8220;I&#8217;m getting there.  [&#8230;] Break/Fix messes with it some, but it&#8217;s a help.&#8221;
To which I offered my reply/opinion/advice:  
It shouldn&#8217;t &#8211; other than  possibly leading to an occasional long day&#8230;  Break/Fix, at least the way I  look at it, is just another [...]]]></description>
			<content:encoded><![CDATA[<p>In a discussion, the comment was made:  </p>
</p>
<div align="left"><em>&#8220;I&#8217;m getting there.  [&#8230;] Break/Fix messes with it some, but it&#8217;s a help.&#8221;</em></p>
<p>To which I offered my reply/opinion/advice:  </p>
<div>It shouldn&#8217;t &#8211; other than  possibly leading to an occasional long day&#8230;  Break/Fix, at least the way I  look at it, is just another context.</p>
</div>
<div> </div>
<div>Scenario:</div>
<div>
<ul>
<li>You&#8217;re busy working away at  something from your &#8220;@Office&#8221; context, because there&#8217;s nothing on your calendar  right now.</li>
<li>Something occurs that needs you to  stop, and go do Break/Fix.  </li>
<li>You return to your desk (or, you  stop doing whatever remote-control you were doing, etc.  This is one of the  reasons Context is a good thing to think about &#8211; it <em>isn&#8217;t</em> necessarily a  location thing, it&#8217;s a <em>what am I working on</em> thing).</li>
<li>If you generated any new Next  Actions as a result of your break/fix work &#8211; they go into the  system.</li>
<li>Right &#8211; anything on the calendar?   No &#8211; OK, time to go home yet?  No &#8211; OK, back to context  thinking.</li>
</ul>
</div>
<p>The risk is that whatever you were  working on in that @Office context is something that&#8217;s actually due today, and  it&#8217;s now 16:30.  One argument would be that last week&#8217;s Weekly Review (because  you did do a Weekly Review, didn&#8217;t you? <img src='http://garyslinger.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' />  would have identified the upcoming  deadline, and you&#8217;d have booked hard-time into your calendar to work on it.   Cool.  But then the counter-argument is that break/fix comes along and you don&#8217;t  get to <em>use</em> that hard calendar time.  That&#8217;s where my &#8220;occasional long  day&#8221; comment comes in &#8211; that&#8217;s just an unfortunate aspect of Operations.  The  underlying reality is that most ducks are smart enough to build slack time into  any deadlines they give you, and if you genuinely couldn&#8217;t do something, because  of break/fix, you can probably use that slack time.</p>
<p>Or stay in the office until Midnight  </p>
</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://garyslinger.com/blog/2005/11/02/gtd-contexts-and-%e2%80%9cbreakfix%e2%80%9d/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.539 seconds -->
