I found myself at the start of my weekly review this morning with a long list of new projects from a meeting that finished late last night. The first task of my weekly review is to proces my inboxes and I normally, using the GTD definitions, Process and Organise as I go.
Today's list was too long for that. It felt like the time spent Processing and Organsing would eat into too much weekly review time. But then, how would I have a complete list of projects for the later steps...?
With this in mind I decided to scan the list for emergencies and put aside time later today to process it.
This all got me thinking. When people "Process" their inboxes for a weekly review to they:
- process = identify next action/file/trash and categorise, or
- process = identify next action/file/trash
Most of the time I tend to both process/organise, process/organise, ... each item as it comes out of the tray.
I'm interested in what you all think?
David
Today's list was too long for that. It felt like the time spent Processing and Organsing would eat into too much weekly review time. But then, how would I have a complete list of projects for the later steps...?
With this in mind I decided to scan the list for emergencies and put aside time later today to process it.
This all got me thinking. When people "Process" their inboxes for a weekly review to they:
- process = identify next action/file/trash and categorise, or
- process = identify next action/file/trash
Most of the time I tend to both process/organise, process/organise, ... each item as it comes out of the tray.
I'm interested in what you all think?
David