To be a Project, or not to be a Project.

I’ve been struggling with trying to implement GTD for the last year or so. I’ve read the book twice and listen to the abridged tapes twice. I’m not sure what the problem is but I’m glad that I found this forum and hopefully I can learn something here to help out.

One of the problems that I struggle with is “What is a project?” It seems that the answer is that a project is anything that has more than one “next-action”. Would you agree with that?

I have a Project called “Home”. What I do then is put all my to-do’s that I want to get done around the house there. But this is frustrating because this “Project” is never going to be complete! There is always going to be things to do around the house. Thus, this doesn’t seem to fall into the category of a Project. What do people think?

On a related issue, if we say there is no Project called “Home”, then what projects do next actions go into, if they are a single next action? Let’s say I have a next action that I put in the @home context that is “wash load of whites”. If there is no Home project, where would this go?

Thad
 
Be careful not to confuse a "project" with a "context."

A context is basically a set of resources needed to complete those actions. @Phone is a list of phone calls. @Errands or @Home Depot is a list of general errands or things to buy at Home Depot, respectively. So @Home is anything that can only be done at home: Run a load of laundry, change the litter box, mow the lawn, etc.

Most of these examples are single next actions, not projects. That's fine. While every next action should have a context, there's no requirement that an action be associated with a project. (Some software tools may impose such a requirement. That's a tool limitation and not part of GTD. You may need to create a placeholder project in that case.)

A project is any defined outcome requiring more than one action. For example, if you don't actually own a lawnmower, "mow the lawn" might become a project:
@Library: read Consumer Reports on lawnmowers
@Fred: arrange to borrow truck to pick up mower
@Home Depot: buy lawnmower, gasoline can
@Chevron: fill gasoline can
@Home: assemble mower, mow lawn

Hope this helps,

Katherine
 
re: What is a Project?

Yes. A project is, roughly, anything that requires more than one step to complete. Of course, if you take it to its logical extreme, making a peanut butter sandwich is a project: (1) Open refrigerator, (2) get jar, (3) get two slices of bread, etc. You don't need to even put this project on your lists since it is easy to both remember and do. What goes on your Projects list, then, are more-than-one-step actions that require further clarification and whittling down to the very next action. You can put more-than-one-step things on your action list if they don't require too much thinking (e.g. get a haircut). It's fairly easy to move through the steps as needed - look up number, call for appointment, etc. Bottom-line, then, is more-than-one-step outcomes that require more thinking, clarifying, and organizing, go on your Projects list.

With respect to your "Home" project -- this is not really a project as much as it is a location. A project would be "Get a new washer and dryer". The next actions would be "@ Online: look at a selection of options", "@ Online: Decide which washer and dryer to buy", "@ Appliance Store: Buy new washer & dryer", "@ Home: Do the laundry", etc. You would put each one onto your Action List as you complete the earlier task.

Hope that helps.
 
Thad;63467 said:
What do people think?

I call those things projects. Lots of projects never get done or are repeating. I have some that repeat every month and some yearly. They are still projects.

Put it in a place or call it whatever makes you comfortable.

I have a top level area of focus to keep a comfortable house and all that sort of stuff goes there.
 
Thad;63467 said:
One of the problems that I struggle with is “What is a project?” It seems that the answer is that a project is anything that has more than one “next-action”. Would you agree with that?

More accurately, a project is an actionable that has more than one next action. Even better, a project is a definite outcome, or something about which you can ask "is it done?" meaningfully (and it is not going to be complete in one action).

I have a Project called “Home”. What I do then is put all my to-do’s that I want to get done around the house there. But this is frustrating because this “Project” is never going to be complete! There is always going to be things to do around the house. Thus, this doesn’t seem to fall into the category of a Project. What do people think?

The way you have put it, it is a context and not a project, as pointed out by Katherine. An example of a home related small project would be 'fix the dripping tap in the kitchen' or 'buy a bigger refrigerator'.

On a related issue, if we say there is no Project called “Home”, then what projects do next actions go into, if they are a single next action? Let’s say I have a next action that I put in the @home context that is “wash load of whites”. If there is no Home project, where would this go?

Not every action needs to go under a project. This action just belongs to the next actions list at home context. An outcome that is not achieved in the first action needs to be a project, simply to remind you that it is not yet complete.

Regards,
Abhay
 
What is a project?

Thad said:
One of the problems that I struggle with is “What is a project?” It seems that the answer is that a project is anything that has more than one “next-action”. Would you agree with that?

NO!

Project must:
a) have a defined outcome;
b) consist of more than one action.

