OmniOutliner Revisited

After much experimentation, I've settled on a new OmniOutliner document setup for tracking todo items. Refined from the more strict-GTD arrangement I described on the main OmniOutliner page, this better reflects my workload. It will inevitably change, but evolution is a good thing (no matter what certain folks in Kansas might think).

First up in my Currently.oo3 document is a set of top-level items covering various timespans:

( ) This week
( ) 11/21 Mon
( ) 11/22 Tue
( ) 11/23 Wed
( ) 11/24 Thu
( ) 11/25 Fri
( ) 11/26 Sat
( ) 11/27 Sun
( ) Next week
( ) Later dates

"This week" are tasks I want to get done, appropriately enough, at some indeterminate time this week, while the dated days hold tasks that need to be done on particular dates/times. "Next week" holds stuff that is either scheduled for or postponed until that point, and "Later dates" correspond to the dated days, but next week or even further out -- as long as they're specific days.

Next, we have categories of stuff, @Contexts in GTD parlance:

( ) 1414
( ) Food
( ) Health and fitness
( ) House and home
( ) Office
( ) Reading and watching
( ) Travel
( ) Writing
( ) Maybe later

Pretty self-explanatory -- items that need doing that don't have specific timeframes attached. These all get looked at the very least during my Sunday weekly review, usually more often.

"Maybe later" corresponds to the familiar "Someday/Maybe" category. And then my favorite category:

(x) Completed

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Allowed HTML tags: <a> <cite> <code> <strong> <em> <blockquote> <b> <i> <p> <br> <ul> <ol> <li> <small>
  • Lines and paragraphs break automatically.

More information about formatting options