Faceman;48781 said:
But since I will be getting the planner, that might be a good collection tool to use while I'm in meetings, take notes in there,
Excellent plan: a good ubiquitous capture tool is worth its weight in platinum.
Faceman;48781 said:
Now I am itching to get a cool pen/pencil/pda stylus tool to further motivate me.
Never underestimate the power of tech toys as motivators.
Over at the 43 Folders board, they have endless discussions about the best pens, PDAs, notebooks, and so on. And when I say 'best', I don't mean that purely in a cold, practical sense: some of these folk wax quite lyrical about their favourite toys. Which makes good practical sense, of course, but it's also fun.
Faceman;48781 said:
I now have the confidence in my list or at least I think I trust my system enough to know where to look for it. This has been a real huge help, and I was surprised I didn't find it sooner. But I am much happier now, and feel a little bit more relaxed now.
This is one of the crucial parts of GTD. Once you begin to trust your system, a lot of that anxiety just melts away.
Faceman;48781 said:
My NA now are to retrain myself to jot everything down on paper and take the time to process the information and place them in their respective contexts and I still need to figure out the whole Project philosophy context thing.
Oook: retraining is not an NA, it's a project. Anything that takes more than one action step is a project. Anything that sounds like a goal is not a project. NAs use action verbs like Read, Type, Buy, Call, etc: really concrete, well-defined verbs that describe something you could be seen to do. Projects may use verbs, but they're rather more vague: things like Organise Meeting, Prepare Document, Design User Interface, etc. They are really goals to accomplish, rather than standalone actions to be done.
For instance, your intention to retrain yourself: is that one action? Can you picture yourself doing a retraining task? Or is it more of a goal that you want to accomplish? That's basically the difference between projects and NAs, and once you fully grasp that difference, it will have a big impact on your GTD implementation, as well as your state of mind.
Note that writing pure NAs is not easy. Most of us still write down things as NAs when they really should be projects. But the better you get at refining your NAs, the better you'll feel.
Also, it helps to separate the Collection phase (jotting things down) from the Processing stage (working out which are projects etc). Just in case no-one's mentioned it yet.