The aim of user research in the alpha phase is to:
- improve the team’s understanding of your users and their needs
- test different design ideas and service prototypes with likely users
- learn how to build or improve your service so that it helps users achieve their goal
How to do user research in alpha
You need to think about your service from end to end and consider all the ways that users interact with it (including all tools, transactions, support and offline steps).
Who to research with
You must do research with a broad range of users, including:
- those with limited digital access and confidence
- people with a range of visual, hearing, motor and cognitive impairments
You should include people who provide the service or who support other users (for example, caseworkers, call centre agents and charity workers).
Typical user research activities
You can learn more about your users and your design ideas by:
- using interviews and visits to deepen your understanding of relevant aspects of your users’ lives and work
- trying out design concepts with likely users to see how well they meet user needs
- testing interactive prototypes to explore the usability of different designs
When you’re recruiting participants with disabilities, it might not be possible to test:
- paper prototypes with users who are blind or partially sighted
- prototype code with people who use assistive technologies like screen readers or speech recognition software - you can do this in beta when you start working with production code
From these research activities, you’ll typically get:
- a better understanding of your users’ needs, including their support and access requirements
- feedback on how well your designs work for users
- helpful insight into usability issues related to layout, functionality and content
You’ll have done enough research when you’re confident that your design solutions will meet the needs of your users, including those with disabilities and support needs.
You may also find these guides useful:
Clarified accessibility requirements.
Guidance first published