Screencast: Yet another set of GTD conventions
rmm5t says:
I'm a newcomer to RTM. I started a few days ago, and I decided to cold-turkey switch from GTDInbox for various reasons. I put together a screencast to help some friends get started with RTM. Like many, I too am influenced by Getting Things Done. I figured my screencast might benefit others as well, so here it is:
http://ryan.mcgeary.org/screencasts/RTM-GTD-Conventions/
(Note, I have since refined the <30d smart list definition after recording this.)
I'm sure I'll continue to refine and add more smart lists as I become more familiar with RTM, but here are my current smart list definitions.
!:
isTagged:false
<30d:
not(tag:-someday) (due:never or dueBefore:"30 days")
>30d:
not(tag:-someday) (dueAfter:"30 days")
?:
tag:-someday
@computer:
tag:@computer list:<30d
@home:
tag:@home list:<30d
@out:
tag:@out list:<30d
etc...
Comments and constructive criticism welcome.
http://ryan.mcgeary.org/screencasts/RTM-GTD-Conventions/
(Note, I have since refined the <30d smart list definition after recording this.)
I'm sure I'll continue to refine and add more smart lists as I become more familiar with RTM, but here are my current smart list definitions.
!:
isTagged:false
<30d:
not(tag:-someday) (due:never or dueBefore:"30 days")
>30d:
not(tag:-someday) (dueAfter:"30 days")
?:
tag:-someday
@computer:
tag:@computer list:<30d
@home:
tag:@home list:<30d
@out:
tag:@out list:<30d
etc...
Comments and constructive criticism welcome.
rmm5t says:
Heh, I just realized a flaw in my date logic. The "<30d" list should really find everything before 31 days to avoid hiding tasks that are exactly 30 days away:
<30d:
not(tag:-someday) (due:never or dueBefore:"31 days")
<30d:
not(tag:-someday) (due:never or dueBefore:"31 days")
thorrrr says:
Hi not sure how you are covering every area! Do you have a MSN or Yahoo address if so email me at daleholden@gmail.com
scott.elias says:
This is wonderful. I sometimes get a little overwhelmed reading through people's "this is how I use RTM" posts, but this was crystal clear. A testament to the power of simple screencasts!
n5csu says:
Great screencast and very helpful. I just changed my system to these conventions, tweaked to <10 days, <30 days, 30 or more, and someday. Thanks for sharing!
- Rich
- Rich
bzpilman says:
That's a really cool thing to do, nice screencast!
For your symbols/prefixes of tags are very similar to mine, you might want to check this thread out.
For your symbols/prefixes of tags are very similar to mine, you might want to check this thread out.
poeminlash says:
Great trick. I like the way you use the smartlist. I also create several regular lists: actions, projects, non-actions and checklists. I use priority to color tasks and to differentiate the active actions and projects (those being assigned with actions) and the inactive actions (waitingfor ones) and inactive projects （maybe-someday ones). Then I create "calendar" and "next" smartlists to take advantage of the GTD structure.
taltos1 says:
Thank you very much. This is a great mini-tutorial on how to set up a GTD system in RTM.
derek.conjar says:
This is the simplest and easiest-to-follow concept I've found for using RTM for GTD. The only constructive criticism that I have is that the system relies on due dates instead of actions, next actions, and waiting-on's, which seems a little contrary to GTD.
maseratij says:
Shouldn't this layout be on top every week? It really looks simple to me and natural for the smart search strength's. Add this with one of those crazy cloud hacks and boom!!!!!!!!!!!!!! You'r getting things done
rmm5t says:
I just realized my original link to this screencast went dead a while ago. I just republished the screencast here:
http://ryan.mcgeary.org/screencasts/2008/01/02/remember-the-milk-conventions/
http://ryan.mcgeary.org/screencasts/2008/01/02/remember-the-milk-conventions/
rmm5t says:
Log in
to post a reply.