Recently I started creating AtContext lists to keep things more divided
and I've discovered its a great motivational tool... It helps you avoid
that "well I can't do that right now because I'm at home/work and I
don't have what I need" excuse.
But I still have my NextActions list and I'm trying to figure out where
it fits in. Is NextActions just a catchall for things that don't fit on
AtContext lists? Or is it something higher level than that? How does
everybody else use AtContext vs NextActions lists?
Thanks,
Chris
(I'm finding that I use my Palm less-and-less for data input, and more
just as a compact and convenient reference platform. I use a
HipsterPDA for input because it's faster and it doesn't crash!)
Anyhow, that is to say that for me, I have everything in the
NextActions list and let Tinderbox take care of contexts. This means
that I need to be sure to scan the entire NextActions list at least
once-a-day since some things don't fit into a context. I suppose I
could create an "other" agent which tests for titles which have none of
the context keywords, but just scanning the NextActions list is easy
enough.
I think there's a bit of a false dichotomy here. @Context lists *are*
next action lists. The point is, you take your next actions and then
group them into contexts. The fact that you happened to have a
non-contextual next action list (NextActions) is a slight departure
from GTD's approach, but I don't think it'll kill you :-)
Personally, I've never found the contextual thing too helpful. The
following makes sense to me:
http://www.marktaw.com/gtd/ContextLists.html
--
@Computer-Home
@Computer-Office
in order to partition the personal from the professional.
I agree with a previous posts that everything in an @context is a next
action; it just has an added contextual attribute that allows you to
group-and-sort (view) them in a useful way. It's an alternative view to
the Project view (I'm a user of the GTD addin for Outlook that has a
buttons for switching quickly between these two views, which is helpful
for things like the Weekly Review).
I also agree about @Errands is out of the office context. Note that
David Allen modified this to have @Errands for general errands and
@Errands-Ojai for stuff that he could only do in vacinity of his home
(presumably things like gardening supplies and pet food).
I also take the point by MarkTAW that for people chained to your desk
who don't travel much, you are likely to have fewer contexts.
David.
http://www.davidco.com/tips_tools/tip43.html
With the Palm as my primary reminder system, I've had hundreds of
people ask about how I've structured my lists to implement the Action
to Outcome model in my seminars.
Because this may save a ton of time for people who've been through my
seminars, Im publishing this and will attempt to keep it current as I
fine-tune it. (This will also be of great value to people using any
list-based system for reminders.)
So, OK, here's the current (work-in-progress) version of my Palm
set-up:
Calendar and Tel/Add - that's pretty standard. (I do not use categories
in Tel/Add, except for Restaurants, under which I have all the local
restaurants. In case were out and about, and suddenly get the urge to
eat somewhere we haven't for a while...Otherwise The "Find" feature on
the Palm is rigorous and easy, and I just keep the tel/address list on
All all the
time.)
To-Do Lists: this is where I've installed the key reminder-type
operational lists that I review daily and weekly. Here is my current
set of categories:
- Projects (active more-than-one-action projects) - (I have about 60)
- Someday/Maybe (projects I might want to do in the future) - (I have
about 70)
(In the following categories I use the @ sign, to represent action
lists)
- @Agendas (items to cover with specific people when I am with them in
person or on the phone. Each person is listed as a to-do, and the
things to go over with them are listed in the attached Notes field)
- @Anywhere (actions that can be done pretty much wherever I am)
- @Call (actions at phone)
- @Computer (actions at computer)
- @Computer - Web (actions that require me being on line. Because I
travel so much, many times I'm not on line, so I like to distinguish
those)
- @Errands - (out-and-about things to do I can do while I'm traveling
as well as at home)
- @Errands - Ojai (out-and-about actions that require me being around
Ojai to do)
- @Home (actions that have to be done at home)
- @Office (actions that have to be done at my office)
- @Waiting For... (actions and projects other people are doing I care
about)
Memo Lists
- Clients (list of all of them, current and past)
- DA Thoughts (possible essay topics for my Food for Thoughts on the
Web)
- Dates (Birthdays and anniversaries, which it automatically sorts
chronologically, as they are listed "02-05 - John Doe")
- Focus Areas (Bigger checklists like larger goals, objectives, areas
of focus)
- Ideas??? (Crazy ad hoc ideas I want to save but don't know what to do
with)
- In development (Relationships, potential partnerships and networking
possibilities)
- Inspirations (Personal affirmations and inspiring quotes)
- Key people (Just that, a list I want to review to ensure I'm doing
what I want with the relationships)
- Lists (Weekly Review, Travel Checklist, and more than a dozen ad hoc
lists I want to keep for a while)
- Maybe Get (Books, CDs, Videos, Misc.)
- Next time in... (Lists of possible things to do by city, when I'm
there next)
- Travel (I have separate docs for each city, and the restaurants,
stores, and people to be reminded of there)
- Web articles (Ideas, themes, and topics I intend to add to this Web
site)
- Wine (Chardonnays, Chiantis, Pinot Noirs, etc. to archive for
reference)
I use both views, Context (aka, Actions in GTD plugin parlance) and
Projects. It depends on what I need to be doing. If I was looking for
calls, I'd go to @Calls, but if when my boss walks in and asks me
what's next with hiring a postdoc, I go to the Project on Hire Postdoc.
They are both NextActions lists, just with orthogonal views into the
lists.
The Project view is helpful especially when doing a Weekly Review.
David