 | whibs says: Great tips! As a result of playing with these ideas I've hit upon an idea for maintaining lists of projects and associated tasks. Before I go into that, I shall summarize my system so far (largely based on the ideas of others and subject to change!)
Locations: @Errands, @Personal, @Work
These are my contexts. I noticed that locations appear in the tag cloud, which may be useful to list every task for the context regardless of task 'type' (ie. action, someday etc). Also, the @ notation ensures all contexts are grouped at the top of the cloud. Nice!
Lists: Inbox, GTD, WishList, Sent
All my GTD stuff goes into one list, as I've found that it's a bit cumbersome to transfer tasks between lists (no keyboard shortcuts), but that's something I can live with when manipulating the Inbox contents.
Smart Lists (cryptic names for nice narrow tabs):
Name: @E_a
Description: @Errands - next actions. 'Due' and 'Time' should be set for each task.
Search string: list:GTD AND location:@Errands AND tag:_action
Name: @E_s
Description: @Errands - someday/maybe. 'Due' and 'Time' not set.
Search string: list:GTD AND location:@Errands AND tag:_someday
Name: @P_a
Description: @Personal - next actions. 'Due' and 'Time' should be set for each task.
Search string: list:GTD AND location:@Personal AND tag:_action
Name: @P_p
Description: @Personal - projects list. Each project should have a unique 'pn_name' tag, where n is the initial of the context and name is a meaningful name for the project (see later).
Search string: list:GTD AND location:@Personal AND tag:_project
Name: @P_s
Description: @Personal - someday/maybe. 'Due' and 'Time' not set.
Search string: list:GTD AND location:@Personal AND tag:_someday
Name: @P_w
Description: @Personal - waiting for. 'Due' set to mark when the task was set to waiting status.
Search string: list:GTD AND location:@Personal AND tag:_waiting
Name: @W_a
Description: @Work - next actions. 'Due' and 'Time' should be set for each task.
Search string: list:GTD AND location:@Work AND tag:_action
Name: @W_p
Description: @Work - projects list. Each project should have a unique 'pn_name' tag, where n is the initial of the context and name is a meaningful name for the project (see later).
Search string: list:GTD AND location:@Work AND tag:_project
Name: @W_s
Description: @Work - someday/maybe. 'Due' and 'Time' not set.
Search string: list:GTD AND location:@Work AND tag:_someday
Name: @W_w
Description: @Work - waiting for. 'Due' set to mark when the task was first set to waiting status.
Search string: list:GTD AND location:@Work AND tag:_waiting
Name: Cmplt
Description: 'Pat on the back' list of recently completed tasks.
Search string: list:GTD AND completedWithin:"2 weeks of today" AND isRepeating:false
Name: Qck
Description: Lists all action tasks estimated to take 20 minutes or less.
Search string: list:GTD AND timeEstimate:"< 21 min" AND tag:_action
Name: Rpt
Description: Lists all repeating action tasks.
Search string: list:GTD AND isRepeating:true AND tag:_action
Name: SevenDays
Description: Lists all action tasks due in the next seven days (excluding repeating tasks).
Search string: list:GTD AND dueWithin:"7 days of today" AND status:incomplete AND isRepeating:false AND tag:_action
Name: Today
Description: All action tasks due today and overdue tasks.
Search string: list:GTD AND dueBefore:tomorrow AND tag:_action
Name: Urgent
Description: Tasks which should have been actioned but haven't (yet).
Search string: list:GTD AND (dueBefore:today OR postponed:"> 5") AND tag:_action
Name: W/E
Description: All action tasks intended to be actioned at the weekend.
Search string: list:GTD AND (dueWithin:"1 day of sat" OR dueWithin:"1 day of sun") AND tag:_action
Name: zCont
Description: Audit list - show all tasks which haven't had a context (location) defined
Search string: list:GTD AND isLocated:false
Name: zDue
Description: Audit list - show all action tasks which haven't had a due date defined.
Search string: list:GTD AND due:never AND tag:_action
Name: zTag
Description: Audit list - show all tasks which haven't been tagged with anything at all.
Search string: list:GTD AND isTagged:false
Name: zTime
Description: Audit list - show all action tasks which haven't had a time estimate set.
Search string: list:GTD AND (NOT timeEstimate:"> 0") AND status:incomplete AND tag:_action
List inheritance behaviour
One neat feature I've noted of RTM is that new tasks created under any smart list will inherit the tags and location defined in that list's search string (provided the search is unambiguous i.e. there are no ORs in that search string). This makes adding tasks for a particular context and task type simplicity itself. For instance, creating a new task in the @P_a smart list will automatically set the location to @Personal and tag the task with '_action'. Cool!
Projects list manipulation.
Handling lists of projects is a little more involved, and I'm merely piloting this process at the moment, so time will tell if it can be deemed effective. Say in the @P_p smart list, one would create tasks to represent projects. Those projects should automatically get tagged with '_project' and have the appropriate context (location) set. Once the 'title' task is created, add a unique tag to represent that project. For instance, a new project could be called 'Clear out the garage'. Tag that project description task with 'pp_clear_garage' or similar. The pp at the beginning of the tag distinguishes it as a project in the @Personal context. A work project would be prefixed with 'pw_' and so on. This ensures that all project tags are grouped together in the tag cloud, both by the fact that they're projects and further by context. This tag provides the link between the project name and its constituent tasks. If a project has a due date, set it here along with an estimated time if you so desire.
Now when we wish to define a task or two for that project, click on that project's tag to get a quick list of all tasks with that tag (which to start with will consist only of the title task). Now you can happily add tasks which will be auto-tagged with the project's unique tag. Unfortunately, you will need to define the context (i.e. location:@Personal) and task type (i.e. tag:_action) yourself. You could get around this by creating smart lists for each project (i.e. list:GTD AND location:@Personal AND tag:pp_clear_garage AND tag:_action) but in my opinion this would be to much work to keep on top of.
A quick list for a project's tag will list the project title task as well as its actions. If you have a due date set for the project title it will likely be lurking at the bottom of the list in this view. If you don't usually use priorites (I don't) then I recommend setting a priority to the title task so it will always appear at the top of the list and provide a header of sorts. This also ensures that a list of projects stands out, reinforcing the idea that this kind of list is distinct to the other list types in a GTD system.
So, when it comes to reviewing our projects, how can we see at a glance that all our projects have next actions defined? Simple - hover your mouse over the project tags in the cloud to get the task count tooltip for each project. If a tag's tooltip shows '1 task' then it has no actions defined (it contains the title task only), more than that indicates an active project, which is what we want for each project if at all possible.
Tags summary
The tag cloud should feature these tags in this order:
Contexts (locations): @Errands, @Personal, @Work etc.
Task types: _action, _project, _someday, _waiting
(gtd, inbox): master lists
Project tags: pp_clear_garage, pw_write_program, etc.
(sent): master list
Wishlist categories: w_photography, w_gadgets, etc.
(wishlist): master list
Now that I've finished procrastinating by creating this post rather than doing some real work, it's time to see if this system will actually work for me! Hope it's helpful to all you GTD-loving milkers out there! Of course, I'm open to further suggestions. Posted 5 years ago |