While coaching my wife in David Allen's Getting Things Done (her request - I swear!), I was asked what project naming convention to use, and I decided I hadn't given this enough thought. My first response was "start with a verb," but I realized I was thinking more of actions, rather than projects. I'm pretty clear that actions should start with a verb, but projects?
First, regarding actions, starting them all with verbs makes sense: Next actions should be named to reflect doing (as he says, projects can't be done, only actions), and verbs (for me, at least) provide a subtle psychological pressure to take action. Put another way, they're commands from my planning self (the part that makes decisions up-front) to my acting self (the part that needs concrete direction, and is easily side-tracked with things that are too big or too vague).
So how about naming projects? Given Allen's perspective on clarifying outcomes, we'd expect him to phrase them in terms of the desired outcome. Interestingly, in the section of the book where he provides a partial projects list (page 37), out of a few dozen examples, only three do not start with verbs ("August vacation", "Staff off-site retreat", and "R&D joint-venture video project"). Here are a few other perspectives:
- From the Belly of the Beasts: Getting Things Done: the Roadmap: Projects should be written in the form of completed goals. E.g., it's not "make a plan for", it's "implement".
- Status report on implementing the 'Getting things done' process: Project Outcome: As Allen suggests, I'm using active verbs and outcomes as the Project Names, e.g. 'Write & Publish Novel'.
- Issues with defining projects - top end: Frank Buck says: I phrase the project as a statement of what the project will look like when it's completed. I find it helps me see more clearly when a project is "done" and there is still work to do.
- Breaking it down: If you’re looking at your list and all you see is nouns, you probably have projects. Actions use verbs.
While I like the idea of a project name reflecting the desired outcome (it goes back to one of Allen's two big questions [1]), I have an issue with verbs in project names: I like the names in my project list to match their corresponding project folder labels as closely as possible, for easiest retrieval. Putting "I know how to speak conversational Spanish" is a great affirmation, but would make a lousy label. I'd probably use something like (brace yourself) "Spanish project" or "Spanish class."
I'd love her your thoughts - How do you name projects?
Update: I should have include a post to this nice piece by David Allen on projects: Defining “Projects” – a Key to GTD. It used to be a tip, but it's gone. However, Jason posted a copy of it on the thread How do you manage Projects?.
[1] I talk a little about them in Some David Allen "twos" - two reasons we procrastinate, and two kinds of problems.
Comments
Hey Brock. Very interesting
Hey Brock. Very interesting questions, which I can tell would lead to a nice insight about GTD and wikis. As you point out, capture (of projects, in your case) *has* to be almost effortless, or it just won't happen (similar to ease-of-filing). I'd love to hear what you figure out. Give me a holler if you want to bounce ideas around.
Because my projects /
Because my projects / milestone tracking is done on Wikis (home and lab have separate wikis) all of my project names are wikinames, usually two to three words that make a nice short link and folder name.
Examples:
GtdSeminar
OctWedge
QuickScience
MarriageLegalIssues
PaperTrackingLabels
They're pretty much nouns.
I actually found this post just now because I haven't quite hit the "aha" I need to keep track of projects and next actions. My current way of using wikis results in too much overhead if every single thing that requires more than one physical action has to have its own project page. It's just not worth it. And yet, how does one keep the Next Actions in the system while still identifying which projects they belong to? I need to resolve this before my weekly review today.
I have some ideas, and I seem to be just on the cusp of figuring it out. Hm....
Thanks a bunch for the
Thanks a bunch for the analysis, GTD Wannabe. You've given me more to think about.
On an unrelated note, I'd like to email you, but I can't find an address on your web site. If you're interested, you can send it to me at matthewcornell@gmail.com
As for Areas of
As for Areas of Responsbility, I don't see that the projects I have listed are quite at that level. That said, I do actually have a few projects that do probably fit that criteria. For example, my many hats include: student, researcher (not necessarily the same thing), wannabe XXX-employee (some of my projects are tied to making myself indispensible to certain people), participant in a couple of groups, minute-taker for large project (in addition to researching for it), web mistress for at least three web pages, not including my own. This is all "work" stuff, as opposed to "home" stuff, where other areas of responsibility come into play.
For the most part, I try to keep my projects as real projects, with discernable outcomes. Obviously, something like "getting papers" is a bit open-ended, but when I fill in the outcome, I say something like, "This project will be finished when I am done my PhD and no longer need to search for papers on a particular topic." On the other hand, I have a project called "Grad Resources Web", which is really an area of responsibility. In that project's supporting material I include any interesting emails/links that I want to add to a particular web page. It doesn't always have a next action, but I'm loath to keep moving it into my "Sleeping Projects" category, because I want to keep reminding myself to look at it.
Long-winded answer, but I guess it just boils down to: yes, some of my projects (although different ones than I already gave as examples) are really areas of responsibility.
I appreciate hearing your
I appreciate hearing your examples, gtd wannabe, and I like the two-part scheme; something for me to think about.
I'm curious: Have you found any of the longer term ones that needed to move up Allen's hieararchy into Areas of Resposibility, values, etc?
Finally, I'm a regular reader of your blog - keep up the great stuff!
Interesting topic; haven't
Interesting topic; haven't thought about it much, so was curious as to how I actually name my projects. Turns out that in my list about half use a present particple verb (ing verb) and half are nouns.
For example:
Getting Papers
Reading
Editing the xxx
Helping xxx with xxx
Tweaking
Blogging
and
Cue Cards
Defence
xxx Paper
xxx Symposium
Next Meeting
Furnace
I think the difference between the two might be some implicit assumptions I have about the purpose or duration of the project. For instance, in some of my projects, there is a clear outcome but it is far away, then the project is more of a "doing" project. Other projects are less continuous, or have sharper edges, e.g., getting the furnace fixed is Furnace.
I love it, Chris - to the
I love it, Chris - to the point, with no waste. Plus, easy to label! Thanks.
Short, concise,
Short, concise, scope-centric. If I'm installing a 5TB disk cluster, that project is called: "EMC 5TB Disk Cluster Install." Catchy, non? I think some of the naming stuff can be more loose (or verb-centric) when there are fewer folks in the company. I imagine 37signals and web2.0 folks having funner-er-er names.