Choose a focused learning goal
Pick a question such as whether visitors can find the right service, compare products or complete an enquiry. Use people whose needs are relevant to that task where possible. A session with colleagues can reveal some problems, but it should not be described as representative customer research without justification. Record who participated and the limits of the exercise.
Write tasks without giving away the answer
Describe a situation and the result the participant wants, rather than telling them which button to press. For example, ask someone to find the information needed to discuss a catalogue website. Avoid wording that repeats the exact navigation label if that would remove the uncertainty you want to observe.
Observe respectfully
Explain the session, obtain appropriate consent for any recording and avoid collecting unnecessary personal information. Let the participant talk through their thinking without correcting every mistake. Record where they hesitate, misunderstand a label or abandon a route. The aim is to evaluate the interface, not judge the participant’s ability or train them to use the design.
Prioritise patterns and serious obstacles
Summarise observations with examples and the task context. Do not turn a small session into a precise claim about all users or a guaranteed conversion increase. Fix severe blockers and recurring confusion first, then test the important changes. Keep the notes available so later design decisions can be traced to actual observations rather than remembered impressions.
Your practical checklist
- Define a focused question and participant fit
- Use tasks that do not reveal the path
- Get consent and record observable difficulties
- Prioritise blockers without overstating the sample
Working through a similar question?
We’re happy to help you find a practical starting point.
Talk to AMGK
