The only way they to know if an application works well for users is to conduct usability testing. A usability test does not need to be expensive like having a laboratory where cameras are mounted in every angle and viewers are on the other side of a one-way mirror looking at monitors that track the users eye movements and heartbeat.
A usability test can be as simple as grabbing the next person that passes by the hallway. You don’t even need a hundred people; five people is enough.
We conduct usability tests because we know that someone with a set of fresh eyes will find more problems in the application than someone who has been looking at the user interface everyday for the past 189 days. When we ask people to participate in our usability tests, we expect them to be super-critical of our software. We tell them we’re evaluating the software, not the person. It is absolutely OK if they tell us that the “interface sucks” or “I felt dizzy after looking at this page. I think I’m gonna puke.”
But as experienced by Jensen Harris, a Microsoft programmer working on the Office software, people tend to become less critical during usability testing as if they are suffering the Stockholm syndrome — a case where the hostage becomes sympathetic with its captors. Why does it happen?
It’s human nature
If someone invited you over dinner and asked you what do you think of the food you won’t say it tastes bad. You will most likely say, “I love it” or “you should start a restaurant business.” It is our human nature not to say bad things of a person especially if we are in her house. Probably after the usability tests, you would tell your friends that the new software Greg is working is a mess, but not infront of him.
We think we’re computer illiterate
When we were kids at school, if we’re the only person who got the division wrong, we feel very bad. Can’t blame you. The other kids would probably be laughing and by now you think you’re stupid. Add the look in your teacher’s face as if telling you to pack your things, go home, and sell banana. Growing up, we were conditioned that if you don’t get it, it is your fault. Every time we can’t figure out how a software works, we tend to blame ourselves, rather than the software, because we think we are “computer illiterate.” If only we could adapt to this software, then there wouldn’t be any problems.
So what can you do?
- Be friendly. It’s difficult to tell the truth if someone would kill you by doing so.
- Reassure the participant that this is not about her, this about the software.
- Be always on the lookout. If the participant appears hesitant to comment, help her speak out like asking questions such as “Do you find the text confusing?”