Usability Testing and the Developers (Part1)

 

Summary:

This article deals with the �How to� of presenting your
usability test findings to the developers, and convincing them about the
changes in design.

 

Introduction

Face it. It is their baby. They have toiled and burnt their
midnight oil before finally coming up with a product that they are so proud of.
Now, picture this: A hot shot comes along tests the product with some users and
lists down a set of changes to be made to the product. It will make the developers�
blood boil. You are bound to face hostile developers who aren�t too keen to
lend an ear to your words on usability, and the worst thing that can happen to
you is, when the developer takes it out on you by arguing about the credibility
of your findings. I have faced that. And it sucks. Big time. Is there a
solution to it?

 

Involving the developer in your usability testing

 

Involve the developer. Make him or her sit there and watch
the user struggle with their product. Nothing convinces like a first hand
experience. I was conducting a simple test and I had insisted that the guy who
developed it sit with me. I had trouble in stopping my developer friend from
telling the user �Come on! Can�t you see it! It is right there! Click it!
For god�s sake!� It was agonizing for him. Later on, he confided to me that
it brought about a fresh perspective to him.

(He also delivered the classic line, �Why do you choose such
dumb users?�

My response was, �Nothing is dumb. It works or it
doesn�t!�).

 

You have to make the developer realize that the product
means everything only to him/her, not to the user. Tell them that the product
is like a doorknob. Everybody might use it, but no one cares about it. The
point is, the software product that the developer is in love with, could stand
between the user and his pre-lunch coffee. They just want to get over with it
and move on. Ask the developer, �How many colors does your free web mail
service site uses?� I am sure they don�t remember. And also ask, �So why
should the user spend time and effort figuring out how to use this software?
Don�t you think you should make it as obvious, as simple and as intuitive as
possible?�

�To be continued

Add to:del.icio.us| Digg| Reddit| StumbleUpon| Technorati