Learning to be self-aware

Jumping off of a concept from my last post about common sense usability, one of the most important things a good designer (particularly in the usability field) needs to be is self-aware. In general, people are extremely un-self-aware. Concepts of time are often way off (anecdotally, I remember my mother, in 2007, referring to Princess Diana's death as having been "a couple years ago," when in fact it had been ten years), and we tend to conflate memories into events that either didn't happen or occurred in separate times and places.

This is particularly an issue when working on web design. Very few people stop to ask of themselves the kinds of questions that are absolutely vital for good design. Where does my eye go first? This can help you organize the layout via information hierarchy. Am I moving my mouse to follow my eye? This may suggest good places to have hover states. Do I quickly click from page to page until I find what I want or do I scan a page fully before making my first click? This could inform your approach to site navigation. How many seconds does it REALLY take for me before I get annoyed at not finding what I want? This may determine whether a long-loading Flash module or graphics-heavy page is worth the sacrifice in loading time it may cost.

As important as it is to do proper testing and remember that, as the designer, you are rarely the intended audience, and you certainly know far more about the site than the average visitor will, you can still glean a lot of information just by carefully noting your own reactions -- even reactions to sites that have nothing to do with the one you are working on.

This is also helpful for someone who is not in design, but may need to work with a designer on a project. Are you working at a small organization that needs a better website? You'll be better able to get a top-notch end product if you are able to articulate clearly what your needs are, and you'll be better able to stand up for good usability practices if you end up working with a designer who has a great eye but perhaps a poor sense of usability. Think about your own site. Are there places you (or your visitors) frequently go to on your site that are buried? Is valuable home page real estate being devoted to unsupported or barely visited portions of your site? What aspects of your own site or your competitors' sites frustrate you and what do you find pleasing?

Asking these questions and being aware of your emotional state (by which I mean, happy, annoyed, indifferent, etc.) while browsing can help you pinpoint the design aspects that work and those that don't. So next time you find yourself frustrated by a website, stop for a second and think about what exactly is bothering you, and maybe even write it down. Similarly, next time you enter a site and find the information you want right away, think about what they did right -- this is often just as important or more important than finding the negatives, and frequently we don't even notice when something is done right.

But even when trying these exercises, keep in mind that there will undoubtedly be things you are doing that you are not realizing. It may sharpen your instincts, but for any larger scale project, you'll still need to take that critical look and apply it to other users to truly find underlying patterns and problems.

Why isn't usability common sense?

One of the things that has always amazed me is just how many books there are out there about every imaginable web-related topic from programming to strategy to marketing. And of course, there are plenty of books about usability and all its related fields.

Let me emphasize for a moment that I'm talking about BOOKS -- big thick tomes, hundreds (sometimes thousands) of pages long. I can't entirely fathom why they are all necessary. How much can you really say on any of these topics? But, I recognize that there is obviously a market for these books and I'm sure many find them incredibly useful. On that end, I chalk it up to a difference of approach -- most of what I have learned has come from experience and small chunks of learning, but I can certainly appreciate that others learn in a different way.

But the one thing that strikes me is just how much of this knowledge, particularly when it comes to usability, should be common sense but isn't. Certain things require research to determine, and may not be entirely obvious. People scan web pages in an F pattern. The first two words of a list item should carry the informational weight (even if it means poor grammar). Most people find websites via search engines. None of those things are all that surprising, but they're not the kind of things you'd expect the average person to know off-hand.

But what about some of the other, more "obvious" aspects of usability? Tiny fonts are hard to read. Straightforward, descriptive language is easier to understand. Human beings are creatures of habit. All of these things seem like they should be self-evident -- the last of those three is even a common proverb. But take a look online. The web is rampant with sites that use extremely small type, writers bury their content in made-up jargon and unclear, confusing prose, and many designers view it as a personal challenge to always break from traditional designs and interfaces in favor of flashy, unexpected interactions.

If you asked a construction team to build a house, but told them it should have no windows, the door should be a round porthole the size of a hula hoop, and the ceilings should be 4 feet high, you'd be called crazy. But, technically, it would still be a "functional" house, and it would certainly get some attention. A lot of websites seem to fall into this category, often because they are old and poorly made just due to a lack of skill/investment, but some newer websites even fall into this trap, as high-end designers seek to create showy, "interesting" sites that draw in the eye but fail when it comes to actual interaction.

Is it that these common sense ideas aren't common sense after all? Is there an innate drive among designers to always push against commonly-held perceptions? The challenge of anyone with an eye on usability is to recognize that the desire to question the status quo is enormously valuable -- but the ability to look critically at your own "innovative" ideas and recognize when change is a negative is possibly even more beneficial, and is certainly undervalued.

Don't blindly accept "the way things are," but don't abandon common sense in the name of innovative design.