User Testing Exam Task Design and Scenario Creation 1 — Questions and Answers
Question 1: What is the primary principle behind writing a good usability test task?
- Tasks should be goal-oriented and realistic without revealing the steps to complete them (Correct answer)
- Tasks should list every step the user must take
- Tasks should test only one feature per session
- Tasks should be written in technical system language
Correct answer: Tasks should be goal-oriented and realistic without revealing the steps to complete them
Good tasks give users a realistic goal to achieve without scripting the path, enabling observation of natural navigation decisions.
Question 2: What is meant by 'task granularity' in test design?
- The level of specificity or detail in a task — too broad fails to focus observations, too narrow removes realistic choice (Correct answer)
- The number of tasks included in a single test session
- The complexity score assigned to each task
- The time allocated per task in the test plan
Correct answer: The level of specificity or detail in a task — too broad fails to focus observations, too narrow removes realistic choice
Task granularity refers to how specific or broad a task is; the right granularity focuses the test without prescribing the user's path.
Question 3: Why should usability test tasks use the product's actual user goals rather than feature names?
- Feature names prime users to navigate to specific locations rather than revealing natural wayfinding behavior (Correct answer)
- Feature names are usually trademarked and cannot be used in documentation
- Using product features makes tasks too easy to complete
- Feature names are unfamiliar to new users
Correct answer: Feature names prime users to navigate to specific locations rather than revealing natural wayfinding behavior
Tasks framed around user goals (e.g., 'find a gift for your friend') rather than features (e.g., 'use the gift finder tool') reveal whether the interface's information architecture is intuitive.
Question 4: What is a 'benchmark task' in usability testing?
- A standardized task used across multiple study rounds to measure performance changes over time (Correct answer)
- The first task in a session used to warm participants up
- A task designed to be the most difficult in the test
- A task taken directly from a competitor's product
Correct answer: A standardized task used across multiple study rounds to measure performance changes over time
Benchmark tasks are kept identical across test rounds so that metrics like completion rate and time-on-task can be compared to track improvements.
Question 5: Which of the following is an example of a realistic, goal-based task scenario?
- You need to send a birthday gift to a friend in Denver — find a suitable option and complete the purchase (Correct answer)
- Click on the 'Shop' menu and select 'Gifts'
- Test the checkout feature by adding item SKU 4521 to your cart
- Navigate to the product page and evaluate the layout
Correct answer: You need to send a birthday gift to a friend in Denver — find a suitable option and complete the purchase
Realistic scenarios embed the task in a believable context and describe the user's goal without prescribing the path or revealing UI labels.
Question 6: What is the risk of including too many tasks in a single usability session?
- Participant fatigue reduces data quality and may cause rushed, inaccurate performance on later tasks (Correct answer)
- Researchers will have too much data to analyze effectively
- Participants will learn the interface too well between tasks
- The screener will need to be longer to match all tasks
Correct answer: Participant fatigue reduces data quality and may cause rushed, inaccurate performance on later tasks
Too many tasks cause cognitive fatigue, degrading the quality of observations and making it harder for participants to engage authentically with later tasks.
User Testing Exam Task Design and Scenario Creation 1
What is the primary principle behind writing a good usability test task?