Bare with me on this.....I am frustrated with getting next actions captured and processed. Perhaps it is too much input, maybe not.
I am using Outlook 2007 and NextAction! on a Blackberry 9000.
My question concerns the use of projects. In my work I will numerous tasks, calls and details to control in the process of completing a sale. My expectation is that I can contain all of those details in my task list and that the they will be connected to the specific project. I also have the usual list of general GTD tasks, it is on the general list that all of my next actions begin.
Is it logical to think that these actions should be (somehow) listed under the specific .project? Or do these task get completed and spawn a next action and never link to a specific project?
The more I describe my confusion the more I seem to be asking for a general explanation of projects and how they are used.
I have purchased the Outlook implementation white paper, I have been somewhat impatient with working through it. I did do a more thorough job with the 2003 guide.
I am using Outlook 2007 and NextAction! on a Blackberry 9000.
My question concerns the use of projects. In my work I will numerous tasks, calls and details to control in the process of completing a sale. My expectation is that I can contain all of those details in my task list and that the they will be connected to the specific project. I also have the usual list of general GTD tasks, it is on the general list that all of my next actions begin.
Is it logical to think that these actions should be (somehow) listed under the specific .project? Or do these task get completed and spawn a next action and never link to a specific project?
The more I describe my confusion the more I seem to be asking for a general explanation of projects and how they are used.
I have purchased the Outlook implementation white paper, I have been somewhat impatient with working through it. I did do a more thorough job with the 2003 guide.