TLU-HCI Summer School 2013
Valeria Gasik, Zahhar Kirillov, Daria Tokranova
Select what user stories/use cases you would like to test
Write a simple script, distribute test session roles, specify
questions and determine tasks and their end-results
Organize and record usability test (notes/video)
Analyze results and make according changes
Most people are happy to
dedicate time to help you
out with your project,
even if it’s just on paper!
Although it’s just on paper,
plan and be prepared!
Tasks to test
“Find the nearest shop”
Any type of doable tasks with clear goals
but without speciﬁc clues of the solution.
“Change your password”
“Go to menu and edit
settings of your proﬁle”
“Rearrange search results
based on the location”
Maria likes second-hand clothes. She goes
on 2ndHand.com and browses the newst
offers. She searches for shoes and quickly
ﬁnds the ones she like. Maria adds them
to her shopping card.
Possible questions and tasks
“What can you do with this app?”
Task 1: Search for women’s shoes with the color of your choice.
Task 2: Buy your favorite pair.
Task 2: Buy your favorite pair of shoes.
User has completed, veriﬁed and paid for her order.
1.Add the product to the cart
2. Proceed to the checkout
3. Fill in needed information (x, y, z, ...)
4. Verify your order
5. Pay a) with online bank b) with credit card
6. Receive a receipt
Deal with errors, e.g.
“What do you think you can do
with this application?”
returns an error
“What do you think went wrong?”
“Do you like it?”New feature
“Er... sure, I like it” “Yeah, I know, it’s awesome.”
1.1.“First change your password”
1.“You need to make some modiﬁcations in your proﬁle.”
End-result: user replaces current password.
End-result: user ﬁnds how to change settings a) via proﬁle b) via settings icon.
• Write a simple script for yourself, if you have a
lot of testing to do. Number/name questions
and tasks to help documentation.
• Write down tasks on a separate paper so you
can show them to your test participants
• Specify, for yourself, end-results for the task.
Think about what “task not completed”could
thinks out loud
to user’s commands
+ Facilitator instructs the user
and helps the computer
Team of 2 or 3
Test structure example
Introduce team members and explaining the test method
Give instructions, e.g.“Point with your ﬁnger/pen to simulate a tap”
Mention that it is not a user who is tested but the system
2. Start with light background questions
E.g.“How often do you use travel planners?”
Explain brieﬂy what is the starting point,“This is the landing page of...”
3. Remind the participant to think aloud
E.g.“I think this link would lead me to…”
4.Introduce the ﬁrst task
Make sure that it’s clear for the user
5.Move to the next task
Continue when the goal is achieved or user expresses that
he/she does not know the answer.
6. Conclude the test session
Ask if user has anything to add
Thank the participant and discuss the results with your team
During the test pay attention to...
• Are participants doing what was expected?
• Did anything cause frustration or confuse?
• Anything new or surprising?
• Any paths that you haven’t thought of before?
• Was there a clearly preferred solution or path?
• Are some paths unused or “misused”?
Reﬂection and Design Changes
Bottlenecks in the process?
What paths were ignored or barely used?
What was clearly missing? etc.
Tip: Update before the next test user and see if it worked.