Skip to content

B1.1 User-Centred Design

B1.1.4 Usability Objectives

Usability objectives are criteria used by designers to evaluate how easy, efficient, memorable, safe, and satisfying a product is to use.

Usability objectives help designers analyse products from the user's perspective and identify opportunities for improvement.

They are important because they help create products that are:

  • easier to use,
  • more intuitive,
  • more efficient,
  • safer,
  • and more enjoyable for users.

Key Idea

Usability objectives help designers improve the interaction between products and users.


Main Usability Objectives

Usability Objective Main Focus
Learnability How easily users learn to use the product
Efficiency How quickly users can perform tasks
Memorability How easily users remember how to use the product
Errors How many mistakes users make and recover from
Satisfaction How pleasant and enjoyable the product is to use

1. Learnability

Learnability refers to how easily users can accomplish basic tasks when they first encounter a product.

Products with high learnability are:

  • intuitive,
  • easy to understand,
  • simple for first-time users.

Key Aspects

  • intuitive design,
  • clear instructions or labeling,
  • logical layout of controls or features.

Evaluation Methods

Designers may evaluate learnability by measuring:

  • time needed to complete a task,
  • number of attempts required,
  • frequency of referring to instructions.

Example: Coffee Maker

A coffee maker with clearly labelled buttons and a simple step-by-step brewing process would score highly in learnability.

Key Idea

Products with good learnability reduce confusion and improve first-time user experiences.


2. Efficiency

Efficiency measures how quickly users can perform tasks once they have learned how to use the product.

Efficient products:

  • reduce wasted time,
  • simplify interactions,
  • improve productivity.

Key Aspects

  • streamlined processes,
  • minimal steps required,
  • well-positioned controls and features.

Evaluation Methods

Designers may analyse:

  • task completion time,
  • number of steps needed,
  • user productivity metrics.

Example: Professional Camera

A professional-grade camera with customizable buttons for quick access to common settings demonstrates high efficiency.

Key Idea

Efficient products allow users to complete tasks quickly and effectively.


3. Memorability

Memorability assesses how easily users can reestablish proficiency after a period of not using the product.

Products with good memorability:

  • are consistent,
  • use familiar layouts,
  • avoid unnecessary complexity.

Key Aspects

  • consistent design patterns,
  • logical organisation of features,
  • memorable icons and labels.

Evaluation Methods

Designers may measure:

  • task success after periods of non-use,
  • relearning time,
  • user recall of functions.

Example: Microwave

A microwave with clear and familiar buttons for common functions such as popcorn or defrost demonstrates good memorability.

Key Idea

Good memorability reduces the need for users to relearn how products work.


4. Errors

Errors focuses on how many mistakes users make, how serious the mistakes are, and how easily users can recover from them.

Good product design aims to minimise user mistakes and improve recovery processes.

Key Aspects

  • error prevention features,
  • clear warning messages,
  • simple recovery processes.

Evaluation Methods

Designers may analyse:

  • frequency of user errors,
  • severity of mistakes,
  • recovery time after errors.

Example: Washing Machine

A washing machine with a child lock feature and warning messages before irreversible cycles demonstrates good error management.

Important

Products should minimise user mistakes and make recovery from errors easy and safe.


5. Satisfaction

Satisfaction measures how pleasant and enjoyable a product is to use.

This objective focuses on the emotional response users experience while interacting with the product.

Key Aspects

  • aesthetic appearance,
  • comfort,
  • positive emotional experience,
  • sense of accomplishment.

Evaluation Methods

Designers may use:

  • satisfaction surveys,
  • recommendation likelihood,
  • emotional response analysis.

Example: Office Chair

An ergonomic office chair that is both comfortable and visually attractive would likely score highly in satisfaction.

Key Idea

Products that create positive user experiences are more likely to be successful and appreciated by users.


Quick Recap

  • Learnability focuses on how easily users understand a product
  • Efficiency measures speed and productivity
  • Memorability evaluates how easily users remember the product
  • Error analysis helps improve safety and usability
  • Satisfaction focuses on comfort and positive user experiences

B1.1.5 Task Analysis

Task analysis is a strategy used by designers to develop empathy and better understand how users perform tasks in order to achieve a goal.

Task analysis helps designers understand:

  • how users interact with products,
  • what steps users follow,
  • what difficulties users experience,
  • and where improvements can be made.

By studying user behaviour, designers can create products that are more intuitive, efficient, and user-friendly.

Key Idea

Task analysis helps designers understand the user’s experience when completing a task.


What is Task Analysis?

Task analysis involves breaking a complex activity into smaller and manageable steps.

This allows designers to study:

  • the sequence of actions,
  • user behaviour,
  • decision-making processes,
  • and potential usability problems.

Why is Task Analysis Important?

Task analysis helps designers:

  • develop empathy for users,
  • understand user needs,
  • identify pain points,
  • improve efficiency,
  • discover opportunities for redesign.

Example: Using a Coffee Machine

A designer may analyse how users prepare coffee using a coffee machine by observing every action performed during the process.

Key Idea

Designers must understand not only the product, but also how users interact with it.


Main Objectives of Task Analysis

Objective Purpose
Understand user behaviour Identify how users interact with products
Identify difficulties Detect usability problems and frustrations
Improve efficiency Reduce unnecessary actions and complexity
Develop empathy Understand the user’s experience and needs
Support redesign Discover opportunities for improvement

