
Originally Posted by
MollyLolly
Thanks for all of the input. Your comments are all very helpful.
Here is my follow-up question(s): It seems that the natural work flow for me is to work on a project basis. Not to work on a NA basis (i.e., not to sit down and make all my phone calls, etc.). So I sit down at my desk to work on Client X's stuff because it is the most critical or the next highest priority. That may entail several different types of NAs (as in my example: reviewing, drafting, conferring, etc.). Therefore it would seem cumbersome to sit down to work on Client X's project and then have to scan several different lists to know what the NA is (e.g., @waiting for, @review; @computer, etc). Thus, I can see the benefit of a modified GTD approach described by Esquire (where you simply list the next actions under the particular client project. But I don't know if I am missing the point of the whole GTD approach or perhaps not fully understanding the way the NA lists function.
Bookmarks