Hi! A really long title so its easier for people to understand what this is about. I did some searching, but to quote U2, I still haven't found what I'm looking for.
I'm finally going to commit to using GTD. I've listened to the audio book a few years ago and made a half hearted attempt at it. I listened to it again last weekend and I think I'm ready. The stumbling block always seemed to be what tool to use and it looks like Nirvana might work.
My question. I'm stuck on projects and next actions. How/when to break them up and organize them. I'll give you one in particular I'm having issues with. Finish laundry room.
I started off with a project "Laundry room is ready to use" and then started putting actions underneath * Install Washer * Install Dryer, etc. I then realized these weren't NAs but really their own projects.
So I created a project "Install Washer". NA is "Drill holes in floor and install pipes" (yes, this simple as all the infrastructure is there, I just need to connect the lines. Another action is "Verify electrical connection". Now those two tasks can run in parallel as they are distinct.
Then I have other projects "install dryer" (actions: staple electrical wire, seal dryer vent, call electrician to hook up dryer) and Tile floor (actions: get estimate, decide to do myself or sub, lay tile) and a few other laundry projects.
Where I get lost is then the project "Laundry Room is ready to use" doesn't have actions underneath but projects. So is "Laundry Room is ready to use" really a project?
The issue is if I only have one level of project>action, how do I define 20 or 30k foot views? (or something I would deem a "goal"). the "goal" is to finish the laundry room composed of multiple projects. And then all of this is for a bigger project "Get the house ready for rent" which includes multiple other projects.
Sorry if I'm not clear, there is a lot in my mind on this and not sure I'm defining it properly. Thank you for any help.
I'm finally going to commit to using GTD. I've listened to the audio book a few years ago and made a half hearted attempt at it. I listened to it again last weekend and I think I'm ready. The stumbling block always seemed to be what tool to use and it looks like Nirvana might work.
My question. I'm stuck on projects and next actions. How/when to break them up and organize them. I'll give you one in particular I'm having issues with. Finish laundry room.
I started off with a project "Laundry room is ready to use" and then started putting actions underneath * Install Washer * Install Dryer, etc. I then realized these weren't NAs but really their own projects.
So I created a project "Install Washer". NA is "Drill holes in floor and install pipes" (yes, this simple as all the infrastructure is there, I just need to connect the lines. Another action is "Verify electrical connection". Now those two tasks can run in parallel as they are distinct.
Then I have other projects "install dryer" (actions: staple electrical wire, seal dryer vent, call electrician to hook up dryer) and Tile floor (actions: get estimate, decide to do myself or sub, lay tile) and a few other laundry projects.
Where I get lost is then the project "Laundry Room is ready to use" doesn't have actions underneath but projects. So is "Laundry Room is ready to use" really a project?
The issue is if I only have one level of project>action, how do I define 20 or 30k foot views? (or something I would deem a "goal"). the "goal" is to finish the laundry room composed of multiple projects. And then all of this is for a bigger project "Get the house ready for rent" which includes multiple other projects.
Sorry if I'm not clear, there is a lot in my mind on this and not sure I'm defining it properly. Thank you for any help.