Conducting a Task Analysis

Task analysis usually follows a structured process.

1. Identify the Task

Designers first define the specific activity they want to analyse.

Example

Preparing a cup of coffee using a coffee machine.

2. Gather Information

Designers collect information by:

  • observing users,
  • conducting interviews,
  • recording user actions,
  • analysing existing instructions or documentation.

Observation

Observing real users often reveals problems that may not appear during technical testing.


3. Break Down the Task

The activity is divided into smaller sequential steps.

Example: Coffee Machine Task Steps

1. Fill the water container
2. Insert coffee capsule
3. Close the machine
4. Select coffee type
5. Press start button
6. Pour coffee into cup

Key Idea

Breaking tasks into smaller steps helps designers understand user interactions more clearly.


4. Analyse Each Step

Designers evaluate:

  • time required,
  • physical effort,
  • mental effort,
  • possible confusion,
  • potential errors.

Example

Users may struggle to correctly insert the coffee capsule because the compartment design is unclear.

5. Identify Critical Points

Critical points are steps where:

  • users frequently make mistakes,
  • tasks become slow,
  • frustration occurs,
  • safety risks appear.

These areas often become priorities for redesign.

Example

Users may accidentally spill hot coffee when removing the cup due to limited space below the machine.

Important

Critical points often reveal the best opportunities for product improvement.


Benefits of Task Analysis

Task analysis helps designers create products that are:

  • easier to use,
  • safer,
  • more efficient,
  • more intuitive,
  • better adapted to user needs.

Quick Recap

  • Task analysis studies how users complete tasks
  • Complex activities are divided into smaller steps
  • Designers observe user behaviour and difficulties
  • Task analysis helps identify pain points and inefficiencies
  • The process supports empathy and product improvement

Case of Use: Marcos’ Assignment Submission

Use case: Marcos is a Year 12 student who needs to submit a History assignment online before 23:59.

Marcos has finished his document at 21:30 and needs to upload it to the school platform. However, the process creates uncertainty because:

  • he has several files with similar names,
  • the platform contains many subjects and assignments,
  • the submission process is not completely clear,
  • he is not fully sure whether the file has been submitted correctly.

Objective for the Student

Carry out a task analysis for this use case and identify opportunities for improvement.


User Context

Marcos has saved his assignment as:

“Historia_final_definitivo_v3.pdf”

However, he also has other similar files, such as:

  • “Historia_borrador”
  • “Historia_final_BUENO.pdf”

This creates confusion and increases the risk of uploading the wrong file.


Task Analysis Application Step by Step

1. Define the Task

Chosen task: Submit an assignment online correctly.
Stage User Action
Before The student completes the assignment
During The student uploads the file
After The student checks that it has been submitted

2. Observe Users

When observing students using a school platform, designers should analyse how they actually complete the task.

Students usually:

  • search for the assignment,
  • upload a file,
  • sometimes upload the wrong file,
  • do not always check if the file has been submitted.
Important Things to Observe
  • whether students use a phone or computer,
  • internet speed,
  • clarity of the platform interface,
  • file organisation habits,
  • how students react to confirmation messages.

Typical Problem

Students may upload the wrong file because several documents have similar names.

3. Break Down the Steps

The task can be broken down into smaller sequential actions.

Actual Steps
  1. Log into the platform
  2. Find the subject
  3. Locate the assignment
  4. Click “Submit”
  5. Select the file
  6. Upload the file
  7. Confirm submission
  8. Check that the submission was successful

Key Idea

Breaking the task into steps helps designers identify where users may experience confusion or frustration.


4. Create a Visual Map

The process can be represented as a storyboard or sequence map.

Example: Storyboard Sequence

1. Marcos opens the school platform
2. He logs in
3. He enters the History subject
4. He searches for the correct assignment
5. He clicks “Submit”
6. He selects a file from his folder
7. He uploads the file
8. He confirms the submission
9. He checks whether the assignment appears as submitted

Important

The order of actions must be clear so designers can understand the user journey.


5. Analyse Each Step

Designers analyse the task to identify usability problems and areas for improvement.

Problem Area Issue Identified
Efficiency Too many clicks are needed to reach the assignment
Ergonomics The platform may be difficult to use on a mobile device
Cognitive Load It is not clear whether the file has been submitted
Errors The student may upload the wrong file

6. Identify Key Moments

Critical points are the steps where users struggle the most.

Critical Points in Marcos’ Task
  • searching for the assignment,
  • selecting the correct file,
  • uploading the file,
  • confirming the submission,
  • checking whether the file has been submitted.

Important

Critical points are the moments where design improvements can have the greatest impact.


7. Suggest Improvements

Based on the task analysis, designers can suggest improvements to reduce confusion and improve usability.

Possible Design Solutions
  • make the “Submit” button more visible,
  • show a clear message: “SUBMITTED SUCCESSFULLY”,
  • provide a file preview before final submission,
  • add a double confirmation message,
  • highlight the selected file name clearly,
  • show a checklist before submitting.

Design Improvement Focus

A good redesign should reduce user errors, lower cognitive load, and make the submission process clearer and more efficient.

Quick Recap

  • Task analysis breaks a user activity into smaller steps
  • Marcos’ goal is to submit the correct assignment online
  • The main risks are confusion, wrong file upload, and unclear confirmation
  • Critical points include finding the assignment, selecting the file, and confirming submission
  • Design improvements should make the process clearer, faster, and safer