Workflow and Omnifocus

I have been moved to action by the stuff I have been reading at MacSparky, practically efficient, Macdrifter and Brett Terpstra’s blogs over the past few months. Of this bunch, a couple of them are strong on Omnifocus. David Sparks has been a long time Omnifocus advocat and bon vivant, while Eddie has been a recent convert.

I started with Omnifocus on the Mac in 2009, added the iPhone edition quickly, then completed the trifecta with the iPad version when it was released. In all of that, I often felt Omnifocus was more of a tonic than a tool. So I cruised the forums, finding tools and scripts, downloading everything. What I ended up building was a home handyman’s equivalent of the perfect workshop. All tools and no talent.

Once I purchased Creating Flow with Omnifocus by Kourosh Dini – a must read for any Omnifocus student – I finally realized how to make the base Omnifocus programs, the add-ons, the workflows and the philosophies work for me. (I ended up using a derivative of Dini’s start date based system and the flag based system.) I was already a secular devotee of GTD – relax I am not going there – so I had a pretty structured set of contexts for personal and career life set up. Being an engineering manager, stuff in my life was already one big list of projects. Most engineers understand GTD instinctively.

A Tip

Here’s something that I synthesized from all of the collected wisdom around Omnifocus; once you get projects set up in a way that works for you in Omnifocus, take a look at the file structure on your main work machine. I created a “Projects” folder – it’s essentially my new “Documents” folder. If you establish a file structure in that folder that matches your Omnifocus project folder structure you will have a system that will complement your workflow. It doesn’t take a lot of time, just go to the Nicola Vitacolonna modified scripts in this forum entry and you will be able to build the file structure as you need to (warning: geekiness level is above moderate on this). The scripts also provide a quick link between Omnifocus, Omnioutliner and the file system. Should that kind of functionality be baked into Omnifocus? Maybe, but the power user crowd that use Omnifocus also appreciate that it is highly customizable while not being full of feature bloat.

Leave a Reply