PROTOTYPE TEST

1
Usability Testing

• Usability testing is a popular UX research

methodology.
• In a usability-testing session, a researcher (called a
“facilitator” or a “moderator”) asks a participant to
perform tasks, usually using one or more specific
user interfaces.
• While the participant completes each task, the
researcher observes the participant’s behavior and • Even the best UX designers can’t design a
listens for feedback. perfect — or even good enough — user
• The phrase “usability testing” is often used experience without iterative design driven by
interchangeably with “user testing.” observations of real users and of their
interactions with the design.
• Researcher never test the user, only the interface
with the users. • The only way to get UX design right is to test it.

2
Usability Testing

• A usability-testing session involves a participant and a

facilitator who gives tasks to the participant and observes
the participant’s behavior and listens for feedback.
• The facilitator may also ask follow-up questions to elicit
detail from the participant.
3
Ilustrasi Usability Testing

• In this usability-test session, the participant sits on

the left, and the facilitator sits on the right.
• The participant uses a special testing laptop,
which is running screen-recording software.
• The laptop has a webcam to capture the
participant’s facial expressions and is connected
to an external monitor for the facilitator.
• The facilitator listens to his feedback, administers
tasks, and takes notes.
• The photo captures the moment after the
participant’s task, when the facilitator is asking
him follow-up questions.

4
Types of Usability Testing

• Usability testing can be either qualitative or quantitative.

• Qualitative
• Qualitative usability testing focuses on collecting insights, findings, and anecdotes about how people
use the product or service.
• Qualitative usability testing is best for discovering problems in the user experience. This form of
usability testing is more common than quantitative usability testing.
• Quantitative
• Quantitative usability testing focuses on collecting metrics that describe the user experience.
• Two of the metrics most commonly collected in quantitative usability testing are task success and time
on task.
• Quantitative usability testing is best for collecting benchmarks.
• The number of participants needed for a usability test varies depending on the type of study.
• For a typical qualitative usability study of a single user group, five participants to uncover the majority
of the most common problems in the product may be sufficient.
5
Types of Usability Testing

• Remote vs. In-Person Testing

• Remote usability tests are popular because they often require less time and
money than in-person studies.
• Two types of remote usability testing: moderated and unmoderated.
• Remote moderated usability tests work very similarly to in-person studies.
• The facilitator still interacts with the participant and asks her to perform
tasks.
• However, the facilitator and participant are in different physical locations.
Usually, moderated tests can be performed using screen-sharing software
like Skype or GoToMeeting.
• Remote unmoderated remote usability tests do not have the same facilitator–
participant interaction as an in-person or moderated tests.
• The researcher uses a dedicated online remote-testing tool to set up written
tasks for the participant.
• Then, the participant completes those tasks alone on her own time.
• The testing tool delivers the task instructions and any follow-up questions.
• After the participant completes her test, the researcher receives a recording
of the session, along with metrics like task success.
6
TASK SCENARIO FOR
USABILITY TESTING

7
Turn User Goals into Task Scenarios for Usability Testing

• The most effective way of understanding what works and what doesn’t in an
interface is to watch people use it.
• When the right participants attempt realistic activities, you gain qualitative insights
into what is causing users to have trouble → help you determine how to improve
the design.
• Also, you can measure the percentage of tasks that users complete correctly as a
way to communicate a site’s overall usability.

8
What Users Need To Be Able To Do

• To observe participants, you need to give them something to do.

• These assignments are frequently referred to as tasks or “activities” (to avoid making the participants feel
like they’re being tested).
• Rather than simply ordering test users to "do X" with no explanation, it's better to situate the request within
a short scenario that sets the stage for the action and provides a bit of explanation and context for why the
user is "doing X."
• Before you can write the task scenarios used in testing, you have to come up with a list of general user
goals that visitors to your site (or application) may have.
• What are the most important things that every user must be able to accomplish on the site?
• Find articles on a specific topic?
• Sign up for UX Week seminars?
• Learn about offered consulting service?
9
Engage Users with Task Scenarios

• Once what the users' goals are determined, task scenarios that are appropriate for usability
testing need to be formulated.
• A task scenario is the action that you ask the participant to take on the tested interface.
• For example, a task scenario could be: You're planning a vacation to New York City, March 3 − March
14. You need to buy both airfare and hotel. Go to the American Airlines site and jetBlue Airlines site and
see who has the best deals.
• Task scenarios need to provide context so users engage with the interface and pretend to
perform business or personal tasks as if they were at home or in the office.
• Poorly written tasks often focus too much on forcing users to interact with a specific
feature, rather than seeing if and how the user chooses to use the interface.
• A scenario puts the task into context and thus, ideally motivates the participant.

10
Why Scenarios?

• Scenarios describe the stories and context behind why a specific user or
user group comes to your site or using your system
• Scenarios note the goals and questions to be achieved and sometimes
define the possibilities of how the user(s) can achieve them on the
site/system
• Scenarios are critical both for designing an interface and for usability
testing.

11
What to Consider When Writing Scenarios

• Who is the user? Use the personas that have been developed to reflect the real,
major user groups using your system.
• Why does the user use your system? Note what motivates the user using your
system and their expectation upon the usage, if any.
• What goals does he/she have? Through task analysis, you can better understand
the what the user wants on your system and therefore what the system must
have for them to leave satisfied.

