As you said over 300 "N/As", not all of them are truly next actions, considering it īs your
first time on gathering everything, I think that is normal.
Definetively, donīt stop the brainstorming...
I have some moments where I can see several things that need to be done; it saves me from
having to get into the brainstorming mode later on, when I've run out of ideas.

You said that you couldn't avoid stopping your mind from thinking ahead 3 or 4 actions, itīs good,
brainstorming working, now you must to transfer this "false N/As" to each proyect.
Iīm agree with other members : each project is a case !.
Besides you must have a Project Control page with a minimum data (status deadlines
%completed)
Personally, I have a folder for each project with the following categories1page for each one)
· Action plan: see how it is organized below.
· Ideas
· Notes
· Subprojects > only if it is necessary.
Now, how to manage the 300 "N/As", join the n/as for each project (case), surely will be 3 or more
for each one.
Brainstorm all the activity you will need to complete this project. In your project folder open the
section " action plan ", put them there. Donīt put these actions on your Next Actions list !
( See an example in my page)
When you finished, choose one action to put in the "next action" section (it must be done this
current week)
Now in this way you have until 60 true "N/As" and 60 project to track.
When I'm starting a project and ideas are popping, I write them all down in a list - this list belongs
in my project folder "ideas". It stays with the project file, and is not considered my actual NA list.
The action plan is organized in this way:
(you can find a better image in http://voipdar.atspace.us/memberlz11.htm)
-------------------------------------------------------------------
|................................................. ..........................................|
|..PROJECT A................................................. ..........................|
|..Next Action : 2- Finalize staff meeting.....................................|

|......Action Plan.............................................. .........................|
|.|#|ok|........Action .............. | due | Transfer |Context.......|
|..1.|.X|..Finalize new buzz plan...| 02-Apr|...............|.................|
|..2.|.X|..Finalize control report....| 02-Apr|>SubProj16|.................|
|..3.|.X|..Finalize staff meeting....| 18-Apr|...............|.................|
: : : :
|..N.|.X|..Ffffffgfgfgfgfgfgfgfgfg...| 18-Apr|...............|.................|
|................................................. ..........................................|
-------------------------------------------------------------------

In my view, to have many subprojects does not give effective control, and it interferes with the
achievement of a successful end result.
I f you really need to open a subproject put a mark in transfer field
If you plan to work at a specific context, instead of on a specific project, so add the context field
This it doesnīt work for me. I need to or want to work on a specific project for a period of time
instead of do work based on a context. But it may be useful for you.

My way of reducing the number of next actions is to be pretty rigorous about allowing
one next action per project, and to carefully manage the number of 'live' projects I have.
The way I implement this in practice is to have one 'live' next action and a number of ' next
actions' under the "action plan " category of each of my projects. As soon as I have completed the
live next action, I take a look to my action plan for this project and choose another action to do.

how to decide what n/a's or projects to handle? Ask yourself:
1. What long-term project should I work on today?
2. What projects will have worst impact if not done?

My system:
Everything is tracked in a serie of screens called Command Center on a computer. So , in this
way, in one screen you see the general status of your cases
See an example in
http://voipdar.atspace.us/memberlz11.htm
(excuse my English, it is not my native language)
All projects are tracked in a Data base, it was made with Delphi. But you can do it with any tool.

How I manage deadlines & no deadlines actions?:

I have a special field for each project called - "Deadlines". Every deadline is assigned this
category. I'm also list the deadline in my calendar, with an appropriate reminder.
Use your calendar effectively. If you have real deadlines for steps in your project (or for the
project itself), make sure that it's on your calendar.
Now , when I have a project with no hard deadlines but with actions to be done some day,
this action is assigned to a field called " to do any time"... this category is listed in my main
screen called Command center.
While I'm doing the Weekly Review I'm viewing all projects and NA'S by category. One of the
phases I go through during the WR is examining the deadline category (as well as the "to do
anytime" category). Any deadline that is approaching and not yet completed-is also assigned the
"status" field - "work /urgent" - this is a field that is being looked at couple of times a day. It's just a
way to bring the specific project, be it a deadline or something else, to my awarness, more often.



Hope this provides some useful ideas.