Getting Things Done for the Holidays

Over the last few weeks I’ve spent a lot of energy getting things done. I mean this in a couple of ways. First, and most plainly, Getting Things Done, by David Allen. Second, there was actual business to attend to and prints to sell. Third, as part of my usual melange of procrastination and creative furnace stoking, I’ve completely rearranged the furniture in my apartment to grant me a small and efficient living space coupled to a large, mostly empty and spare workroom.  I wanted to write about all of this, but then I wrote far too much about the GTD process, and got really intimidated by the prospect of trying to tie all of these things onto one bloated, sagging barge of a post. This is a rare case of resistance coming in line with good sense. Truth is, its the Getting Things Done process thats been most interesting, and after this much of it, you’ll probably want a break. So here we are:

To put the first thing first, Getting Things Done. Its written quite clearly for last-century executives. I am a plainly 21st century, internet-dwelling creative. Still, the central tenets are useful and important. I’d recommend the book to most of the working world. If you have tasks that last longer than 2 minutes, and projects that overlap, get your hands on a copy of Getting Things Done. The first part of the book is about the why and the implications of getting things out of your head and into a reliable system that you will use with unfailing consistency.  If you’re like me, you probably won’t care about suggestions on how to manage paper files within arms reach of your desk, because the daily information deluge is now 95% electronic. Still, having a repository for those digital reference materials, ticklers, and items of personal curiosity is important. Being confident that your inbox will actually get addressed in your routine, and that your file system is capturing things you need later on would put anyone into a far stronger position for active engagement in their work. It was actually listening to David Allen on a podcast and in a TED presentation that I became interested in Getting Things Done. He mentioned the idea of making available your “Psychic Bandwidth.” Its a fancy and flashy phrase, but it spoke to me, because as an artist, I know exactly what that is. Psychic bandwidth is the difference between having a great rehearsal because you are totally, unfailingly present, and trying to get out of your head. In so many pursuits, its never been said better than “there is no try, there is only do or do not.” Getting Things Done is about freeing your mind (not necessarily your time) from all of the things which are not doing your work. For this tiny piece of perspective alone, it is worth the read and a really serious attempt at getting all the open loops of your life into a reliable system of filing, and lists of next actions. 

That all said, I spent the better part of two days and one extra evening collecting all of the projects in my head that were not written down. Even for someone like me, an avid task and project-management app watcher, there was a tall stack of things that needed better organization and a unification of priorities. I took the magazine file boxes that were holding all of my important papers (credit card disclosures, car title, car service history, insurance policy documents, etc.) and put them into a genuine file system. I read through all of the tasks, recurring and single which I had stored in Things. Then I sat down with a stack of index cards and (careful to avoid the rabbit holes) wrote down all of the remaining open loops that I had in my mind, the tasks and projects that had no physical repository… an entire package of index cards later I was able to establish a usefully complete list of open projects, and an appropriate list of next actions. 

Part of the reason for my copious number of open loops was that in the never ending quest for the perfect tool, I turned up lots of applications. Worse yet, lots of them I really like. So, it became difficult to decide where to capture something, and therefore even more difficult to find it when it was needed. I had a journal in Day One, most of my drafting was taking place in iA Writer, unless it needed a basic page layout in which case I was usually drafting directly in Pages, I had notes spread across iOS Notes and Evernote, I was using Things for my projects and recurring to do items, but often using iOS Reminders for basic lists like groceries. Altogether a TON of capture, but only a little search-ability. This left me only moderately effective even when I remembered to stay action oriented in putting tasks down in Things. Finally I didn’t have enough confidence that I would for CERTAIN be able to find the thing I wanted later, so I was getting numb to some of these lists and having to dream up new reminders for really important stuff. 

I’ve had an Evernote account, probably for the 5 years they’ve been around, and frankly I never took it seriously. The problem with any every file system is that until you hit a critical mass for the amount of stuff inside it, it doesn’t work. Organizational systems seem floppy, unnecessary, wishy-washy, meaningless work to feel officious until there’s enough stuff in them that you would be hopeless to find anything without a system in place. This is the real beauty of Evernote, even if you made no notebooks, no tags, you might not even need a good titling convention, even if you put literally no work into organization, you would still probably be able to find what you need. So, naturally I decided to make a ton of notebooks, notebook stacks, and a completely revamped list of tags. I even sprang for a very helpful book, Evernote Essentials by Brett Kelly to help me get a really comprehensive restart. Now I’m completely moved into Evernote for project lists, journaling, personal reference (with Evernote’s Web Clipper browser extension and email upload features, capturing reference material is spectacular) documents like my business registration and expense receipts, contracts, everything can go into Evernote, I’m even drafting this post in Evernote on my mac. That leaves Things, which is for the time being still the best task and project management app out there (if you don’t need team management), to collect all my next actions and even future next-actions using scheduling and multi-step projects features. I have also reworked my Things tags list as well to be more functional (more on this in a minute). Lots of Evernote power users write about doing these kinds of things with Evernote reminders and check-box items, but so far I’m not ready to jump in that deep. 

