Recognize a usability issue when you see it - 3, undo and change of mind
When usability testing, participants would often
* open a page then go back;
* make an edit then undo it;
* go with
Recognize a usability issue when you see it - 3, unexpected behavior
When usability testing, participants will find new and creative ways to get tasks done.
Some UXRs I mentored would gracefully
Recognize a usability issue when you see it - 2, hesitation
In the previous episode: failing a task is not the only sign of a usability issue. There are more subtle
Start with an easy task
It's a well-known advice that: When usability testing, start with the easiest task so the participant can get the hang
Don't do exploration task
When giving tasks to participants in usability sessions:
DON'T: "Tell me what you see on this dashboard"
DO: "Check if
Recognize a usability issue when you see it - 1, emotions
As I was watching fresh UXRs doing usability tests I noticed their biggest mistake was not recognizing usability issues when
Unpack why user asked the question
It's commonplace among UX Researchers that when usability testing, we shouldn't answer the participants' questions. But we shouldn't remain silent
Stick with the task like a bulldog
This will sound trivial, but I see it all too often: when the participant goes off-topic mid-task the UXR forgets
Don't give away the goal of the research
When usability testing
* "The goal of the test is to find problems in the design."
* "We want to see
Don't invite opinions
When usability testing, try avoiding opinion mode at all costs.
* "We want you to review the prototype and give