Research & evaluation

Usability testing

Find out where people struggle by watching them use your website, app or prototype.

When this helps

Whether you are preparing a launch, comparing designs or investigating a difficult task, usability testing helps you see what people understand, where they hesitate and when they need help.

What you receive

A research plan, task script, observation record, synthesis and prioritised recommendations; recordings only where agreed and consented.

Recruit for the question

We define who needs to take part from the service question: current or prospective users, relevant experience, digital confidence, device use and access requirements. Participant numbers need a rationale based on the variation being studied and the decisions ahead. A convenient group of colleagues is not automatically a substitute for the intended audience.

Recruitment feasibility is checked before promising a schedule. The proposal identifies who recruits, any incentive arrangement, screening criteria and how participant information will be handled. For sensitive settings, use appropriate consent and safeguards and avoid requesting unnecessary personal information.

Tasks that reveal the experience

Tasks describe an achievable goal without telling someone which button to press. We agree a realistic starting point, what counts as completion and what the moderator should observe. A pilot helps reveal wording that gives away the answer or a prototype state that prevents meaningful investigation.

During a session, the researcher records what happened, where help was needed and what remains ambiguous. Direct observations and participant comments stay distinct from interpretation. The analysis should include both recurring patterns and important exceptions, rather than reducing every experience to an average score.

Example task prompt

Template: “You need to change an appointment because you cannot attend. Show how you would find your options.” Observe whether the person locates the appointment, understands available actions and knows whether a change has been confirmed. Use a safe test environment and fictional appointment details.

The fintech scenario shows another proposed investigation. It is illustrative material, not a completed study.

How the engagement runs

  • Discuss what you need to learn, who uses the service and what you already know.
  • Agree the research activities, access requirements, deliverables and what is included in the proposal.
  • Carry out the research and explain both what we observed and what we think it means.
  • Walk your team through the findings, prioritise improvements and agree what needs a follow-up check.

Cost and timing

Recruitment difficulty, participant access needs, study format, incentives, task complexity and analysis depth. The proposal states the scope, fee basis and dependencies. Recruitment, stakeholder availability or access to a test environment can affect the calendar; no fixed turnaround is assumed before these are understood.

What to bear in mind

A small qualitative study can uncover important problems without estimating their prevalence across the whole customer base.

Your team receives recommendations it can discuss and implement with its chosen supplier. Where another method would answer the question better, we explain why before proposing additional work.