I have always liked well-organised project files. You know… labelled spine, cover page with project description and file index, clearly defined sections for meeting minutes, CDs in their sleeves, flipping through it as you would a book … you get the picture.
So when I started researching examples of GTD® implementations in Evernote and did not find one that had similar concept, I knew I’d have to get creative.
In this blog, I describe how I created electronic project files in Evernote using notebooks and tags.
Creating a new project
To create a new project, I simply create a new notebook and give it a project name that clearly describes the project outcome. The project then gets moved to the appropriate notebook stack.
Setting up new projects
I then copy in my Project Information Sheet (PIS) template. I keep this template in my ^Templates notebook with a *Quick Reference tag so I can easily find it. In the new Evernote 5 version, I also keep it in the shortcuts section.
I replace “Project Name” in the note title with the new project, and then complete as much of the template as make sense.
- Outcome = If the project name does not clearly describe the outcome, I use this section to add more description about what done for this project looks like.
- Reference Locations = If I will have more reference locations than this project file, or a file in My Documents folder, I include links here to those reference locations here. I use this for complicated projects with multiple reference locations or systems, or collaboration projects with completely separate collaboration spaces.
- Next Actions = This is not where I track my current next actions. This is simply the location where I brainstorm project plans and list any future actions that someday or maybe will become current next actions. As I complete current next actions, I reference this section to see if I had any thoughts about what needs to be done next.
- History = I use this section to keep track of any relevant project history I want to keep note of. For instance, I might keep a call log for an important series of phone calls.
- Notes = In this section, I simply track any notes related to the project. Given what Evernote functionality allows me to do, I rarely use this section now. Instead I include a note link to separate Evernote note.
Building out the project file
Once the Project Information Sheet (PIS) for my new project has been created, I tag the PIS with my project status indicator (#Project – Active or #Project – S/M) and the Horizons of Focus category (examples: ~Health, ~Work, ~Service).
I can then create next actions and various project documents. Each document type gets tagged with a #GTD Tag > Indicator which tells me what kind of project file document it is. It could be an email thread I want to store in the project file that gets tagged with #Email History. Or perhaps they are meeting notes synched from my Livescribe or scanned in from a notepad I used. Those get tagged with #Meeting Notes.
I use a convention of “<Document Type> | <Document Title> | <Reference Date>” for each document so it is easy for me to locate the relevant documents simply by looking at the titles.
Some of the benefits I have found from using notebooks as project files are:
- Complete History: I am able to maintain a complete history for each project I work on by document type, by date or even by size. And yet, with the one click, I am still able to easily sort by @Context tags to see the relevant next actions for that project.
- Project by Horizon of Focus Category: By searching for my Project Information Sheets (search: [PIS]), I am able to get a complete inventory of all projects, by horizon of focus category. This makes it easy to compare to my 20k – 50k during weekly, monthly, quarterly and annual reviews.
- Link across Projects: By using the PIS, I can link to any other note in my Evernote system, and indeed, to any other location that has a URL, without requiring that external reference to be part of this project.