Tuesday 16 December 2008

Do users need to know why design works to get value from it?

Watching these workmen this morning, as I sit here waiting for the bus, it strikes me that users don't need to know why a design works to know how or when to use it

So these guys are working on the road verge, essentially in the bike lane, while traffic whizzes past at morning-rush-hour speed.  To make the situation even more dangerous, they are often crouched down low and are located on the crest of a hill.

As is likely dictated in their OH&S policy, they have the witches hats out - and I'm sure they feel slightly more comfortable as a result. But, I'm thinking "They only have a few out. Wouldn't you want to close that bike lane out sooner, like over the other side of the crest?"

Then it strikes me that the physical shape (not to mention colour) of the witches hat allows it to be seen from behind small crests.  Being a little over a foot high means that it sticks up above the hill and is more visable from a distance on gently undulating road surfaces.

It could have been designed more cheaply like sports field markers, which are little half spheres, but it seems that the conical shape is, so far, winning the "evolutionary" race in this part of some commercial ecosystem.  Incidentally, sports field markets are used on flat surfaces - possibly supporting the hypothesis above.

It is clear that a taller safety marker is safer (in a variety of situations) than a shorter one.

So thinking about all of this, I wonder what the answer would be if  you asked these users (the workmen) why these safety markers are shaped so.  I didn't have the guts to ask before my bus came but I wouldn't mind betting that one answer would be "So that they are easier to pick up and put down".

This brings me to the fundamental point...

 Users don't need to understand every detail of a design rationale to experience its utility or usefulness.

If the first step on the path to designerly enlightenment is realising that you (the designer) are not your user, then maybe the next step is realising that your users are not designers.  Not sure what the final step is but these things usually come in threes.


Unknown said...

Hi Matt,

I have a small point of disagreement here. I think that in this case there are two kinds of users:

- the "end-users" are the motorists: the height and colour of the witches were clearly designed for them.
- the workmen are a second kind of users: the conic shape and light weight were probably designed for easier manipulation and storage.

I still agree with your main point though: users don't always know, and don't need to know, every detail of a solution to enjoy its utility. Now, one question to meditate would be: where is that fine line when it is worth for the users to have that level of consciousness of not?

Matt Morphett said...

Good point Ju. There are two users here and the motorist is just as important, if not more important. I wonder if I fell into that trap of thinking of buyers as users. There is a blurry line in this case.

Anonymous said...

My view is that users shouldn't even need to know that design exists, let alone how it works. When users start questioning the design, or trying to make sense of it, then in my book the design has failed.

To me, design is like the referee on a footie pitch. The best refs are the ones that just let the game flow. None of the players question the rules, nor do the spectators, when a referee has a good game.

You shouldn't see the design, you should just see and feel the experience that the design was intended to portray.

Does that make any sense at all? :)