Voice of Customer
Part of Customer experience for digital services
Observing where users struggle with an online task
Plan a neutral online task, record moments of struggle and turn observations into bounded usability findings.
To find where an online task breaks down, watch someone pursue a clear goal without guiding their clicks. Note the point of hesitation and what happened next, then check whether the obstacle came from the interface, the wording or the service itself.
Set a believable task
Choose one outcome the service is meant to support. For example, ask a participant to update a contact address and show how they would know the change had taken effect. Start where a customer would normally start, rather than on the relevant form. Use a prototype or a safe test account when a live task would change personal records.
Recruit people who might use the service, including those with different devices, access needs and digital confidence. Give each person a neutral goal. A prompt such as “find the edit button” gives away the path you need to observe; “change the address used for future messages” leaves the choice to them.
Make an observation record
For each meaningful pause, note the step, the participant’s action, their words and the outcome. Keep any inference about what they expected separate from what you saw or heard. Useful observations include opening the wrong menu, rereading a label, entering information in an unexpected format, recovering from an error and seeking help. Note when a participant succeeds only after a moderator intervenes.
Let the person work unless they become stuck or distressed. A neutral follow-up such as “What were you looking for here?” can clarify behaviour without supplying the answer. Record any intervention so the final outcome is not mistaken for unaided completion. Obtain consent for recording and handle notes containing personal information appropriately.
| Possible observation | Question to investigate |
|---|---|
| Someone returns to the start page after submitting | Was the confirmation unclear, or did the change fail to take effect? |
| Several people choose the same wrong option | Does the label describe the organisation’s process rather than their goal? |
| Someone cannot use a control with a keyboard | Is the interaction blocking access? |
These examples are diagnostic prompts, not findings about a tested service.
Observation vs. Inference: What to Record
- Observation (record this)User rereads the label 'Update contact details' three times before clicking.
- Inference (do not record as fact)They didn’t understand the label because it’s poorly worded.
- Observation (record this)User attempts to tab through form fields but cannot reach the submit button.
- Inference (do not record as fact)The keyboard navigation is broken due to poor design.
Turn sessions into a bounded finding
Group observations by task step and type of difficulty. Distinguish a single issue from a repeated pattern, and note who was represented in the sessions. Check support records or service data to investigate scale, but do not turn a small usability study into a population estimate.
Write a finding in terms of the customer’s goal and the observed barrier. An illustrative finding might be: “People in these sessions could not tell whether the address change had taken effect.” Then propose a change and a follow-up task that could show whether it helped. If the task failed after submission, investigate the service outcome as well as the screen.
Key Observations from User Sessions
- Common struggle
- Unable to confirm change took effect
- Pattern observed
- Multiple users select wrong menu option
- Accessibility issue
- Keyboard-only users blocked from completing task