• Some scenarios also answer:

How can the user achieve their goals on the system? Define how the user can
achieve his/ her goal on the system, identifying the various possibilities and
any potential barriers
12
TIPE-TIPE SKENARIO

13
1. Goal- or Task-Based Scenarios

• State only what the user wants to do.

• Do not include any information on how the user would complete the scenario.
• These scenarios are useful in helping to define your site architecture and content.
• You should give these types of scenarios to users in a usability test.
• It gives them a reason and a goal for going to the site, but it lets them show you
how they would use the site to accomplish that goal.

14
1. Goal- or Task-Based Scenarios

• Example: A parent is worried about a ten-year old refusing to drink milk and
wants to know if it really makes a difference that the child is getting very little
calcium.
• Example: You are traveling to Seattle for your job next week and you want to
check on the amount you can be reimbursed for meals and other expenses.

15
2. Elaborated Scenarios

• Give more user story details.

• These details give the Web team a deeper understanding of the users and users’
characteristics that may help or hinder site interaction.
• Knowing this information, the team is more likely to develop content,
functionality, and site behavior that users find comfortable and easy to work with.

16
2. Elaborated Scenarios

• Example: Mr. and Mrs. Macomb are retired schoolteachers who are now in their
70s. Their Social Security checks are an important part of their income. They've
just sold their big house and moved to a small apartment. They know that one of
the many chores they need to do now is tell the Social Security Administration
that they have moved. They don't know where the nearest Social Security office
is and it's getting harder for them to do a lot of walking or driving. If it is easy and
safe enough, they would like to use the computer to notify the Social Security
Administration of their move. However, they are somewhat nervous about doing
a task like this by computer. They never used computers in their jobs.

17
2. Elaborated Scenarios

• Example (cont): However, their son, Steve, gave them a computer last year, set it
up for them, and showed them how to use email and go to websites. They have
never been to the Social Security Administration's website, so they don't know
how it is organized. Also, they are reluctant to give out personal information
online, so they want to know how safe it is to tell the agency about their new
address this way.

18
3. Full Scale Task Scenarios

• Include the steps to accomplish the task.

• A full-scale scenario can either report all the steps that a specific user currently
takes to accomplish the task or it can describe the steps you plan to set up for
users in the new site.
• Scenarios at this level are very similar to use cases, but they lay out the steps
from the user's point of view rather than from the website's point of view.
• They explain how the site supports the goal-oriented scenarios that you started
with.

19
Test Scenario
Alur di Interaction Map dan Sketsa Scenario

Breakdown Konteks
dari User Goal Environment

Ekspektasi
Testing

20
Contoh Scenario & Task (dari sisi user)

21
Contoh Scenario & Task (dari sisi user)

22
Rules to write useful task scenarios

23
Avoid giving clues in the scenario

• Don’t use uncommon or unique words used in your website or app.

• Why not?
Testers will scan the screen to find these words and you won’t get many insights
about the usability of your website.

24
Write in a clear, understandable, and easy to follow.

• Write the way you talk and don’t try to sound scientific or academic.
• Pre-test your tasks with colleagues or friends to make sure they are easy to
understand and people really know what you want them to do.

25
Trim any detail that’s not absolutely necessary

• Your task scenarios should set a context and provide users with necessary details
like a username or a special delivery address.
• Everything else is unnecessary.
• Keep your task scenarios as short as possible and let testers figure out things for
themselves.

26
Engage Users with Task Scenarios

27
1.Make the Task Realistic

• User goal: Browse product offerings and purchase an item.

• Poor task: Purchase a pair of orange Nike running shoes.
• Better task: Buy a pair of shoes for less than $40.
• Asking a participant to do something that he wouldn’t normally do will make him
try to complete the task without really engaging with the interface.

28
2. Make the Task Actionable

• It’s best to ask the users to do the action, rather than asking them how they
would do it.
• If you ask “How would you find a way to do X?” or “Tell me how you would do Y”
the participant is likely to answer in words, not actions.
• And unfortunately, people’s self-reported data is not as accurate as when they
actually use a system.
• Additionally, having them talk through what they would do doesn’t allow you to
observe the ease or frustration that comes with using the interface.

29
2. Make the Task Actionable

• User goal: Find movie and show times.

• Poor task: You want to see a movie Sunday afternoon. Go to www.fandango.com
and tell me where you’d click next.
• Better task: Use www.fandago.com to find a movie you’d be interested in seeing
on Sunday afternoon.

30
3. Avoid Giving Clues & Describing Steps

• User goal: Look up grades.

• Poor task: You want to see the results of your midterm exams. Go to the website,
sign in, and tell me where you would click to get your transcript.
• Better task: Look up the results of your midterm exams.

31
3. Avoid Giving Clues & Describing Steps

• Step descriptions often contain hidden clues as to how to use the interface.
• For example, if you tell someone to click on Benefits in the main menu, you won’t
learn if that menu label is meaningful to her. These tasks bias users’ behavior and
give you less useful results.

32
References

• https://www.usability.gov/how-to-and-tools/methods/scenarios.html
• https://www.nngroup.com/articles/task-scenarios-usability-testing/
• https://www.nngroup.com/articles/usability-testing-101/
• https://www.nngroup.com/articles/task-scenarios-usability-testing/

33
terima
kasih
34