Having done my capture I needed to ingest and make decisions on next actions. This is one of the timeless (and still revolutionary) parts of GTD. The act of processing the inbox is of central importance. Decisions can never be tasks, sometimes research or questions are required for a final decision on what to do next, but I was often guilty of putting “Decide on,” “Decide how” in my tasks. This is tantamount to placing those items back in my inbox and its a great way to end up with open loops. It doesn’t matter how the information comes to you or how you’re going to store it, this idea of handling an inbox item one time before deciding not just whether or not something needs action, but what action should come next, is the real power of GTD. This makes it possible to gauge when you take out a list, what actions you might actually take in the moment. Now, David Allen suggests lists organized by context, like “at the office,” “at home,” “running errands,” “at the phone,” “at the computer,” etc. Well, today many of these contexts are meaningless, with smartphones and cloud services like Evernote, IMAP email, Office 365 and others, a lot of actions can be taken from anywhere at any time. So we can simplify, and that brings me to my Things tags. Tags are great for context, but beyond the context of in-person meetings and perhaps out on errands, if you don’t do your work on highly specialized machinery context has almost nothing to do with where you are in the physical world. But the really great news is that today ALL of your lists can be in your pocket, and easily temporarily reorganized with tags based upon what you think might be doable at the moment. So all of my tasks now get three tags: estimated duration, difficulty (or required energy level), and high-med-low priority. So if I am at the laundromat with half an hour to kill but I’m tired, I can now view all of the tasks that will take me less than 30 minutes and don’t require a lot of energy. More than likely I will be able to accomplish at least one from my smart phone. Likewise, if I’m bouncing off the walls confined and waiting on the dryer, I can choose something appropriate to that mood as well. 

Another part of this experiment was The 4 Hour Workweek by Tim Ferris. Its not something that I ever felt was going to be really useful, the title is classic get-rich-quick click-bait. As a matter of fact, there is a short section of the book that explains that the title was chosen specifically, and scientifically for its click-baiting potential. Still, Ferris makes a lot of audacious claims and calls out a lot of examples that might open up one’s thinking about how they would really like to live and work. What he tries to offer are strategies to remove as many working hours as possible from earning a useful income. For people who want to travel and experiment and Live first, work second, this stuff is great. I would like to have the latitude to get immersed and lost in the real, important work of my art, but as it stands I have to spend a lot of my time doing someone else’s work in order to survive. This is a fine temporary action, but it is not a good long term strategy, because it means I can only stay half invested in each thing. Those of us working “survival jobs” tend not to advance very far in them, because we do not take complete ownership of them. This is one of the most interesting ideas from The 4 Hour Workweek, that even if you hate your job, you might be best served by putting all of your attention into it for a time. This way you can establish your own systems and efficiencies and become an irreplaceable asset to your organization, then ask not to have to be there, and work remotely for fewer hours than you’ve needed before. Now thats a position from which to launch something new! However, there are some ideas he discusses which are a bit more relatable to GTD. The primary strategies Ferris uses to get more uninterrupted time are outsourcing, auto-responders, and gatekeepers. Outsourcing is obvious, other people attend to things that you don’t absolutely have to do, The auto-responders and gatekeepers are there really just to set expectations for people trying to get in touch with you to deter them from badgering you too much. The idea is that if you can get all of the things people need from you to stack up in your inbox, then you are more in control of prioritization. This is also a great way to get hugely overwhelmed and very far behind. But if its dovetailed into a rock solid GTD system, then you’re in business. There’s a lot to say about The 4 Hour Workweek, but for now I’m going to leave it here.

I’ll probably be following this post up with more about how the 4 hour workweek and GTD fit together. Plus another post about the benefits of giving your brain some breathing room in your physical space. Thanks for reading, go make stuff happen and live a life, useful.  

How To: Multi-size Export from Lightroom

After doing a shoot recently with the creators of Dates Like This, I was able to take my first good swing through Adobe Lightroom 4. The shoot was for some of their promotional material, and I’m pretty happy with the results. Although I did have to wait until after their announcement of the second season on Valentines day (happy birthday to me!) before I could share this work. Which was a new experience for me, as I am more accustomed to not WANTING to talk about stuff I am allowed to say. But that is a post for another time. Today I want to share a little bit of my experience in Lightroom 4.

I have been an avid user of Apple’s Aperture for some time. And the experience has been quite enjoyable for all of Aperture’s strengths as an all-in-one solution for asset management, RAW image processing, and basic photo editing. At least at the enthusiast level, Aperture is great. But if you have aspirations that involve more in depth editing or compositing then you will need a sophisticated pixel editor like Photoshop. And if you need to first batch process files and then interface with Photoshop, there is no better place to be than Lightroom.

Lightroom’s interface is a bit friendlier than most of Adobe’s CS products, and its handling of batch processing is very clever. I had played around in Lightroom before, but I took this opportunity to jump in with both feet and run my entire workflow for this project through Lightroom. And everything was great. Until I had to export… First of all I find Adobe’s preset editor to be wildly unintuitive. Secondly I was putting out images for use on the web, in slideshow videos, for a favicon, as banner images, in blog posts, possibly in print, you name it, and yet Lightroom was content to output only one size at a time (though I’m glad to put Aperture’s crapshoot of a watermarking tool behind me). So here I was navigating through export dialogue after export dialogue to get the numerous sizes I needed. 

