Open ended projects

[apastuszak]

I have a number of open end projects in my life. The prime example would be the fact that I maintain the website fory kids school. I keep this project open at all times, as stuff comes in my inbox, it gets dumped into that project.

Is this the right way to deal with this kind of commitment?

[ellobogrande]

The example you gave isn't a project; it's a 20,000 ft area of focus/responsibility. That stands along side things like your health, finances, family, spiritual practices, career, job responsibilities, etc. These are things that need to be maintained at some level. You do want to track them on a separate list from your projects or in a mind map. They never are marked off as "done" or go away unless your life changes at or above that level.

Projects emerge from these higher areas of focus. For example, you might want to upgrade the web site's appearance or add some new features. That would be a project. Perhaps you need to set up an exercise program to improve your physical health. That's another project (an example of a "process project", in fact).

Does that make sense?

-Luke

[TesTeq]

The example you gave isn't a project; it's a 20,000 ft area of focus/responsibility.

I agree - it is an area of focus/responsibility that you maintain. Project must have measurable, achievable successful outcome.

[Oogiem]

Is this the right way to deal with this kind of commitment?

I'm heretical because I think that projects can be open ended or recurring. Sure they fit into a larger area of focus but they are still projects in that they are multi action steps. Keep website current is a project to me even though action items will come and go depending on what's happening.

If it's working and you aren't bothered by handling it that way leave it alone.
If something is bothering you about that then perhaps you need to change to a more standard definition of project.

[Day Owl]

I have a number of open end projects in my life. The prime example would be the fact that I maintain the website fory kids school. I keep this project open at all times, as stuff comes in my inbox, it gets dumped into that project.

Is this the right way to deal with this kind of commitment?

This sounds to me like a real project. A "successful outcome" doesn't necessarily mean that at some given date you will close everything down and file it away. Your ongoing successful outcome is that you keep the website up to date and include everything in it that belongs there without lagging behind. At any given moment, you will surely know whether the website is in a state of success. There's no need to get hung up or stalled on exact GTD definitions. That is counterproductive. It's the website that's important.

[TesTeq]

Keep website current is a project to me even though action items will come and go depending on what's happening.

This sounds to me like a real project. A "successful outcome" doesn't necessarily mean that at some given date you will close everything down and file it away. Your ongoing successful outcome is that you keep the website up to date and include everything in it that belongs there without lagging behind.

I do not believe in "ongoing successful outcomes" like "keep website current".

What does it mean current? One second delay is OK? Or one minute? Or one hour? Or one day? Or one month? And so on...

There is no such thing as "ongoing successful outcome" since you can never say that the project is done. Project can be in two states only: not done and done.

"Keep website current" is not a project - it is an area of focus/responsibility.

[Jamie Elis]

Right is relative, meaning what works for you. If your way of looking at the website is not getting you the results you want, then you might try to apply the GTD paradigm more stringently. So in GTD thinking you might find that "keeping the website current" has:

recurring tasks: so a project might be "recurring tasks are done on schedule" (and define the tasks and schedule)

one-off tasks are completed as they come up (return call to school principal with date of big finale)

projects: 1. "three student helpers enjoy serving as assistants each term"
2. "we have a method for getting feedback from the content committee that we use when we put up new content and we review it"

Subprojects: "student training module is completed by 11/15/09)"
"student interviews for evaluation of experience are scheduled the last week if each term".

Hope this helps. Depending on how the project fits with your experience and knowledge you may or may not have to break it down carefully and explicitly.

[Layla]

I agree it's probably an area of focus/responsibility.
I can also see how it could also be a 'project' if it's fairly simple and you know all the steps etc (it ends in a year, no? )

It may be subjective - if it feels 'overwhelming' as a project and if you often don't know what to do and where to start, where to find things, how to prioritize etc, it's probably an area of focus with smaller projects.
The distinction between 'project' and AoF (and other horizons) was EXTREMELY helpful to me!!

You probably have routines to eg update software (this could be an ongoing project or 'maintenance' if it's fairly simple) or keep track of things and people's plans or wishes (school calendar, events).

A project under the 'maintain/update website' AoF might be 'move to another platform' or 'add pics from the Science day' (if someone else has taken them and you need to first identify or locate that person - anything more than one step) or 'add teachers' photos' (with possible steps or NAs such as 'get names of all the teachers' or names of any new teachers, 'get pics of all the teachers' - from teachers, school secretary or the photographer/s and maybe a checklist for this if needed - this could actually be a mini project, if you need pics from different people, or arrange for a photographer to visit first) or 'get content for the _specific part/s of the site_' if you are the one who puts it on and other people write it (if there are eg blogs that teachers/school admins update themselves it's easier)...

A maintenance activity could be to evaluate the site each week (maybe as part of weekly review?) and see if anything needs to be done, talk to teachers/people also working on this (usually tech teachers) maybe monthly or weekly.. It's better to perhaps ask people in advance what they would like and clarify expectations than get any 'explosions' later when things weren't done the way they imagined it.. (You could ask teachers, headmaster, parents, kids.. what they'd like to see - depends again how much energy and time you have for this? And how important it is, what has been done already.. If it's new or fairly well set up, loved and appreciated and used with success?)

Also, as stuff comes into your inbox, do you process it first?

[Oogiem]

Project can be in two states only: not done and done.

Not in my world. Projects can have all sort of states, done for this year, done for this season, done for this decade, done for this lifetime and yet almost all of my projects are also never done. Every project I work on will come back eventually in some form. In fact the more important projects will not be done within my lifetime at all, All I am doing is moving them forward a few actions at at time. Individual actions can take several years to finish, they are still single actions and it's still a project just a very very long time frame one.

I have a more traditional project that is keep ABWMSA web site current. I collect actions under that project as they come in (fix address for new BOD member, put sheep for sale ad up for member x, upload newsletter) and so on The project is never done because new actions come in all the time. It's part of my larger area of focus of Sheep Club work under my goal of Manage the Farm Sustainably. I can check it off as "done" each month when I clear all the current actions but it's going to come back again. Sometimes there are additional projects related to the web site but the main one still holds only single actions and is never done.

Another example is Process ABWMSA requests: It's a project that is never done as new requests always come in. Right now I have several register lambs for X requests in there for several people who have sent in lamb reports. Those are single action items under the project of process requests.

[Toby Jarvis]

I came up against this question too, so will pass on how I've approached it.

Strictly speaking this is an Area of Focus, aka a job responsibility. However, I think this could work in your GTD system by identifying "Maintain website" either as an Area of Focus or as a project. As others have said, the solution you choose will be based on your personal preference and perhaps the limitations of the GTD tools you use.

The end goal is that you are reminded of this particular responsibility during each review, which prompts you to ask "is there anything I need to be doing here?". If there is, you then need to have a place in which to capture and organise your next actions.

In my job I also have a responsibility to maintain our website. I use Omnifocus and have a folder called "Website and forum" (other folders include "Admin", "Market analysis", "Strategic planning" etc.). In this folder are kept the various "projects", subprojects and next actions that fall into this category. An example project is called "Newsletter" (which is strictly an Area of Focus), within which there may be either subprojects (e.g. "Publish newsletter" or "Collate articles") and/or single next actions (e.g. "Write trip report for newsletter article").

For me I try not to get too hung up on strict definitions except for next actions. I think the concepts of Area of Focus, project and subproject are dynamic heirarchies whose main roles are to ensure that (1) you are reminded of what you need to review for next actions and (2) you have a logical place to store those next actions.

I hope that makes sense!