In "Making It All Work" David Allen defines projects as outcomes that can be finished within a year that involve more than one action.

Thad said:
I have a Project called “Home”. What I do then is put all my to-do’s that I want to get done around the house there. But this is frustrating because this “Project” is never going to be complete!

What is the "Home"'s outcome?

Will you finish "Home" within a year?
 
TesTeq;63483 said:
Project must:
a) have a defined outcome;
b) consist of more than one action.

In "Making It All Work" David Allen defines projects as outcomes that can be finished within a year that involve more than one action.

I have a real problem with the 1 year timeframe. Projects with defined outcomes and consisting of more than one action can often take much longer than a year to complete. Some individual next actions (concrete definable physical actions) can take more than a year of elapsed time to finish!

As to when a project like "keep a comfortable home" is "done" For me home being done means I can invite friends over for dinner without any notice and not worry about how the house looks. :-) Even vague projects can have a criteria for the desired outcome even though they will constantly need work/actions to keep in that state.

That's where I include Flylady's routines in with GTD myself but the goal is the same.
 
Thad;63467 said:
One of the problems that I struggle with is “What is a project?” It seems that the answer is that a project is anything that has more than one “next-action”. Would you agree with that?

Yes, I would agree with that, but keep in mind that there other levels of work beyond what one would call a 10,000 ft project. Whether or not you call something a project or a goal depends on how you chunk it. One might call "Organize home" a project, but in my case that's simply too big to manage as a project. I would create a project for each room or space I want to organize (but not activate all of them at the same time--only one or two), and label "Organize home" as a 30,000 ft goal related to a 20,000 ft area of focus and responsibility--my home.

Thad;63467 said:
I have a Project called “Home”. What I do then is put all my to-do’s that I want to get done around the house there. But this is frustrating because this “Project” is never going to be complete!

EXACTLY! There are some things that you are NEVER done with. You're never done taking care of a house, your body, your mind. You NEVER finished moving in (at least, according to David Allen--he said this in the seminar I watched). Don't try to manage these things as projects--give yourself a game you can win.

"Home" is not something that can be checked off as a completed project. Other than a context (a specific place where you perform next actions), your home is a 20,000 ft area of focus. At any time you'll have multiple projects related to your home (organizing a room, fixing a leaky toilet, painting a bedroom, etc).

Keeping a home neat and clean is a challenge, and I find that I don't usually put regular or recurring cleaning tasks on my @Home list. I have a checklist to follow regarding cleaning, but usually things get cleaned or added to the @Home list when the scuz factor reaches a certain level.

Best of luck!
 
Oogiem;63498 said:
I have a real problem with the 1 year timeframe. Projects with defined outcomes and consisting of more than one action can often take much longer than a year to complete. Some individual next actions (concrete definable physical actions) can take more than a year of elapsed time to finish!

As to when a project like "keep a comfortable home" is "done" For me home being done means I can invite friends over for dinner without any notice and not worry about how the house looks. :-) Even vague projects can have a criteria for the desired outcome even though they will constantly need work/actions to keep in that state.

That's where I include Flylady's routines in with GTD myself but the goal is the same.

I do the Flylady routines as well. But no routine home cleaning activities ever make it to my project list and USUALLY don't make it to my tasks lists either. This is ideal use of a checklist and, in FlyLady speak, that's pretty much what she's espousing by using her "Control Journal".
 
I'm going to agree here.

"Home" is really a too broad concept to set as a project. As a location or context @home is fine, but as a project it is not finite. You need to have a successful outcome. There is no successful outcome, because it is an eternal situation.

