The first thing you have to do before any user test is to assume that you know nothing. Having that mindset will help you to not assume that you know all the answers. Instead it will encourage you to keep asking the users “Why?”
“You know nothing, Jon Snow!” ― Ygritte, Game of Thrones
It is easier to understand information that you already agree with. This is one of the biggest traps during user testing. It is incredibly easy to pay attention to data that confirm your ideas which leads to disregarding contradictory data. During a test you should consider all feedback the same, don’t sort it yet. Things can seem unimportant in the beginning but may be a part of a bigger pattern later on.
The main reason of testing is to find what to improve in your product. A user test that didn’t result in a list of improvements is useless and the test should be corrected.
Be aware, keep an objective thinking, be open to new! Iterate on the tests!
Reading body language is an indispensable tool during the test. People tend to say different things than they act on. Often, they say what they think you want to hear, from the fear of not looking stupid.
Also, a natural experience is unnoticeable for the user when using a product. You need to observe:
A product should speak by itself, and if it doesn’t there’s a bigger problem. Let the user explore the product without instructions, encourage them to ask questions, to be curious, and to own the journey. There you can learn what is the natural flow/way for the user to explore the product, and importantly, if you covered all user cases. This is an opportunity to find something that you haven’t thought of.
One of the most basic mistakes during user testing is to have poorly written questions. There are a lot of strategies on how to ask a question in order to receive an honest answer.
Do not include the answer you are looking for in the question. Avoid :
Use instead :
Avoid asking YES or NO questions. These questions can only approve or disapprove what you think. It doesn’t give you any new or unexpected information.
Never ask for the solution, ask for the need they have, what are their pain points.
“If I had asked people what they wanted, they would have said faster horses.” ― Henry Ford
“Why?” is the key question during a test. The answers/result do not have any value if you don’t understand why the user chose a particular answer. It is not the answer that is important, but all the factors that influenced that answer. The more times you ask “why?”, the more chances you have to understand the real pain points. Also, comprehend how relevant are they for your product and how can you solve them.
There are more reasons why you should ask the same question multiple times. This can ensure:
It is good to have duplicate questions at the start and end of questionnaire.
Negative feedback is more important than positive feedback. It is a way to learn what’s not working well in your product. Assuming no product is perfect, there is always room for improvement! The design process includes lots of testing and iterations. Negative feedback takes out poor solutions and leaves space for the better ones. There are always many bad solutions before a great one appears. The faster the bad ones are cut, the closer you get to the great one.
Receiving negative feedback and understanding it, is the key to a better product.
Always give users the opportunity to say things that you haven’t asked. By the end the of the test, people are generally comfortable enough with you and the product, and they are ready to suggest ideas, to change answers to previous questions, and to talk more.
Instant feedback is the easiest way to screw up user testing. By approving or disapproving an answer, you encourage or discourage the user. In this way you influence the answers you’re receiving. During user testing there are no right or wrong answers, there is only data and answers that could create more questions! Stay neutral, interact with the user, and let them know that they are doing a great job!
Listen, observe and keep the user talking!