I’m trying to implement a Getting Things Done (GTD) system which works for me and which I can stick at on an ongoing basis. I’ve tried various set-ups in the past but constantly find them becoming derailed and eventually abandoned. In the process, however, I’ve seen enough to know it is something I want to get working more permanently. I’m making a push at the moment to get a proper system that works for me and that I continue to use. I’ll keep my progress posted on this site.
Online or Offline GTD Implementation?
The first issue is (as I see it) the big one. The main reason GTD hasn’t worked for me to-date has been that I’ve never found the right balance between online and offline. Previous systems have either been almost entirely computer-based and then failed because I spend most of my time away from the computer / my @computer list is the largest and I need all my online time for clearing it. Or they’ve been largely offline (i.e. in a notebook or organiser) and have failed as they are too bulky to carry around or are too inflexible to use. The offline systems are further affected by the fact that much of my offline time is not in contexts suitable for use of the system.
It seems to me that my ideal system will have to be somewhat of a mix between online and offline. It will also need to be workable with inconsistent and limited time in each context.
Some ideas I have which I’d like to try implementing:
- Having lists stored / in the most appropriate format for where they’ll actually be used. For example computer actions should be stored in a text, excel, or similar file on my laptop / usb key, while errand actions should be stored in a lightweight notepad or similar that I can carry with me anywhere.
- A central offline store for projects which is used to farm actions out to the appropriate lists. I’m thinking about having a large notebook which acts as the processing phase of GTD exclusively – inboxes will get summarised into there in terms of the projects / actions they inspire. Then the projects can be extracted to a list somewhere and the actions farmed to the distributed lists as and when appropriate. This processing setup would also let me make good use of the relatively large amount of time I have where I’m able to work on my own stuff but don’t have computer access (which was the Achilles’ heal of my attempted online systems).
- I may make that central processing notepad small enough to be portable if needed (I’m thinking legal pad / moleskine…).
Mixed Online / Offline GTD System
So I’m going to give the mixed online / offline system a go. It’ll take more work to set up and get going, but hopefully it will let me tailor individual parts of the system to more neatly integrate with my situation.
To kick it off, I’m going to begin with the following:
- A medium-sized notepad (large enough not to feel restrictive, small enough to be portable if needed). This will be used as a funnel into which all inboxes are emptied and processed. It will contain a series of entries, each a single line identifying a project and the next action on that project. These will be scored off as I farm them out to the various lists.
- A pocket-sized diary for calendar items
- A pocket-sized notepad for entering @errand / @anywhere tasks.
- A medium-sized notepad for @home tasks
- A text file for @computer tasks (stored on my usb key)
- A medium-sized notepad for project / someday maybe lists
Note that I already have reasonable systems in place for initial capture – that’s something I do to a decent enough standard for the time being.
During offline time I will process inboxes into the processing pad. Then as appropriate I’ll move items onto the distributed lists when I’m in the appropriate context to do so.
Next Actions
I could go elaborate endlessly on the details, but I’ll save that for later. Today I’ll focus on two things:
- Getting hold of the various notepads, etc.,
- Making a start on processing some of my inboxes into the processing pad,
- Doing any two minute actions which show up during that time.