I have been using RTM for maybe half a year now and I've changed the way I worked with it several times, but finally I have settled on a system based on GTD that works *really* well for me. I might need to make a few adjustments in the future, but I expect the basic setup to remain unless RTM introduces more flexible searches.
Quick summary for eager people:
One list (Inbox), only smart lists, locations used for contexts, specific location used for project identifier, tags used for projects, tags used for someday and waitingfor. "Inbox" is defined as any task with no location.
In more detail:
I never felt comfortable with having several lists, so I decided to go with an approach where I place every task in the Inbox, and then I apply smart lists on this list.
These are all my smart lists, with query
@Work: location:Work and (due:never or dueBefore:tomorrow) and not tag:waitingfor and not tag:someday
@Errand: location:Errand and (due:never or dueBefore:tomorrow) and not tag:waitingfor and not tag:someday
@Personal: location:Personal and (due:never or dueBefore:tomorrow) and not tag:waitingfor and not tag:someday
Calendar (Today): dueBefore:tomorrow
Calendar (This Week): dueWithin:"1 week of today"
Open Loops: isLocated:false
Waiting For: tag:waitingfor
I use @Work for items I would do at work @Errand for things when on the move and @Personal is a more general thing for when at home, have a few minutes to spare etc. I previously tried to have more contexts than these, but in the end, for me, the complexity wasn't worth it and I settled for these.
I use tags to specify a task as "someday" and "waitingfor". These are then not shown in the contexts' next actions. I first used locations for these markers as well, but I didn't like it as I wanted to preserve the original context (say Work) when putting something as someday. With tags I can as a task can have several tags.
For each project, I create a task with a descriptive name, give it a suitable unique tag and place it in the Project location. The purpose of this task is two-fold. One, it makes it easy for me to create a "Project list", and two, it makes sure the project tag is always visible in the tag cloud to the right. By clicking on the tag in the cloud, I get a nice view of all tasks, include someday, waiting for etc.
For my weekly review, I check all projects and make sure a next action is defined. In a perfect world, I would like a project to show up in "Open Loops" if there are no next actions, but such query is impossible to define in RTM with this setup. If I could create a query like "show tasks having tag x and there are only 1 task with that tag uncompleted" I could do it, like "tagCount:"xxx = 1".
I have toyed with using priorities in RTM to represent next action, waiting for, someday and so on, but never felt comfortable with it. Instead, I now use them to make a quick 'n dirty ordering in each context. For example, I work as a developer, so I tend to give all @Work tasks that are bugs priority 1 to make sure they are placed at the top.
Other than that, it all seems to work out nicely. I work on tasks depending on context. I often forward mails to my RTM-mail and input quick tasks descriptions with no tags and location that I then later process from Open Loops.
Posted at 4:09pm on November 3, 2010