Response to 10 Most Common Misconceptions About User Experience Design

Christine Benson

The other day I posted Whitney Hess' article 10 Most Common Misconceptions About User Experience Design on Twitter, along with "'User experience is not user interface design' and other good tidbits." And then I re-read the article ... more than once. My response ended up being much longer than 140 characters.

Here's what I liked:

1. User experience is not user interface design. 

It's super important to go beyond how a site works. Too many companies jump ahead to 'So, what will that look like?' before they even figure out the why and how. They create meaningless goals like "build the brand" or "make it engaging" and people are too scared to say that doesn't mean anything. While I have some varying opinions on user research, here's an example of creating a good interface that solved the wrong problem.

2. User experience is not just about the user. 

When I heard Tamara Adlin speak a couple of years ago, she said "Without the business, there is no user." As we are likely to witness with many 2.0 companies, if you don't find a way to be profitable, your user experience won't matter much.

I think it's all too tempting to assume the "only I care for the user" mantle and take up the fight against the big, bad corporation. There's a continuing culture that seems to believe big companies are evil and make bad sites because they want to trick people. The truth, as I have experienced, is that it's more a sin of neglect than of malice. No one sets out to build a bad site. So many people responsible for these sites have way too much on their plate. They have internal and external pressures that lead to bad decisions that lead to bad sites (and so on, and so on).

Explaining why a site is bad could go on forever, but the bottom line is this: We get paid to help the companies that hire us to explain their value to their users.

3. User experience is not about technology. 

Within the UX field, there is a group that is pulling things deeper and deeper into the tech side. Whenever this happens, the usefulness of the web seems to slide backwards. From my humble observations, the web started out pretty shaky. Then terms like "usability" and "user experience" started being tossed around, and the web was on it's way to getting useful.

Enter 2.0. People were all dazzled by all the new toys and undid much of the progress. This is a gross generalization, but the trick of our field as we mature will be to incorporate the bright, shiny x.0 object while maintaining a focus on the basics. No matter what technology comes along, we should always remember that there is a person using it, and it's not the users fault.

4. I like the quotes.

"User experience design isn't a checkbox. You don't do it and then move on. It needs to be integrated into everything you do," Liz Danzico says.

"Interface is a component of user experience, but there's much more,"Peter Merholz says.

5. Since everyone's name is linked, it's a good resource to find some super smart people and their blogs.

Here's what I think she missed:

1. There's no mention of Information Architecture, other than glossing over it under "User Experience is not a single discipline." Interface Design and Information Architecture are not the same thing. A good site can be built without an interaction designer (mentioned as a component of UX again and again), but not without good Information Architecture. She doesn't make a home for what role Information Architecture has within user experience in this article, and I think that's a huge miss.

2. "User experience is not the role of one person or department"should be "Making sure someone is caring about the user experience is everyone's role." I've heard a couple of other people make the same comment ("it's everyone's role") and I completely disagree. People want to be responsible for it (see #2 above), but caring about it isn't the same as getting it done. Everyone wants to take credit for when it's good, but there needs to be someone accountable for when it's not. This is a legitimate job with too many tasks to be shared across a variety of people who probably already have too much on their plate or other jobs to attend to.

3. There's no mention of content and how it fits into User Experience. It's a huge oversight. People want the content to be good, but they want someone else to make it that way. Too bad the users judge by what is said as much as how the site works. Which is why content needs a new home.