---
title: "UserTesting | Skills We Assign For | Azendo"
description: "UserTesting for research at pace — participant access, panel limits, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/usertesting/"
---

[Skills](https://azendo.co/skills/) Design and research 

# UserTesting.

UserTesting is a research platform providing access to participants from a large panel, session recording with screen and audio, and analysis tooling for moderated and unmoderated studies.

## 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](https://azendo.co/services/ux-ui-design/) 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.

## Roles we assign UserTesting for

* [UX Researcher UX/UI design](https://azendo.co/services/ux-ui-design/ux-researcher/)

## Service lines it sits in

* [UX/UI design](https://azendo.co/services/ux-ui-design/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in design and research

* [Zeplin — skill we assign for](https://azendo.co/skills/zeplin/)
* [Framer — skill we assign for](https://azendo.co/skills/framer/)
* [prototyping — skill we assign for](https://azendo.co/skills/prototyping/)
* [information architecture — skill we assign for](https://azendo.co/skills/information-architecture/)
* [journey mapping — skill we assign for](https://azendo.co/skills/journey-mapping/)
* [user research — skill we assign for](https://azendo.co/skills/user-research/)
* [User interviews — skill we assign for](https://azendo.co/skills/user-interviews/)
* [moderated and unmoderated usability testing — skill we assign for](https://azendo.co/skills/moderated-and-unmoderated-usability-testing/)

## 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.

[All skills we assign for](https://azendo.co/skills/)