Unconscious Interface Design

—Thursday, June 22 2006

I’ve seen a lot of applications in the past few months, some have been around for a while and some are new to the scene, but the one thing all these applications have in common is unconscious design decisions.

What is Unconscious Design?

Marco Dorante has a very complete and informative explanation of unconscious design, but I’ll do my best to summarize it here.

Basically, unconscious design is design where there is no “conversation with the situation”. Sometimes we make design decisions based out of habit; we are simply following the norm; or we just never asked ourselves “Why?”. Every design decision we make should involve us having a “conversation with the situation” if we wish to break free of unconscious design.

If we were the set designer for a Broadway play, we would probably scrutinize our decisions with much more precision because we’re working with physical objects. Every prop on the set is there for a reason. If there was a musical chair scene coming up, we’d expect to have chairs lined up in some fashion taking center stage, and possibly a boom box (1980s!) set slightly out of the main focus of the scene.

We know that when an audience expects to see a musical chair performance, the chairs should take center stage, and although music is vital to the scene, we shouldn’t put the guy with the boom box directly up front.

These decisions seem like common sense, so what happens when we apply the “scene in a broadway play” analogy to a weblog system like Wordpress? Can we find some props that shouldn’t be on stage? Or maybe some asset that demands to much attention that shouldn’t?

Unconscious Design in Wordpress

Wordpress is a very popular blogging platform, and for good reason. The setup process is extremely easy, and it’s widely supported and documented among other things. So does the interface design in Wordpress contain unconscious design? Yes, Wordpress is full of unconscious design, and we’ll take a moment to point out a couple of them.

wordpress

The screenshot above is from the Wordpress “manage” page. Your probably pretty familiar with similar screens because you’ll find it in almost every content management application. By looking at this screen, you should be able to spot some occurrences of unconscious design. Do you think that every item shown in this screen was included in the “conversation with the situation?” If each of these items was a physical item we literally had to carry on stage in some way, would we have added them all? Well, lets answer this question by thinking about our audience and having our “conversation with the situation” as we put on our fictitious Broadway play “Wordpress”.

Wordpress on Broadway

We are putting on our highly anticipated Broadway play “Wordpress”. The current scene is one where our actors (users) will be managing their articles. We could conclude that the props we have to choose from come from our database columns, and possibly some props are just standard in other plays similar to ours.

Our props

  • ID
  • When
  • Title
  • Categories
  • Author
  • View Link
  • Edit Link
  • Delete Link

Setting the stage for scene 1

We know that in order to have a successful play we must please at least 80% of our audience. As much as we’d love to please everyone, there will always be a minority of people that are simply never satisfied. In this case, it’s safe to apply the Pareto Principle, better known as the 80/20 rule.

Let’s start by asking ourselves if we need the ID prop in our scene? What purpose will it serve and why is it beneficial? Can we still maintain 80% approval if we didn’t include it?

The ID field has no real benefit to the majority of our audience. It is vitally important to make the scene work, but does it need to be front and center on the stage with the rest of our props? I think not. Considering most people will scan a page from left to right in some fashion, the ID field is given a supreme amount of importance on this page, but serves little or no importance to the majority of our users. I think it’s safe to conclude that we could safely get rid of the ID field in this scene and it would have little to no impact on our audience.

I’ll let you continue this exercise with the rest of the props we’ve defined above because I’m sure you’ve gotten the point of the game. Just to stir up your thoughts, here are a few questions you might include in your conversation:

  • Can we get rid of the “View link” by just linking the title?
  • How important is it to know the categories of every article in this scene? Is it equivalent to knowing the ethnicity of our actors? If we wanted to know such details about an actor(s), surley we wouldn’t want to know this about all of them, and we would further pursue the actors that interested us (e.g. Clicking a link to view more details)
  • If every item on the screen was a 100lb weight, would we have been more aware of the fact that all the weights didn’t need to be put on the stage?

Scene 2: You don’t need teapots to drink tea

If you we’re enjoying a nice cup of tea, would you need to refill your cup every time you took a drink? The answer to this question is pretty obvious, but how does drinking tea have anything to do with interface design? You’d be surprised just how much they have in common. Lets take a look at the next screen shot:

Wordpress

When you log into Wordpress you get this “Latest Activity” box off to the side. We can see that we have our recent comments shown here. This is handy feature, and one that is very important to a weblog because a blog is about communication (regardless of what some think).

The one thing that strikes me as being out of place in this scene is the Edit link. Just like every time we take a drink of tea—we don’t need to fill our glass, every time we receive a comment—we don’t need to edit it.

The ability to edit a comment is an important feature, but is it something we need to do every time we receive one? I’m not convinced myself.

Someone might argue that this could be a pretty handy feature for those days where spam comments are rolling in. My questions to you would be: a) Can you judge every spam comment based on it’s title (as in the screen shot)?, and: b) If you knew a comment was spam based solely on it’s title, wouldn’t a delete link be much more appropriate? Why would you ever want to edit a comment that you knew was spam?

We’re All Guilty

Every designer has probably been guilty of making an unconscious design decision before—myself included. The reason we make mistakes like this is because most of the time we aren’t consciously aware of them. Does this mean we are bad designers? Not really. It just means that as we become more aware of our situation, we will be better equipped to handle them. We have to break out of “the norm” and make sure the props we place in a scene are there for a good reason and are given the correct amount of importance. Because it’s so easy to make these mistakes, we’ll always make them unless we train ourselves to become more aware of what we’re doing.

Just as a fun (or not-so-fun) exercise, go back through some of the interfaces you’ve created, or for extra fun, browse through the interfaces at Opensource CMS and apply these principles. Spot any unconscious design decisions?