A few months ago I wrote about how I’m organizing Evernote. Have no fear! I’m still loving my basic set up, but I have made a few additions to keep important information at hand.
I’m not sure which podcast introduced me to Tiago Forte, but in the weeks after learning of him, I spent hours reading into his P.A.R.A. method – a “universal system for organizing digital information.” His idea is simple – The tools you use aren’t important as long as you have a system to organize things. Of course, any mention of systems has my attention.
I won’t get into the nitty-gritty details, but P.A.R.A. stands for Projects, Areas, Resources, and Archives. He has a 4-part series if you’re interested in learning all the details. Unfortunately, the posts are now behind a paywall though, so here’s an interview he did with Evernote that goes over the basics.
I’ve not adopted his system fully, but I did walk away with a few insights.
Take Away 1: Projects vs. Areas of Responsibility
Coming from a GTD mindset, projects and areas of responsibility seem fairly straightforward, but I was surprised to discover I was mixing them up just as Forte mentioned. He describes a project as “a series of tasks linked to a goal with a deadline,” whereas an area of responsibility is “a sphere of activity with a standard to be maintained over time.” Projects can be completed. Areas of responsibility are ongoing.
Forte argues that when you mix the two together, it’s difficult to see everything you’ve committed to, and I couldn’t agree more. Clarifying the commitments required by my ongoing areas of responsibility has given me a better understanding of just how feasible taking on that extra project might be.
Take Away 2: Make Most Used Information the Most Accessible
It’s no surprise that information isn’t equal. Some notes are used more than others. Part of Forte’s P.A.R.A. method includes keeping your notes organized hierarchically so that your most used information is easily accessible. More actionable information flows up to the top Project level, whereas lesser-used information flows down to Archives.
Forte suggests moving everything into Archives to start. As you need to use notes, move them to their appropriate level, and they will gradually end up in their respective areas. I actually tried this, but quickly found his distinctions between Resources, Areas, and Archives too arbitrary for my needs.
Instead, I settled on a simplified system. I created two stacks – one for Current Projects and one for everything else, Reference. Like, Forte suggested, I just moved my existing notebooks into a Reference stack. For any projects that require supporting documentation, I create a notebook under Current Projects. Once completed, their content will be archived to their respective area under Reference.
(Side note: I’ve also made two other changes: Agendas now live in their own notebook for easier access, and I created a separate Reference notebook for book highlights.)
Take Away 3: Review and Improve your Notes as You Use Them
A lot of people seem to treat Evernote as a junk drawer. I’m guilty as well. Forte has a whole system for randomly resurfacing his notes and annotating them. As cool as it is, I simply don’t have time to review and revise notes each day. Moreover, I find his rules for when to highlight versus bold a bit fiddly. Instead, I’m simply trying to make a point to improve my notes each time I use them. As I use a note, I’ll clarify or highlight the portion I used.
With these three takeaways, my notes should become more and more useful over time. I’m sure that the system will evolve, but for now this seems to be a nice blend of simplicity and functionality.