Getting in the Weeks, Part Two: Remember the Milk
On Wednesday, I started a series of posts that are meant to share an “in the weeds” view of my system for getting things done. Today, we’ll take a closer look at Remember the Milk (RTM).
I use RTM to capture all next actions. For those of you who are unfamiliar with RTM, it’s a browser based system that allows you to capture and organize all sorts of reminders. From
this screen shot, you can see that there are lots of features and ways to use this handy program. RTM is free. However, I am a “Pro” user (which costs $25 US per year) so that I can integrate more effectively with my iPod Touch. Well worth the extra cost and nice to support a great program.
When entering a task into RTM, no matter how I go about it, the task goes to the inbox. I use rather strict conventions when I enter a task which makes processing easier later on. Here’s an example. Say I need to pick up ink cartridges for my printer. The task in RTM would be: “@errands Rapid Refill black & color + exchange bad cartridge. What this works out to is: Context, Where, Action. All tasks are entered with similar conventions which gives me a list that is alphabetized by context, then an object (where, who) followed by the next action. Depending on need, tasks are then tagged with due dates.
I use the notes feature but not on a consistent basis. Most often, if I’ve entered the task using my conventions, the description itself contains enough info for me to know what to do and how to do it.
One more example should make this more clear. Here’s a task straight out of RTM: “@web bi311 check gradebook change settings midterm II.” Translated: must have internet connection to complete this task = @web; bi311 is the course I teach. The action is to check the grade book and update settings on the second midterm. I know what I mean by “update settings” but if it was an unusual task, I’d say exactly what the update entailed. This happens to be an update I do often, so I felt no need to add extra detail.
A while back, someone asked me how next actions come to me. What he was getting as was how much work comes in the form of email, how much is generated from meetings, and so on. In my world, I’ve found that next actions show up in several ways:
- Assigned tasks
- Meetings
- Self-assigned through roles, projects, higher level goals and aspirations
Assigned tasks are activities like updating the monthly Board meeting agenda for a non-profit I serve, teaching duties, and so on. Meetings generate next actions from requests and commitments made by me or made to me by others (which become “waiting for” items). Most of my work is self-assigned: this is the stuff I ask myself to do like writing, gardening, taking care of the dogs, and so on. And then there’s email.
I use three methods for getting email-generated work into RTM:
- Forwarding emails to RTM
- Using the import list function (emailing a list of tasks to RTM)
- Entering tasks directly into RTM using the browser
Linked RTM with email is probably a post unto itself, so I won't go into details here. If you want to know more, email me and I'll give you the rundown.
No matter what, all tasks in RTM start out in the Inbox. From there, I review to see if a due date is needed and if there is a clear context. Once I’m satisfied that the item is properly entered and labeled, like the task you see in this screen shot, I move the item to the list labeled “.” which is a static list that serves as a general holding tank.
From the screen shot below, you can see that I run a whole herd of lists (the tabs labeled !, < .7 d, and so on). All lists except one (the list “.”) are Smart Lists which means that RTM generates and updates each list automatically depending on Smart List search criteria I have set up. (No technical details here; want to know more? Email me.)
- ! is a sanity list. If a task has no associated context, it’ll show up here. In essence this is a fail-safe so that no task falls through the cracks. This list should always be empty if tasks have been properly entered and labeled.
- <.7d: Any tasks bearing due dates within the coming week or any overdue tasks show up here.
- <30 d: Tasks due in the next 30 days.
- > 30 d: Tasks that have due dates sometime beyond the next 30 days.
- @....: Context driven lists that are self-explanatory.
- IAC, ICF: organizations that I serve
- Someday: ideas I don’t want to lose but aren’t necessary. These are all tagged with “-someday.” When an item moves off someday and into a real context, all I have to do is delete the tag.
- Today: tasks that are due today or are overdue. I found this list necessary because RTM’s default overview for “today” doesn’t include overdue tasks.
When tasks are completed, I mark them as complete. RTM automatically re-files such tasks to a completed task list. If a task changes (i.e., is now a “waiting for”) I use a tag to indicate the change in status. That adds the task to the list labeled “@waiting for” and allows me to ignore it in the context list it continues to reside in (e.g., “@Email”) until completion.
The key to my success at using RTM is to be absolutely draconian about making sure tasks end up there. To have a trusted system means to be fully committed to it. By fully committing to RTM, I absolutely have to know that anything that needs doing is listed there. If tasks are in my head, listed somewhere else, or existing as emails, then RTM isn’t acting as my trusted system and my commitment to it will waver. That’s why it’s so important to be able to send tasks to RTM using email, the iPod Touch, or via Jott.
That’s it for tasks. Next time, I’ll take a look at my calendars.




