Users identifiable as the person “juanjo”
brief searches saving stop words.
They quickly click on the snippets.
If they don’t find the information right away, they go back to google.
Users identifiable as the person “catalina”
very diverse searches.
They click on ads often, they don’t discriminate against them.
If they don’t find the information
they go back to google and modify the search.
In short, starting the test with a search will only take the user a few seconds and will not interfere with the rest of the test, so carrying it out is almost always interesting.
The important thing is that the user ends up reaching the page in question (in this case, the refrigerator or mobile section) and once there begins the rest of the tasks that actually make up the test.
፠ ask what they expect from each section/category
during a usability test it is common to talk a lot with the user.
It’s about understanding what’s going
on in your mind while you’re using the website, and that’s the biggest difference between cold analytical data and data obtained live, with feedback from the user themselves.
most interesting is, once the user has arrived at the site in question, to tell him not to click on anything yet and ask him an open question:
“ what kind of content do you expect to find when you click on these sections of the website?”
this can be very interesting when testing the effectiveness of the main navigation menu or a secondary menu of an e-commerce.
