Where user research fits in a long-term product team.

Teams always have a model of their users; the question is whether it comes from evidence or from extrapolating from themselves. The second is the default and it is systematically wrong, because the people building a product are unrepresentative of the people using it in almost every way that matters.

A small amount of research changes decisions disproportionately. Five interviews will surface most major usability problems and will contradict at least one thing the team was confident about, which is usually worth more than the research cost several times over.

What your dedicated team does with user research.

Research is most valuable as a steady rhythm. A team talking to users every few weeks builds accumulating understanding; one that researches at the start of a project and not again is working from a snapshot that ages.

Making it continuous is what a standing assignment enables and project-based capacity does not, which is why it is agreed as a committed monthly capacity.

Common user research use cases.

  • Assumptions contradicted early A handful of sessions surfacing what the team was confidently wrong about.
  • A steady research rhythm Continuous contact, so understanding accumulates instead of ageing.
  • Decisions traceable to evidence Design choices backed by findings.

Adding user research skills to your team.

Research sits with the designers we assign to you, run as a continuous rhythm.

At Azendo, user research work sits with a dedicated UI/UX design team. You can add user research capacity as one dedicated specialist or as part of a wider remote team, managed by a service delivery manager from our offices in Thailand. Companies hire dedicated developers this way under one agreement and one monthly fee.

Tell us what your roadmap needs user research for.

A service delivery manager will reply with the specialists we'd suggest, the monthly capacity and what the first month looks like.

Loading the form…

We reply within one business day.