From Interface Evaluation to Experience Auditing
From Interface Evaluation
to Experience Auditing
Define a focused audit, understand user goals and select the key tasks that will guide an evidence-based evaluation.
Module overview & learning objectives
A UX audit examines how effectively a digital product supports users in achieving their goals. It goes beyond the appearance of individual screens to consider tasks, pages, devices and service touchpoints.
In this module, you will identify visual, usability and service issues, describe user goals and task contexts, and define a manageable audit scope. You will select three to five key user tasks to guide the evaluations in subsequent modules.
By the end of this module, you should be able to:
- Distinguish interface evaluation from experience auditing.
- Recognise visual, usability and service issues.
- Describe user goals and the contexts in which tasks take place.
- Define audit boundaries and desktop and mobile coverage.
- Select three to five realistic tasks with observable completion conditions.
- Separate evidence, interpretation and assumptions.
UX Audit Scope & Key User Task List
From screens to experiences
Interface evaluation focuses on elements such as typography, layout, buttons, forms and menus. Experience auditing examines how these elements work together as users pursue a goal: where they begin, what they need to know, which decisions they make and whether they can complete the task.
Interface evaluation
Is the button readable? Is the form clearly labelled? Does the page have a clear visual hierarchy?
Experience auditing
Can a prospective learner find a suitable course, understand the requirements and submit an enquiry with confidence?
A course website may have attractive images and clear typography, yet make it difficult to compare fees or understand what happens after an enquiry. An experience audit follows the broader journey.
How well does the product support the user’s goal within the context of the task?
Visual, usability & service issues
These categories can overlap. Describe the observed problem before assigning a label. Expand each category for an example.
Visual issues
Examine readability, spacing, hierarchy and visual clarity.
Example: Important eligibility information has little visual emphasis and is difficult to notice.
Record: The page location, the affected information and a screenshot showing its presentation.
Usability issues
Examine how users understand and operate the interface.
Example: A form rejects an entry without explaining how to correct it.
Record: The input, the steps taken and the error message displayed.
Service issues
Examine how the digital interaction connects to the wider service.
Example: An enquiry confirmation gives no indication of when or how the user will receive a response.
Record: The confirmation message and any stated next steps.
“The primary action is difficult to distinguish from secondary links” is more useful than “The page looks outdated.”
User goals & task context
A user goal is what someone wants to achieve. A task is the activity they undertake to achieve it.
User goal
Choose a course that fits my needs.
User task
Find and compare course fees, schedules and entry requirements.
Task context describes the conditions that may influence the experience.
| Context | Questions to consider |
|---|---|
| Knowledge | Is the user familiar with the service or visiting for the first time? |
| Device | Are they using a desktop computer or a mobile phone? |
| Environment | Are they in a quiet setting or travelling? |
| Constraints | Do they have limited time, connectivity or attention? |
| Access needs | Might they use a keyboard, screen reader or enlarged text? |
Use research, analytics, support enquiries or stakeholder information to understand users. When evidence is unavailable, state assumptions explicitly.
Define the audit scope
The scope establishes what will be evaluated and why. A focused scope makes the work practical and supports comparable evidence collection.
| Scope element | What to specify |
|---|---|
| Product or service | The website, application or digital service. |
| Audit purpose | The question or problem the audit will investigate. |
| Target users | The users whose goals will guide the evaluation. |
| Journey boundaries | Where the evaluated experience begins and ends. |
| Included areas | The pages, features and interactions to examine. |
| Devices | The desktop and mobile contexts to cover. |
| Exclusions | Areas outside this audit. |
| Constraints | Limits involving time, access, accounts or available evidence. |
Evaluate how prospective learners find a course and submit an enquiry on desktop and mobile. Start at the course website homepage and end at the enquiry confirmation. Exclude payment and the student portal.
Select three to five key tasks
Choose tasks that matter to users and support the audit purpose. Consider frequent tasks, tasks essential to completing a journey and tasks associated with known difficulties.
Write each task as a realistic scenario with an observable completion condition. Avoid instructions that reveal the interface route.
Leading instruction
“Click Courses, select Business and open the fees tab.”
This tells the evaluator which route to follow.
Goal-based task
“You are considering a business course. Find its total fee and check whether you meet the entry requirements.”
This describes the outcome without prescribing the route.
| Key user task | Successful completion |
|---|---|
| Find a suitable course | Identify a course meeting the stated subject and study-mode requirements. |
| Check eligibility | Locate the entry requirements and determine whether the stated qualifications qualify. |
| Compare two courses | Find enough information to compare fees, duration and schedules. |
| Submit an enquiry | Send an enquiry and identify the expected next step. |
Specify relevant details, such as the user’s qualifications or preferred study mode. Use an authorised test environment or stop before submitting a real enquiry during a walkthrough.
Evidence & desktop–mobile contexts
Record what happened, where it happened and how it could affect the task. Useful evidence includes screenshots, page locations, interface messages and documented steps.
| Evidence layer | Example |
|---|---|
| Observation | On the mobile course page, fee information appears inside a collapsed section labelled “Additional details.” |
| Interpretation | The label does not indicate that the section contains pricing. |
| Potential user impact | Users comparing costs may overlook the fee information. |
Desktop walkthrough
Record the browser and viewport. Examine visible navigation, information hierarchy, keyboard interaction and the route between relevant pages.
Mobile walkthrough
Record the device or simulated viewport. Examine collapsed menus, touch controls, stacked content, form entry and information hidden in expandable sections.
Use the same task goals across devices, while recording differences in the route and presentation. If you simulate a mobile viewport, identify it as a simulation.
An expert walkthrough can identify potential barriers. Claims about actual user behaviour need supporting evidence, such as usability testing or recorded feedback.
Practical activity & learning output
Select a website or application and prepare a concise audit brief.
- State the product, audit purpose and target users.
- Define the journey boundaries, included areas and exclusions.
- Describe the desktop and mobile contexts to examine.
- Write three to five goal-based task scenarios.
- Define successful completion for each task.
- Identify evidence sources, constraints and assumptions.
Submission checklist
- A clear audit purpose and target-user description.
- Specific scope boundaries and device coverage.
- Three to five realistic user tasks.
- An observable completion condition for every task.
- Relevant constraints, assumptions and evidence sources.
Could another evaluator understand what to inspect and what successful task completion looks like? Your brief will provide the foundation for Module 2’s heuristic evaluation.
Review & reflection
Use these prompts to review your audit brief. Expand each prompt after considering your answer.
Why is an attractive interface not enough?
Users still need to find information, make decisions and complete tasks. Experience auditing examines how the journey supports these goals across pages, devices and service touchpoints.
What makes a task suitable for the audit?
It is relevant to a user goal and the audit purpose, has a realistic scenario and defines observable success without prescribing an interface route.
How should you report a suspected barrier?
Record the observation, explain your interpretation and describe the potential impact. Identify assumptions and avoid presenting predicted behaviour as a tested fact.
Start with user goals, define the scope, select three to five tasks and collect evidence in context.