Where UserTesting fits on a long engagement.

Finding participants is the bottleneck in most research programmes, and a panel removes it. Getting eight relevant participants in two days rather than three weeks changes research from something that has to be planned around to something that fits inside a sprint.

Panel participants are not your users, and that limitation is real. They are experienced at being research participants and are selected on demographics rather than on genuinely using your product. For evaluating general usability that is acceptable; for domain-specific workflows it is not.

What an assigned team does with UserTesting.

Knowing which questions the panel can answer is the judgement that matters. Testing whether a checkout flow is comprehensible works well; testing whether a specialist tool fits a radiographer's workflow does not.

Being clear about that rather than using the convenient option for everything is part of research rigour, held under outsourced design team capacity.

What we use UserTesting for.

  • Research inside a sprint Participants in days rather than weeks, so testing fits the delivery rhythm.
  • General usability evaluated Comprehension and flow questions the panel can answer well.
  • Domain research sourced properly Real users approached separately where the panel cannot represent them.

How UserTesting capacity is assigned.

Research operations sit inside design capacity, with the participant source matched to whether the question is general or domain-specific.

Tell us what your roadmap needs UserTesting for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

Loading the contact form… You can also email hello@azendo.co.

We reply within one working day. No obligation, and no newsletter.