You can put the concept "home" into a higher level, such as a goal "maintain a comfortable, clean home" or as a role "family leader" or "family person". From both a goal and a role, many projects can follow. One example: "clean & prep home for superbowl party." That's finite and you definitely have an outcome.

I also don't have a project list for regular home cleaning tasks I perform. I will, however, open projects for something more specific, such as "reorganize bookshelf" or "sort, archive, or trash boxes in garage."

Separately one can have non-project single next actions. I have about 10 right now. One of these is a task I noticed just now "dust ceiling fan in den."
 
Barb;63502 said:
I do the Flylady routines as well. ... This is ideal use of a checklist and, in FlyLady speak, that's pretty much what she's espousing by using her "Control Journal".

Well the task that makes it to my Next Actions list daily is "Spend 15 minutes on Control Journal Cleaning" :-)

My CJ is a notebook with pages in page protectors and little checkboxes I can cross off with a dry erase marker so I see what's not yet done for the week or month. So far most of them are getting done at least every other month doing it this way. Still working on a few tasks like that I hate to do.
 
Daily Checklist

Oogiem;63512 said:
Well the task that makes it to my Next Actions list daily is "Spend 15 minutes on Control Journal Cleaning" :-)

My CJ is a notebook with pages in page protectors and little checkboxes I can cross off with a dry erase marker so I see what's not yet done for the week or month. So far most of them are getting done at least every other month doing it this way. Still working on a few tasks like that I hate to do.

I actually have a "Daily Checklist". It reminds me to take my medications, drink enough water, exercise, CLEAN A LITTLE, check to see if I need to thaw out anything for the next days' dinner, charge my cell phone, etc. This is the only checklist I have on an Excel spreadsheet, just so I can check off things as I go. At the top of my calendar for each day, I have a recurring entry that simply says "Daily Checklist". This has been working very well for me, and keeps my contexts lists clean.
 
Can you give me an example, please?

Oogiem;63498 said:
Some individual next actions (concrete definable physical actions) can take more than a year of elapsed time to finish!

Can you give me an example, please?
 
Thad;63467 said:
One of the problems that I struggle with is “What is a project?” It seems that the answer is that a project is anything that has more than one “next-action”. Would you agree with that?

I have a Project called “Home”. What I do then is put all my to-do’s that I want to get done around the house there. But this is frustrating because this “Project” is never going to be complete! There is always going to be things to do around the house. Thus, this doesn’t seem to fall into the category of a Project. What do people think?

On a related issue, if we say there is no Project called “Home”, then what projects do next actions go into, if they are a single next action? Let’s say I have a next action that I put in the @home context that is “wash load of whites”. If there is no Home project, where would this go?

I think a lot of the answers to your questions depend on the system you are using: i.e. paper vs. computer (and the software you use).

As others have pointed out "home" is a context not a project.

In my system "wash load of whites" would be a recurring item that is part of a project called "keep laundry under control", and would take place in the @home context.

The "keep laundry under control" project would sit in a folder called "home", in the software I use (omnifocus) but note that this is not the same as the context. The folder could easily be called something else like "keep home running smoothly".

- Don
 
TesTeq;63524 said:
Can you give me an example, please?

Spinning enough 40 WPI Z spun singles for weaving 15 yards of 60 inch wide 2/1 twill fabric to be woven at 21 EPI and 20 PPI. I need approximately 75,000 yards of the singles to do the job. Since I have other jobs to do and am not a spinster that alone may take several years to complete. Even if I was a full time production spinner that is a job that would take between 3-5 months of full time work.

That is a single concrete definable action with a clear ending but it will take a long time to get there.

I have a lot of projects where the next actions are of that type.
 
Thanks to all!

There's been some really good information in this thread, it's really helped out. Thanks to all who replied :D

Thad
 
Oogiem;63560 said:
Spinning enough 40 WPI Z spun singles for weaving 15 yards of 60 inch wide 2/1 twill fabric to be woven at 21 EPI and 20 PPI. I need approximately 75,000 yards of the singles to do the job.

Looks like you have several hundred thousand Next Actions there. I think the Next Action would be "Spin one 40 WPI Z spun single." Or am I missing something?
 
