A few days ago, Josh Gruber took a potshot at an admittedly dreadful looking Windows utility, the aptly named “Bulk Rename Utility.” For some reason, something just felt off about the post — yes, it looks like hell at first glance, but it also looks powerful.

Then it hit me; I’d used this app a few years ago (back when I used Windows), and it had saved me the trouble of renaming about 300 JPGs that had the always sexy “DSC_000.JPG” pattern. It took me less than a minute to figure out how to use the program, and to get it to work perfectly.

What is bad?

Shortly after the DF post, the always insightful Chris Fahey took up the task of defending Bulk Rename Utility’s UI on the grounds that it’s 100% transparent — it shows you everything, all on one view. While that is an admirable design goal (the best navigation is the least), I don’t know if that’s enough to justify the dense, cluttered interface. Really, there’s just not much defending the application on its UI aesthetics or organization.

But that’s just the thing — in rare cases, it’s actually better to pose a little bit of difficulty and confusion to the user. Not every task we perform on a computer is an easy one, and therefore not all interfaces must be designed to make things easy. Presenting a complex, slightly non-traditional UI to solve a sticky problem can slow users down, and force them to consider each choice before clicking around.

Apple does it

Consider Time Machine. By many accounts, this is a terrible looking interface — it’s garish, cheeky, somehow reminds me of MS Bob, and looks absolutely nothing like what I’ve come to expect from well-designed OSX applications. But it’s wonderful, and a perfect UI for the task of restoring lost files.

File restoration is a very critical task — if you screw up restoration, you’re most likely screwed. As such, Apple went to great lengths to make you a bit uncomfortable, out of your normal environment, and focused on the task. The Time Machine interface blocks out all other apps, puts you in a fully single window mode of working, and you can only do the task of browsing through old files for restore. It works wonderfully because it’s different, and a bit clumsy. It slows you down so that you can make a considered, correct choice.

But bad is kinda bad too

Of course, you just can’t use this as an excuse for bad design — only in certain contexts (backup, bulk rename, system restore, syncing, etc.) is it useful to slow the user down. And even then, there’s room for good design. Apple’s Time Machine, while not my visual cup of tea, is thoughtful, well presented and considered. Bulk Rename Utility, not so much — there’s room for improvement.

In a follow up post, Gruber unintentionally reveals there’s never a simple recipe for design:

If your UI even vaguely resembles an airplane cockpit, you’re doing it wrong.

Of course, the complex interface of an airplane shouldn’t be anyone’s goal — unless you’re designing controls for an airplane! Context and use-case matter immensely, and must shape the overall design of a product or interface. While file renaming isn’t insanely complicated, it’s also a non-trivial task, and surely not as straightforward as a UI for a word-processor. Different use cases require different, sometimes unaesthetic design solutions.

In the end, Bulk Rename Utility probably won’t win any design awards. It did however, get a great design discussion going.