User research is an essential part of the Design Thinking and User Experience (UX) design process. The application of user research is to
Discover innovative ideas by observing what users do
Close the gap between designers’ and users’ mental models
By getting feedback from those who will use our product (or service) regularly, we want to make sure that the design will delight and help them to get things done adequately.
At Bonanza Design, we offer two packages:
By which we discover new ideas and design user-centered solutions. At this phase, we conduct extensive user research to study users’ needs and discover new patterns of consumption
By which we design pixel perfect applications. At this phase, we rely heavily on usability testing to make sure the finished product is usable and engaging
In this article, we offer you our hard-earned experiences doing user research and usability testing for years. We categorized the insights into four segments
Tap into communities across social media such as Facebook groups, Linkedin groups, Reddit channels, etc. You can source testers within a few hours.
This is a great option for testing cases that deal with consumer products. The only caveat is that testers could cancel on you easily. And it happened to us (a lot!)
TIP: If you need to source 5 testers, aim to book at least 8.
In this case, you have to create the NDA, book the time with the testers, and guide them into the facility. All on your own. It’s resource-consuming for sure.
Through platforms such as Testing time, you can book testers. Platforms as such offer options to filter your search. This is a great option for testing cases that deal with Business to Business (B2B) products.
Bear in mind that, by adding a few filters, the total price of sourcing 5 testers might easily go over 1000€. Use this option when you deal with a niche market in which finding the right person is strenuous.
In this case, you don’t need to do anything. The platform books the testers and makes sure they find their way to the doorstep of your office. You just need to open the door and say hello.
Your interview script is the guideline by which the team aligns on the purpose of the project and interviewer(s) performs their job. Sometimes you have to bring a professional from the outside of the organization to get the job done. Hence you want to make sure the interview script is clear and includes all the sections below:
You don’t need to go in-depth explaining the project but it should offer enough information so both the interviewer and testers understand the purpose of the project.
You want to explain the objectives of the testing. The clearer the objectives are, the more promising the results of the testing.
The next chapters are about the questions you want to ask. Try to be brief and ask only questions you need to answer. Your time is limited; hence your questions.
This is the part to write down the general questions you have about the users including where they live, what they do and their age etc.
Here you get more specific about their habits when it comes to the topic of the testing. For example, if you’re developing an app to track users’ diets, then the open-ended questions relate to how users deal with food daily.
Here to write down the tasks you’d like the testers to perform in case you have developed a prototype.
For example, you’re developing a landing page for a new product, and you’d like to know how testers feel about the information architecture and branding.
To get the testers’ impression, try the Five Second Test exercise first. Show the design for only five seconds. And then ask them about their impression. And then show the design again but this time with more time, and record what’s changed in their impression.
This is for when you’re developing a prototype of an app that performs certain functions. Then you want to test those functions with users like signing up or booking an appointment.
IMPORTANT: Often we only design tasks to test how usable the application is. Seldom do we design tasks to test whether testers are willing to contribute to the growth of the business and user base.
A user can contribute to the growth of the business in two ways
When you design a testing plan, it has to include a few tasks to test whether a user is willing to contribute to the growth of the application. How?
You want to get testers off-guard so their reaction would be genuine and honest.
Do not let the designers, product managers, or developers, who are invested in the project, to be the ones who interview testers. This is especially important if you have a prototype. Find someone outside of the team.
Midday is important! In case there are things to improve, you’d have enough time to implement changes.
Meet users where they are. Especially important if you’re conducting user research. For usability testing, it’s okay to invite them to your office.
Don’t show testers low-fidelity prototypes. Testers won’t take the testing session seriously. When you have low-fidelity prototypes, then test them internally so colleagues can spot the ice-berg-type usability problems. Then finalize the design and test them with real users.
We’ve tried 15, 30, 45 and 60-minute formats, none of them worked better than a 45-minute format. It’s just the sweet spot.
Study shows that interviewing five testers reveals about 80% of all the potential issues with your design. Also, our experience proves this claim right. On top of that, it’s only possible to test five users in a day.
To capture interview observations, notes, and scores for each task, use the rainbow sheet. Read about it here and look at it here.
Try to have two rooms. One room for the interview. The other room for your team to observe the interview via a TV and take notes. The Interviewer does only lead the session; the team does the note-taking.
Only do user testing in the morning and early afternoon. Leave the rest of the afternoon for the reflection and sorting insights
Hi there! My name is Claire and today I’ll be guiding you through the process. On behalf of my team, I’d like to thank you for being here with us. Your feedback means so much to our team.
Remind testers that we don’t test them and we’d like to get their reactions to certain things we’re working on. Remind them that their critical eyes could help so much to improve the experience.
Make testers feel comfortable first. Use an ice-breaker. Find a relevant topic to talk about e.g. today weather.
Your task as a testing team is to observe user behaviors. As the interviewer, stay in the background and don’t disturb the tester flow.
You want to record the testing session but before testers need to give their consent. Just google user testing consent form, and you get what you need.
Don’t help testers during the task performance. Let them deal with the task themselves. If they’re getting frustrated, don’t interrupt. Observe their situation and encourage them to talk about their frustration.
Be unbiased towards each screen and try not to point their attention to certain parts of the design.
Encourage testers to think out loud constantly. Ask them questions when they’re silent for a while. Silence yields more silence. Be careful. It’s a fine line though. Don’t keep interrupting them constantly. Give them enough time to express their thoughts seamlessly before you ask them a question.
I said you should be unbiased. However, here’s a trick. Early on, try to make a light-hearted joke about the design yourself e.g. Oops our designers forget to change this font again!
Doing that, it encourages users to express their judgment without the fear of being judged, wrong, or impolite. They see you as their friend. And that’s important.
Do not help testers to figure out things. Period.
Allow testers to reflect and summarize their experience and add the last points if they desire. Do not skip this part. Sometimes testers need time to conclude their thoughts and give their final feedback.
Great. Then iterate. Don’t be jaded by the results of the test. There’s no failure. Feedbacks are there for you to improve your work. Happy iterating!
Great. Then continue with the detailed design and preparing the assets for the development.
Reflect. Derive clear action points from studying the results of the tests, improve the prototype, and TEST again.
IMPORTANT: Do not continue without testing the improved version with the testers again. You want to proceed only if you got super positive results from the follow-up user testing session.
We have an amazing Instagram post that visualizes this section. Take a look here
This section is taken from the design thinking playbook. It’s a fantastic book and you should have it on your bookshelf.
We hope that you find this article helpful. As always in case you have feedback to share reach out to us at email@example.com
Receive handpicked content on design, UX, Innovation and sustainability every week