Tests with guerrilla users are a very useful and cheap alternative type of test to test a digital product, be it a website or an application.
They are informal, relatively quick tests that help test ideas and get feedback to uncover UX issues.
Before carrying out a guerrilla test, it is convenient to use another type of Usability and interface, such as , among others.
What are guerrilla tests?
A guerrilla test is a type of test that allows you to collect user feedback on a design or prototype. It is a very simple type of test and since it allows you to test designs very quickly, it has a low cost.
It basically consists of asking passers-by, entering a cafeteria and asking the attendees or simply assaulting your co-workers to find out their opinion and how they interact with the design or prototype.
Logically, this type of test or proof, has its putos against. Targeting users or people who don’t fit into the product’s defined persona archetype may result in us never discovering the problems faced by the actual users who will use the product.
They are not very deep tests and the data and conclusions obtained from them must be viewed with some suspicion.
On the other hand, it has certain advantages, such as having a person who has never looked at or interacted with the design or prototype. It can give you a fresher view of the product.
Also, another advantage can be the fact that you do not have to go through the entire process of recruiting participants for the test or wait for the tool to get you the right panelists.
How to do a guerrilla test with users?
For the results of a guerrilla test to have some validity, they must be planned and well structured.
What are we going to test?
It is recommended that you be clear about what you want to test. Above all, you have to test short and complete processes.
An example would be testing the login or registration, the filtering system by performing a search, the payment process or Check Out, etc.
Where to take the test?
Think about where we are going to go to look for the participating users. A cafeteria, a park, in the corridors of our office, etc.
Depending on the type of user we need for the test, one site or another will be more recommended. It also depends on the number of users required, but 5 users should be enough to obtain conclusive data.
The ideal would be to carry out the test with 8 or 10 users where 5 resemble the product’s target audience.
How is the guerrilla test done?
When we start the test, we must ask the participating users to comment aloud on their impressions. It is important to encourage him to delve into the problems that he finds when executing the specific tasks.
More important than what the user tells us is to observe what he does and how he does it.
Calculate the approximate time to execute the task.
How should the script be?
You need to have a script for the test. We must explain to the participating users what the test consists of, the task that they are going to execute as well as the time that is required.
They have to sign the permission to be recorded and the confidentiality agreement, so it is also necessary to explain it.
Comment with the user that it is not an exam or test for him, but for the design. It is necessary to make clear the task that must be carried out and that once it begins, it cannot receive help from the observer or facilitator.
You have to be kind, close and polite so that the user relaxes and explain why it is important that they comment on their impressions out loud.
Do not forget to be grateful to the participating users, they are giving you their time and few things are so valuable.
In conclusion, comment that guerrilla user testing should never replace more formal user researchbut if there is not enough budget, this type of test is better than none.
Facebook Comments
Disqus