org-mode and the magical WAIT keyword
I recently made my way through Getting Things Done (GTD). I wish I had done it a while ago! I’ve read many surface-level summaries in blog posts or in tutorials for organizational tools about how to use GTD. But, similar to programming, reading the source code can be illuminating in ways that someone else’s high-level summary cannot be.
Anyway, one realization I had in the book is that I was completely missing a key feature in my TODO tracking in
I’ve always tried to keep my TODO tracking on the simpler side, so a task was either
STRT (I began work on it) or
This works when you have a kind of tunnel vision view of incoming work: incoming task arrives, you do it, mark it as done. But thanks to reading the GTD book, I’m trying to organize my work more by short term and longer term projects. And in that context, there are a lot of times where you need to wait to make sure something is ready to start or is actually done, and I still want to have this captured in the TODO system so it’s not taking up mental space.
WAIT keyword, which I use with org mode’s
org-schedule feature. So far I use it in these situations:
- I’ve left code review comments on a patch, and I know I will re-review it after the author responds to my comments. I place a
WAITkeyword and schedule the task so that it appears in my org mode agenda in a couple of days.
- I have pushed a patch that is ready for review; I turn the
WAITand again schedule for a few days ahead, so I know to ping people for review if I haven’t gotten feedback by then.
- There’s an internal discussion where I want to give opportunities to others to weigh in, but want to make sure that if they don’t, I eventually reply:
WAITkeyword, plus schedule for later in the day or the following one.
WAIT is helping me get a whole other set of things that occupied mental space into my TODO tracking system so I don’t have to think about them anymore. I recommend trying it!