Then I stumbled upon a post from one photography blogger at He highlights this very problem and proposes a solution via the wee export setting called Post-Processing where Lightroom allows you hand off the exported files directly to another application. This post goes on to offer a bit of Applescript code (provided by John Day of that one might use to create an application which resizes and renames image files as they are exported from Lightroom. I promptly leaped for joy, created a new Applescript Editor document and landed flat on my butt. I couldn’t get this darn script to work for me. So it was clear there was an easier way to do this.

Automator to the rescue! If you work on a Mac and you deal with files in large quantities, you NEED to explore Automator. It will save you hours of your workday, help you sleep at night, make you taller, better looking, reduce your stress, make you less forgetful, make you seem really smart, and regrow your thinning hair. And since this is something I am under no direction to keep quiet, I’m gonna share with you this Automator App I built to augment Lightroom’s export dialogue. 

First Things First:

This is the primary sequence of actions I’ve used to create new versions of the images that are coming out of Lightroom. 

  1. First of all the items get duplicated (in step 1), when OS X duplicates these items in the same folder it will automatically append “copy” to the file name, making it read “imagname copy” so that has to be corrected. 
  2. You’ll notice that the first thing I do to correct this is to add my own descriptor to the filename in step 2, in this case “2k” for the 2000px version (you may wish to choose a different descriptor or different sizes, but this made sense to me). Now the filename will look like “2kimagename copy”
  3. We add the new descriptor first because OSX will not allow the appended ” copy” to be removed while the new file remains in the same folder without replacing the old file of the same name, or adding an additional index number to the end of the file name. So, now that the file has a unique name we can remove the ” copy” from the file name in step 3. You can see that there is no “remove text” action so instead I have used Replace, and dictated that we replace with a blank field, this action behaves just like Find and Replace in a word processing application. Resulting in a nice, clean, meaningful and unconfused name “2kimagename”
  4. Having now prepared the filename we move on to the purpose of all this, creating a version of this image in a smaller size. In step 4 I’ve used the Scale Images action and chose to scale to the specified size of 2000px. This will make the image fit within 2000px x 2000px or 2000 on the longest side.  You might be done here, if you only need one more image size after your export, but we can go further:
  5. At this point, we’ve created a second copy of the file coming out of lightroom that has been resized to 2000px and been named to make clear its differentiation from the original, fullsize version. But we might want another additional size, so step 5 duplicates the file or files that resulted from steps 1-4. And we will move through basically the same process once more.

Now we will go through the next rename, resize process.

First Steps in Automator
First Steps in Automator

Next Steps:

Here, we receive the duplications from the end of the first set of instructions. Their filenames will look like “2kimagename copy” so we need to fix this to be meaningful for the next size we create and then clean it up by removing the ” copy” addendum. 

  1. Note that the first step here after the duplication is Replace Text not Add Text as it was in the first process. This is because the automator script will move in a liear fashion when it comes to the handling of files. In other words we are picking up here, right where we left off in the first section, and not moving back to the orginal files that were passed in from Lightroom (its possible to do this with an applescript injection, but more on this later). Now after this find and replace our filename stands as “1kimagename copy” and its time to clean it up.
  2. Again we Replace Text, finding ” copy” and replacing with a blank field. Leaves the filename as “1kimagename” which is exactly where we want it, but the file is still 2000px on its longest side.
  3. Step 3 takes this currently mis-named 2000px image and scales it to 1000px in the same way we did the resize earlier. Note that the Scale Images action will scale up as well as down. I mentioned 2 steps ago that  with an Applescript injection you could revert to the original file for each resize/rename process. While this would protect you from degrading image quality through multiple resizings, it is not neccessary to our puroses here. As long as you keep your steps moving toward smaller and smaller pixel counts you will not see a degredation of the image.

This script ends here at 1000px, but you could keep repeating this duplicate-rename-scale process for ever smaller versions according to your needs.

Here's where Automator really starts making your life a lot better.
Here’s where Automator really starts making your life a lot better.

Make your Application:

When you’re finished creating your script make sure that you choose the file format “Application” so that it will be usable from Lightroom’s export preset under Post-processing.

Automator save dialogue making you look smart.
Automator save dialogue making you look smart.

Set up Lightroom Export:

Here, you can select the desired application wich you created in Automator to handle your Lightroom output. And once you’ve created an export preset which leverages this, it will effectively give you an export of one or many images simultaneously to multiple image sizes. You may notice that I’ve got this preset outputting first fullsize versions of the images and then my Automator App will take care of the multiple resizing.

Enjoy the fruits of your labor.
Enjoy the fruits of your labor.

So, this post was a little unusual for me but I ran across this and knew there are lots of folks out there who need this functionality and may be having trouble doing it. I hope its of use to you. After all I wouldn’t want to be all philosophy and no tangibles. Please comment here if you have questions or suggestions.