How do I run UX tests correctly?
The purpose of UX testing is to find weak points in the design to fix them before you start development. To understand where users may have problems, you need to run UX testing without hints. Obvious tasks and hints will help most users to pass a scenario correctly, but the results of this kind of survey won't show exactly what needs to be fixed in the prototype. Our recommendations will help you to compose your tasks properly and get a useful result.
Don't use open-ended questions. Ask questions in a way that allows users to respond with a click.
|
Bad |
Got it |
|
Is it convenient to choose a tariff based on price? |
Where would you click to choose the cheapest tariff? |
Give the user tasks they can relate to. Formulate your tasks using real-life situations. Respondents should feel that they are solving their own problems rather than just following your instructions.
|
Bad |
Got it |
|
Where do you click to add an item to favorites? |
You've been browsing an online store and found a great gift for your friend. You don't intend to buy anything now, but you want to easily find the product on the site when you decide to buy the gift. Where would you click? That way you don't hint at the Add to favorites button, and can observe how the user solves the problem. |
Explain the context. Your task description must make it clear to the user which service they're looking at, and how and why they got to the current screen. This will help the respondent to complete the task correctly, and help you get relevant data.
|
Bad |
Got it |
|
How would you navigate one category up? The user is unaware of what site they are on, why they see this screen, and why they have to go one category up. |
You are on an online store for stylists and want to buy makeup brushes. Where would you click to find them? |
Do not prompt users. Don't use the names of interface elements and don't give any direct instructions. In reality, users think in the context of their task rather than look for interface elements with certain names.
|
Bad |
Got it |
|
Click Order at the bottom of the screen. The user will search for the button with the desired name rather than follow the task scenario. |
You've had a look at the product range, made your choice, and want to buy a product. Where would you click? Here we have explained why the user needs to perform an action. |
Sometimes, task texts don't specify the answer directly, but give an obvious clue. It's better not to prompt the user in such cases, but instead describe a situation.
|
Bad |
Got it |
|
Where would you click to change the payment method? The task includes the answer: find the Edit button in the interface. |
You decided to pay for your order using Mastercard instead of Apple Pay. Where would you click? We provide a situation without giving any clues. |
You also shouldn't highlight areas in images or point at them with an arrow.
Test one scenario and give a single task at each step. For the respondent, each step is a separate page. If there are several tasks on the page, the user might do one task and skip another. In this case, you wouldn't know whether your scenario has been completed successfully or not.
|
Bad |
Got it |
|
Step 1. Follow the user and share any of their posts. At the first step, users much perform two actions straight away, and can start with either of them. That's why it's better to split the task into two steps. |
Step 1. You are interested in a user's profile on a social network, so you want to follow them. Where would you click? Step 2. You liked one the posts of this user and want your friends to see it too. Where would you click? Each step is a separate task, and the user knows the context. |
Avoid special terminology. Testing is run for a wide audience. Respondents are experienced online users, but they might not know some professional terms. Try to make your task understandable for everyone.
|
Bad |
Got it |
|
You went to the store's site and saw a pop-up after a few seconds. Where would you click? |
You went to the store's site, and after a few seconds a small window appeared. Where would you click? |
Be sure to test the prototype before the launch. All selected click areas must match the task. Use a preview to avoid mistakes when building a prototype. To do this, go to the What respondents will see section, click View test survey, and imagine you're one of the respondents taking the survey. Run a test scenario and make sure all options work correctly.
Tip
Select multiple areas if your task can be completed in several different ways (for example, by clicking a button or a menu link). To delete an area you don't need, click on it.
You can also go to
