Yusef Hassan Montero, proposes the following definition for the test with users: “It is a Usability test that is based on the observation and analysis of how a group of real users use a website, noting the problems of use with which they are in order to fix them later. It is a test carried out in the laboratory, that is, we should not confuse it with a field study.”
When executed correctly following the process and taking into account , it perfectly complements the .
Next, you will be able to find some resources or keys for the planning part in carrying out tests with users.
Questionnaire before performing the Usability test
It will help us identify or verify the participating user and their profile. It will also serve to “break the ice”. It is a good time for the Usuability test participant to feel that we are close and relax.
Depending on the type of test some of the generic questions could be:
- What’s your name?
- What do you do (profession, activity)?
- What experience do you have on the Internet?
- Do you surf regularly? How many hours do you sail a day?
- What websites do you usually visit?
- What are your favorite websites?
The script for the facilitator and test participants
The script must be a document that helps the facilitator and the participants of the usability and User Experience test. It must be able to be understood by anyone who reads it.
Some key aspects to introduce in the script:
1. Introduction
The first thing is to greet and welcome the participant, as well as thank them for the fact that they want to participate in the test.
Next, we remind you that before participating in the test, you must have read and signed the privacy conditions and the consent to participate in the test.
Next, explain how many tasks the test consists of and how much time you have in total to take the test. At this point it is important to note that if a task is too complicated for you, move on to the next.
Highlighting this fact gives us the opportunity to explain to the participant that we are not evaluating him, but rather the design or functionality of the product.
In the introduction, we must ask the participant that as they carry out the tasks, it is essential that they comment aloud their impressions, that their opinion is what matters most to us and that they can be extremely critical.
At this point we will also explain that there may be other people in the room as observers and that they will be taking notes but will not be able to help you complete the tasks.
2. Test tasks
The tasks are the actions that we are going to ask the participants to carry out in the interface that we are testing.
For each task, it is necessary to define and explain the context of the scenario so that the person performing the test can understand why they are doing it.
It is very important to mimic the real context of use so as not to force the participant to perform specific tasks in a way that is not theirs. We cannot bias user behaviors.
You should not give hints, force to use features or describe steps.
It is recommended to use a standard or common language for the description of the tasks. Using a technical language can lead the user to a block in the understanding and assimilation of the task.
It is necessary to communicate how long it is estimated that it will take to complete each task.
3. Close
After the explanation and description of the last task, as a closing, we will once again thank you for your participation. We will pass the post-test questionnaire and we will give you financial compensation if it exists.
Questionnaire after performing the test with users
Once the user has finished performing all the proposed tasks, it is interesting that you are asked to express your feelings, thoughts or opinions about the interface.
It is necessary to avoid that the answer is a simple “I think everything is fine” or “I see everything correct”.
We will encourage the user to expand and expand on their response, especially if they are not positive towards the design or functionality.
Facebook Comments
Disqus