Howdy,
I am just starting out, and decided to use Outlook to magage my lists. I (purchased) downloaded the whitepaper from davidco and followed the directions. So I am using my "Tasks" in outlook to manage my NA lists and my projects.
Then I decided to check out the GTD plugin, and am trying to get my mind around some conceptual issues. In the manual there are references to "tasks" that seem sort of general or interchangeable with NAs. There are also "projects." Is this a new type of item within outlook created by the plugin? Or is a project really a task underneath?
As a practical matter, can I convert all of the projects I entered as tasks to "projects."
As an aside, I cant imagine how anyone could implement this system in two days! Getting the document on setting up Outlook in and of itself gave me a much strong perspective on what GTD is on a nuts and bolts level (in comparison to just the book). I am just delving in to the plugin, scanning through the manual. I think I see a bit more of how this works. There are projects with lists of actions attached to them. The plugin helps organize this.
I have been wondering about how to handle a list of actions conected with a project. Let's say my project is clean the basement. As I create it, I automatically think a bunch of actions: buy cleaning supplies
rent shop vac
call friends for help
call city for old appliance pickup tag
etc...
Obviously these cant all be NA by definition. Does it make sense just to "stage" them in the project to be picked from for the NA. Or should they all go onto the various context lists as NAs?
Anyhow, I combined some conceptual questions with some practical questions about the Outlook plugin. I hope my meaning is clears.
If anyone can stear me straight it will be much appreciated.
You all seem so nice here!
Best,
Brian
I am just starting out, and decided to use Outlook to magage my lists. I (purchased) downloaded the whitepaper from davidco and followed the directions. So I am using my "Tasks" in outlook to manage my NA lists and my projects.
Then I decided to check out the GTD plugin, and am trying to get my mind around some conceptual issues. In the manual there are references to "tasks" that seem sort of general or interchangeable with NAs. There are also "projects." Is this a new type of item within outlook created by the plugin? Or is a project really a task underneath?
As a practical matter, can I convert all of the projects I entered as tasks to "projects."
As an aside, I cant imagine how anyone could implement this system in two days! Getting the document on setting up Outlook in and of itself gave me a much strong perspective on what GTD is on a nuts and bolts level (in comparison to just the book). I am just delving in to the plugin, scanning through the manual. I think I see a bit more of how this works. There are projects with lists of actions attached to them. The plugin helps organize this.
I have been wondering about how to handle a list of actions conected with a project. Let's say my project is clean the basement. As I create it, I automatically think a bunch of actions: buy cleaning supplies
rent shop vac
call friends for help
call city for old appliance pickup tag
etc...
Obviously these cant all be NA by definition. Does it make sense just to "stage" them in the project to be picked from for the NA. Or should they all go onto the various context lists as NAs?
Anyhow, I combined some conceptual questions with some practical questions about the Outlook plugin. I hope my meaning is clears.
If anyone can stear me straight it will be much appreciated.
You all seem so nice here!
Best,
Brian