5 methods to improve your user test
User testing is an incredibly valuable tool to test whether your audience appreciates the (prototype of your) product. It has many advantages such as saving you and your organisation time and money in the development process, providing a better user experience, increasing your customer’s satisfaction and many more.
But conducting a reliable user test is not as easy or simple as you might think. That’s why we created a short video to explain the process to our testers. And summarized our 5 best tips to help you organise a successful user test and get the most important insights you need to design and develop products and services people enjoy.
1. Plan your test to the T
When you’re conducting a user test, preparation is everything. But how do you prepare for it?
First of all, it’s important to decide on the actual goal of your user test such as desirability, user friendliness, but in most cases it’s a mix of both. Once this is settled, you can start thinking about the most important questions to ask the participants.
Second, it’s essential to find the right people for your tests. Making sure you don’t compromise the test by recruiting less-than-ideal participants will already put you in a good position. If you really want to nail the test, use an external recruiting agency and decide the exact profile you want to recruit. Make sound agreements and follow up thoroughly.
Third, decide on the type of user test you want to conduct. You can either organise a formal or a guerrilla user test. In the former, you have a lot of control: you’re able to choose the location, invite the participants… While with the latter, you just start questioning people on the street. There are more parameters out of your control. Guerrilla tests are especially useful when you’ve just kicked off a new project, or as an easy way to find your target group in one location.
2. five perfect users is better than twenty okay ones
When you think about user testing, you might picture 20 different people getting tested. However, Jakob Nielsen’s research shows that elaborate user testing is a waste of resources. Just recruiting 5 participants for a test and running different small tests instead of a couple of big ones is much more valuable and efficient. That’s for usability tests, not for desirability tests though.
Testing 5 people gives you 80% of the insights on problems you need. Invite 6 participants because there’s always someone who gets sick or has to switch up their schedule. An extra tip from the house? Recruit a variety of people who have the right background.
3. Test your technical setup beforehand
When it comes to your technical setup, preparation is once again key. If you know everything works, you’ll feel better and less stressed as you’re conducting the test. In this way, you’ll create a safe environment for your participant.
To do the test, we use a software called Lookback at Leap Forward. We like it because it’s easy to use, you can observe the participant without having them notice and stress out. Also, if you send the participant a step-by-step plan beforehand on how Lookback works, the user test goes a lot smoother.
4. Don’t forget GDPR
It doesn’t have to be complicated, just either asking your participants a couple of questions or offering them a simple form at the beginning of the user test should do the trick. Another option is to do it a couple of days or weeks before, when you sign them up for the test, with an online survey like a Typeform. It’s also easier to respect people’s privacy in this way.
5. Create a safe space for the participants
Last but not least is the interview qualities of the one who’s running the test. You can prep everything beforehand, but if your interviewer doesn’t have the following important qualities, you won’t get accurate results.
There are different soft skills required for a great test: creating a safe space, being able to comfort people, not taking remarks personally… And on the other hand, the interviewer also can’t give a presentation of the prototype or answer any questions, otherwise the results could be compromised. That’s also why it’s less interesting to let the person who designed the prototype run the test. Often, the designer is attached to his creation in some way.
One way in which you can make sure the user test is not compromised is by answering the participant’s question with another question, for example: “What would you like to see there?” In this way, you’re saving time and you get a new insight.