Brent;63622 said:
Looks like you have several hundred thousand Next Actions there. I think the Next Action would be "Spin one 40 WPI Z spun single." Or am I missing something?

giggling, yeah I think you're missing something. You spin a continuous thread until you fill one bobbin. I am not even sure how many yards my spinning wheel bobbins will hold at that grist so I have no way to say how many bobbins it is. But even one bobbin full will be more than I can spin in a single day if I spun all day. There is no way to break it down to a smaller physical action ergo that is the next action. The only physical action left to do is spinning the thread/yarn to the specifications listed. But the physical time it will take is months. You can start and stop but the action doesn't change.

40 WPI describes the number of wraps per inch and is a description of the fineness of the thread you spin. EPI is ends per inch and defines the warps in the fabric, PPI is picks per inch and defines the number of wefts in the fabric. All are describing the details of what you have to spin for the purpose you define. The decisions made about those details are what make this a next action not a project. It's the drilling down to the actual physical action that got me there.

Saying spin yarn is insufficient data to actually do it. What type of yarn (wool singles with what twist), what grist (the WPI), what's the purpose (weaving yarns need different handling compared to knitting yarns and the type and sett of the weave also affects how you spin the yarn), how much (yardage required for the project you envision), how will you know when you are done (enough yarn that meets the specifications), all the standard processing questions have to be answered first to get it to a next action. Before it was an amorphous project with not enough information to do the job. But now it is a real next action, you can't break it down further. But it still will take months of effort to do and in my case, since I cannot work on it to the exclusion of all else I do, we're talking years.

Just like my weaving action, start to finish was just over 6 years. The next action was weave the fabric. At my fastest I could weave about 3 inches an hour. I needed 20 yards of fabric, the weaving part took about 300 hours spread out over the course of 6 years.

Nothing I've seen in GTD really deals with how to manage and handle next actions that are so long. Or projects that are so long. So I just keep the next action on my lists constantly.
 
Just to add my own thoughts to this thread, I categorize projects in a few different ways. For business purposes I categorize them as Client or Internal.

With regard to time I categorize them as a normal project with a start/end or "ongoing". I see nothing wrong whatsoever with categorizing a project as ongoing (I don't view GTD as a religion I use it in a way that makes sense for me). It's true as one poster pointed out that an ongoing project can often be the same as "context" but for me it works because I think in a very "project centric" way and I like to think of/enter everything as being part of a project. It's also much easier to do in this way with a lot of software, if your software supports projects but not contexts. At most times I have about 25 projects going, most with start/end and and some ongoing. One of my ongoings is called "Miscellaneous Tasks". Anything that does not fit into one of my other projects gets put there.

An example of one of my ongoing projects is "IT Work". I have that project because a significant amount of my time is taken up by IT work and creating a single place to track it all is quite convenient for me. However, and this is key for me - I use that to track ongoing "basic" IT work that would never be more than one or two actions. For instance, "set up Outlook on new computer". The moment something is "complex" and deserving of its own project it is going to get one. For instance, "implementing new CRM system" would never get placed into the ongoing "IT Work" project, it would be its own project.

Another example of an ongoing personal project might be "physical conditioning". If physical condition is a major part of your life and does not have a start and an enn date, why not make it an ongoing project IF that works for you? YMMV

p.s. I'd think if you end up with too many ongoing projects that's a bad sign and it's not going to work for you. I have 7. I would think if you had too many it would be like always having a full inbox and be overwhelming.
 
Oogiem;63637 said:
giggling, yeah I think you're missing something. You spin a continuous thread until you fill one bobbin. I am not even sure how many yards my spinning wheel bobbins will hold at that grist so I have no way to say how many bobbins it is. But even one bobbin full will be more than I can spin in a single day if I spun all day.

Then the Next Action could be "Spin thread for a while," couldn't it?

Nothing I've seen in GTD really deals with how to manage and handle next actions that are so long. Or projects that are so long. So I just keep the next action on my lists constantly.

How is this not dealing with long next actions? They're being tracked, and you're doing them, correct?
 
Top