7 Testing, Feedback, and Iteration

Start with a focused test question

Usability testing evaluates whether people can use a design to achieve their goals. Usability depends on the users, their goals, and the context in which they use the product. It is commonly considered in terms of effectiveness, efficiency, and satisfaction.

A useful test begins with a decision the team needs to make and a focused research question. For example: Can first-time visitors find and book an available appointment? A specific question helps keep the test useful instead of turning it into a general request for opinions.

Prepare participants, tasks, and observations

Plan the test around the question it needs to answer. Choose a prototype or working service that can provide relevant evidence, and recruit people who represent the intended users, including people with relevant access needs.

Write realistic, goal-based tasks that do not reveal the intended steps. For example, ask a participant to find and book a suitable appointment with a clinician next week, rather than telling them to click a particular button.

Decide what to observe and record, including task completion, hesitation, errors, requests for help, and participants’ comments. Agree on consent and privacy before recording. A short discussion guide can help the facilitator introduce the test, explain tasks consistently, and keep sessions on track.

Try the tasks with a colleague first to catch unclear wording or prototype problems. Small, focused rounds can reveal issues early, and findings from one round can help shape the next.

Conduct sessions without leading participants

Explain that the design is being tested, not the participant, and that there are no right or wrong actions. Give each task in neutral language, then let the participant work. When appropriate, invite them to think aloud by describing what they expect, notice, or find confusing as they use the design. Avoid leading questions and avoid rescuing participants too quickly, since either can hide problems.

Observe both what participants do and what they say. Someone might describe a page as clear while repeatedly searching in the wrong place. Keep the observation separate from the interpretation: a note that someone paused at an address field for 20 seconds records behavior; concluding that the form is confusing is an interpretation that still needs investigation. A note-taker can help the facilitator focus on the session.

Interpret evidence and prioritize problems

After sessions, organize notes around the tasks and research questions. Look for patterns in where people succeed, hesitate, make errors, or take unexpected routes. Compare observed behavior with participants’ explanations, keeping direct evidence distinct from assumptions.

One person’s difficulty may reveal an important barrier, but a small usability-test sample does not establish how common that problem is across all users. Treat individual evidence as useful for identifying issues without overstating what it says about the wider user population.

Prioritize findings by considering how severely an issue blocks a user’s goal, who is affected, and whether the issue recurs. An unclear optional setting may be less urgent than a booking error that prevents someone from completing the main task. Where available, combine test observations with other relevant evidence, such as accessibility checks or support requests.

Revise the design and test again

Use findings to make specific design changes, then test whether those changes address the problem. The process is iterative:

1. Identify a user goal and a question about the design.

2. Test the design with representative users.

3. Record behavior and feedback.

4. Interpret patterns and prioritize problems.

5. Revise the design and test again.

For example, if participants overlook an appointment date because it is visually weak, a team might make the date more prominent and then observe whether people notice and use it in a follow-up test. Retesting matters because a change can solve one difficulty while creating another.

Share findings with the whole interdisciplinary team so research can inform design, content, development, and future priorities.