I agree planning hour by hour would be unrealistic for many people. I don't schedule NAs, but I do have a list for each day. After a couple of years of GTD, I finally worked out that for me the key elements are:
- Ubiquitous capture, funnelling into a single location (file, pages or whatever)
- Decision on what projects and NAs are current i.e. this week.
- [Not strictly GTD] Decision on when this week each current NA will be done
The captured "stuff" is like a soup in which projects and NAs accumulate. The soup has essentially two layers: Current and Not Current, and I decide where the boundary is. Current items by definition get an allocated day. So the day list is generated as follows:
1. All projects and NAs are in a single big outline. This includes an Inbox section where I initially note anything that does not have an obvious place in the outline. There may be project support materials elsewhere ie not in the outline, but the outline aims to include the universe of what has to be done - whenever that may be.
2. Weekly review includes the usual things, including:
a. weeding and tidying up the outline
b. deciding what is going to be Urgent (asap), Current (this week), Soon (30 days), Someday or Maybe and marking them accordingly
c. copying current NAs to suitable days, mainly in the following week
3. Each day now has a list of Today tasks which are not time-bound. (In addition it may already have a separate hard landscape of meetings etc). The Today tasks are grouped into contexts (very few: Office, Home and Shops). So for example if I am going shopping on Thursday I will put all shopping or errand-type tasks there.
This method has a number of advantages:
- I am obliged to decide what is current and what is someday/maybe, since if an NA is current it is by definition added to a specified day list.
- Projects are bound to advance (or at least be planned to advance), as I am not waiting for a priority algorithm to push any particular NA to the top of my priority list. Being current and therefore planned for a particular day is good enough.
- Similarly, tasks that are chronically being postponed become apparent soon, and can be investigated. (Am I not making the phone call on the defined date and so continually postponing it for a good reason, or simply because I am not looking forward to it?).
- Context need not be formally specified until a day is allocated. For example, I could decide to make all those phone calls together on a particular day when I suspect there will be time for them.
- Ticklers are easily included e.g. phone calls to be made on or after a specified date.
- If all the day's tasks are done, I can consider doing some of tomorrow's, context permitting.
- if I am repeatedly not getting all the day's tasks done, I know something is wrong. Maybe I have declared too many current NAs. Maybe I have too much "stuff" altogether and must drop some projects or move them to Maybe.
Only two documents are required: an outline and a daily list. The outline could be a paper outline or mind map, the daily list could be a paper diary. I use a Palm with Bonsai and Daynotez and native Calendar. Data capture is often on the Palm and the review is on the PC.
Tarentola
P.S. See Mark Forster's
site and excellent book
Do It Tomorrow for more on using daily "Closed Lists".