Taking it seriously with GTD projects isn't always easy. While you'll be able to grasp the concept of projects in GTD fairly quickly, you'll have a number of challenges to adopt your way of working. By definition, everything that takes more than two steps and has your attention qualifies as a project. The majority of these projects, say those with four to five action steps, are fairly straight-forward and don not require a lot of brainstorming and planning, i.e. getting tires changed on your car. But then again you have these really large projects that first need some cutting (creating smaller sub-projects) and more serious planning and organisation.
For those projects I, for a long time, struggled to get myself sorted. Of course I use a task list manager and of course I store project support materials in a separate folder. But this alone did not help me to see things through and so I came up with the idea of a Project Charter and a simple way to link all things together.
Creating a project charter
My project charter is nothing more than a simple OmniOutliner Pro template that structures the information and holds some simple check-lists for myself (which I delete once the charter is done).

So here is what the Project Charter contains:
- The three natural planning steps: (a) Why am I doing this and what are the guiding principles, (b) What is the desired outcome and (c) what are (brainstorming) roughly the things that need to get done
- Links to project resources: Link to the Project Folder in Finder where I keep all the stuff that belongs to the project and links to any other relevant resources like online work spaces or web pages
- Project Team (Core/Extended): Links to the Address Book cards of all project members, so I can easily look up their details and call
- Key customer stakeholders: People involved from the customer organisation
As you can see not an awful lot of information, but that is by design. I wanted to keep the barrier as low as possible so that I actually create a project charter for every major project. Again, you may not want to do this for every single project, specifically not for those that you feel comfortable and in control with, but the bigger once deserve this level of attention, planning and organisation.
Of course you can use other tools such as Word, Pages, Ponies Notebook, ... to do the same thing. OmniOutliner just happens to be my tool of choice and so is The Hit List (THL) from Potion Factory when it comes to task management. What I like about both is the linking capabilities. Again, OmniFocus or Things provide similar functionality, so you should be okay adopting this in your environment.
Linking with your Task Manager
Most important to me is that I have things available in the right context and without any effort to find or open. So I tend to interlink things where ever possible. The project charter and the project folder get inserted into THL as simple tasks (unfortunately the only way you can currently do this in THL) that always stay on top of the project task list.

As you can see the alias links get inserted as small icons into the notes section of these two tasks. Not assigning any context like "@email" to those tasks makes sure that they do not show up in any of my context task lists where I usually perform my actions. But whenever I need to access this information, I can quickly change to the project list from the context task list by using "Show in List" from THL's context (right-click) task menu.
Download the Project Charter Template
Download the OmniOutliner 3 template or the OPML version if you use another outlining tool. To use it as an template in OmniOutliner Pro open the file and "File > Save As" OmniOutliner Template in your template directory. You should then be able to create new Project Charters from this template by "File > New from Template > Project Charter".
The simplicity of this approach works perfectly to me and I am curious if anyone of you came up with different solutions for the issue of "keeping it all together".
Comments [0]