RobertAndrews
Registered
Hi, I've just finished reading GTD after a long time of poking around.
Here's something that just occurred to me...
So, a Project is a container for multiple Actions, right?
The core message of the book is loud and clear - shape "stuff"/to-dos into actionable wins.
So, let's say I want to post a letter to my parents. I suppose, until GTD, the task would be "send letter to parents", but that's not quite it anymore - I can see how I could procrastinate over that because it's actually not quite the action. So, let's go...
But - and here's the question - do they really merit a Project?
I'm on board with the idea of some tasks in life clearly requiring multiple actions - containers, Projects.
But is it worth ascribing "Project" status to something so a) mundane and b) few in number? If not, how do you handle related next-actions?
Here's something that just occurred to me...
So, a Project is a container for multiple Actions, right?
The core message of the book is loud and clear - shape "stuff"/to-dos into actionable wins.
So, let's say I want to post a letter to my parents. I suppose, until GTD, the task would be "send letter to parents", but that's not quite it anymore - I can see how I could procrastinate over that because it's actually not quite the action. So, let's go...
- The contents are already in the envelope, which is sealed.
- The address is written on the front.
- Buy stamp for letter.
- Post letter.
But - and here's the question - do they really merit a Project?
I'm on board with the idea of some tasks in life clearly requiring multiple actions - containers, Projects.
But is it worth ascribing "Project" status to something so a) mundane and b) few in number? If not, how do you handle related next-actions?