I just published an article in UXmatters, Conducting Qualitative, Comparative Usability Testing. It’s about conducting usability testing with two or more designs, early in the design process to get better information and better user feedback, before settling too soon on one particular design.
When participants are able to experience multiple designs, they can provide better feedback. As a result, you can gain greater insight into the elements of each design that work well and those that cause problems.
Today I published an article in UXmatters, Testing Your Own Designs. It’s often been said that you shouldn’t conduct usability testing on your own designs, because you may be too biased, defensive, or too close to the design to be an impartial facilitator. Although that may be the ideal, often UX designers don’t have a choice. They may be the only person available to test the design, so if they don’t test it, no one will. So in this article I provide advice for those times when you have to test your own design, and I also provide advice for when someone else tests your design.
I was hesitant to write this article, because it’s been a topic that many others have written about, but I felt that as someone who has been on all sides of the issue, I had something additional to add. Here are some other good articles about this topic:
Testing Your Own Designs: Bad Idea? and Testing Your Own Designs Redux by Paul Sherman
Should Designers and Developers Do Usability? by Jakob Nielsen
BECAUSE NOBODY’S BABY IS UGLY … SHOULD DESIGNERS TEST THEIR OWN STUFF? by Cathy Carr at Bunnyfoot
I published a new article in UXmatters this week, “What Could Possibly Go Wrong? The Biggest Mistakes in Usability Testing.”
This article came out of thinking about all of the mistakes I’ve made, and problems I’ve encountered, over the last 16 years conducting usability testing. I think it’s good to look back and think about the lessons you’ve learned. This article is jam-packed with advice learned the hard way.
Usability testing is the most highly structured user research method. Compared to field studies and interviews, the tasks and questions are usually highly planned, and you usually stick pretty close to the discussion guide. That also makes it the most repetitive method. You see the same types of people performing the same tasks and answering the same questions over and over again.
After you get some experience, you can begin to think of usability testing as routine and pretty easy. At a former company, it was the first task that we gave to new researchers, just out of college. It seemed like the easiest method to learn. That may be true, but there are still all kinds of mistakes that can occur. This article discusses the main problems and how to avoid them.
Photo by Blue Oxen Associates on Flickr
I just published an article on UXmatters, 10 User Research Myths and Misconceptions. It addresses common misunderstandings about user research that I’ve encountered over the years.
Here’s a bonus outtake from the article, Myth 11…
Myth 11: Field Research Is Better Than Usability Testing
On the other end of the spectrum from those who don’t understand the difference between user research and usability testing, are the user research elitists who think up-front, generative user research methods are far superior to usability testing. In this view, field studies take researchers out of the lab to observe people in their natural environments performing their usual activities, while usability testing takes place in the sterile, artificial environment of a usability lab and asks people to perform a limited set of artificial tasks. Instead of learning about people and what they really do, usability testing provides the limited value of learning whether people can perform your artificial tasks.
The Truth: Both Field Research and Usability Testing Have Their Places
Field studies and usability testing are two different methods used for different, but equally important, purposes. Field studies provide information to inform design, while usability testing evaluates a design. You have to make interpretations and conclusions from the user research and apply that to a design. Even after very thorough user research, you’re never completely sure that what you’ve designed will work well for the users. Usability testing is the evaluation that either confirms your decisions or points you to refinements. Both user research and usability testing are important and necessary. There’s no reason we can’t appreciate the value of both methods.
Analyzing the data is the most interesting part of user research. That’s where you see the trends, spot insights, and make conclusions. It’s where all the work comes together and you get the answers to your questions.
Why, then, did I publish an article in UXmatters – Analysis Isn’t Cool? All too often I’ve realized that clients, management, and project stakeholders underestimate the analysis phase and just want to get to the answers. People like to say that they did user research, but they don’t like to spend the time to analyze the data. They like the deliverables, whether they read them or not, but they don’t want to spend a lot of time on the analysis to produce those deliverables.
In this article, I discuss what analysis involves, methods for individual and group analysis, and ways to speed up the analysis process.
Photo by Josh Evnin on Flickr
I’m happy to report that user experience is alive and well in Bulgaria. I just got back a week ago from attending and presenting at UXify 2015 in Sofia, Bulgaria. A very enthusiastic audience of over 300 people attended a day of presentations, followed by a day of in-depth workshops. UXify was the end of a month of user experience events – UX Month Sofia.
On Friday, June 19th, I presented User Research in the Wild, a presentation about visiting people in their natural environments to observe their tasks. In addition to being a how-to guide, I covered common problems you face in conducting field studies and how to solve them, and how to overcome obstacles to field research.
On Saturday, June 20th, I gave a workshop on Paper Prototyping to about 20 attendees. After an introduction to creating paper prototypes and how to test them, the participants divided into groups to create their own paper prototypes. We only had a limited time to create them (about 40 minutes), so I was very surprised by how detailed and creative their prototypes turned out in such a short period of time. Each group of two people then joined with another group to take turns conducting usability testing on their paper prototypes. Each group did four rounds of tests, switching roles, so that each person was able to experience the role of the facilitator, “the computer,” and the participant twice. The attendees really seemed to have a good time, with a lot of laughing and joking around.
In between my own presentations, I attended several interesting presentations about dashboard design, gamification, socially responsible design, and ecommerce user experience.
It was a fun trip, and it was nice to meet a lot of similar people, in another culture, who are similarly committed and enthusiastic about user experience.
I recently wrote an article in UXmatters about how the information displays in my Prius changed my driving behavior. Seeing the miles per gallon (MPG) I was getting in real time, acted like a feedback loop, causing me to make a connection between my driving actions and how they affected my gas mileage.
Something I didn’t write about, however, was another type of feedback that you get as a Prius driver – the drivers behind you. When someone drives up behind you and tailgates, that’s feedback to go faster or get out of the way. However, that feedback conflicts with the feedback from your Prius to drive economically.
To drive economically and get good gas mileage requires a steady pace and slow acceleration. That doesn’t necessarily mean slow driving. I drive 65 to 75 miles-per-hour to work, while getting about 60 miles per gallon. But it does mean that you need to avoid quickly accelerating. So being a Prius driver sometimes puts your gas-saving goals in conflict with the drive-fast goals of other drivers. There’s a reason some drivers get annoyed by Prius drivers.
Although I always drive in the right hand or middle lanes when I’m driving economically, I’ve found that the best way to drive economically is to ride along behind someone else. If there’s no one in front of you, and another driver comes up from behind, you feel pressure to go faster. If you have another driver in front of you, you have an excuse to drive economically. It’s that guy’s fault, you’re just driving behind him at a reasonable distance. So you don’t feel the pressure to speed up.
I’ve gotten my highest MPG records from driving (at a safe distance) behind a truck that was going a steady, reasonable speed (maybe 70 MPH). That allows you to ignore the feedback from drivers behind you and pay attention to the MPG display.
Sounds like I’ve put too much thought into this gas mileage thing with my Prius. Maybe, but I save money and it’s fun.