What we proposed
The workshop was broken down into three parts:
2. Performing an actual user test
3. Quick summary and subsequent analysis of the workshop
1. Introduction and inquiring about the participants’ knowledge of user tests (20 minutes)
After a little introduction about User eXperience and why we deem it important for projects, we first asked five questions (through a multiple-choice questionnaire) to learn what the participants knew about user tests. We focused on clichés that we encounter frequently. We used Plickers to make things a bit more fun and engaging for participants.
a. What do we essentially test during a user test?
b. How many users (by profile) are needed to detect more than 80% of usability problems?
c. Is a user test is always expensive?
d. What is the best moment to do a user test in a project?
e. Is it difficult to do a user test in agile mode?
The answers to these questions will not be given here; however, we answered each question in great detail and provided participants with information about user tests (goals, how-to, key points and resources).
2. Introduction and inquiring about the participants’ knowledge of user tests (20 minutes)
The next step of the workshop was to perform an actual user test.
Before the workshop, we chose a website for the general public. While looking good, this site had major usability flaws.
For this part of the workshop, we divided the audience into two groups of three or four people. In a personal envelope, we hid a personal role card for each member: one would play the part of a User while the others would be Observers.
Since the Observers were not familiar with the selected website, we asked the Users to exit the room for a few minutes so we could show the Observers the website and the normal steps to follow for the scenario.
Next, the Users came back and tried to carry out the tasks (with considerable difficulties) in 15 minutes. Rookie Observers were a little lost because of the overabundance of problems.
The next step consisted in reconstituting the Users’ journey and understanding why they had those problems. We suggested Observers should use the “5 WHYS” technique — a quick method for finding the cause of a problem that can also be used in situations other than user tests.
3) Quick summary and subsequent analysis of the workshop
To conclude the workshop, we asked each group to specify three good things and three problems that they detected during the test. Each group shared those results on a board.
It was difficult for them to find anything good to say about the site.
To conclude, we asked the participants to tell us what they thought about the workshop.