You should plan user research at the start of each development phase, and regularly update your plan as you learn more about your users.
Agreeing your objectives and the approach you want to take will help you build a service that meets the needs of your users.
Decide your objectives and approach
Work with your team to define your research objectives and decide how you’ll approach the research.
Agree research questions
Start by running a workshop to capture and prioritise your research questions. In the workshop be careful to turn any unfounded assumptions and opinions into research questions.
Knowing the questions you need to answer and the assumptions you need to test will help you focus on the most important things your team needs to know.
In discovery, your research questions are likely to be broad and evolve quickly as you learn.
They should become more specific in later development phases, as you focus on particular user groups and parts of your service.
Identify user groups
Decide who you need to research with. Depending on what you need to learn, this could include all the different users of your service, or just specific groups.
In the discovery phase for a new service, you may not have a clear idea of who your likely users will be. Research this as a priority. As you learn about your users, you can create personas or profiles to capture and present what you’ve learned.
Choose relevant research activities
Choose research activities that will provide strong evidence and reliable answers to your questions, for the least time, effort and cost.
If the team doesn’t have much experience with user research, prefer simple methods like interviews and usability testing that the team can easily understand and join in with.
You’ll also need to consider what you need to do to access funding and how long it might take to arrange. Speak to your budget holder to find out more - this may be your delivery, product or service owner.
Decide your recruitment approach
There are different ways to recruit participants for user research. Once you know the research activities you want to do and the groups you want to research with, you can decide which recruitment methods will work best for you.
Some research methods have longer lead times than others, and some require an agreement with a supplier. Deciding your approach early on will avoid problems and delays later.
Map out rounds of research
Once you’ve worked out your research questions, user groups and activities, you can start preparing ‘rounds’ of research. Each of these should answer specific research questions with specific user groups.
Aim to do at least one round of research every 2 weeks.
Focus on your most important questions
Prepare just the rounds of research you need to answer your highest priority questions. You can arrange more rounds as you learn more about your users and your service.
As you prepare more rounds, make sure you stay in sync with your team’s high-level roadmap.
Don’t do lots of research that the team can’t respond to, or get left behind if they’re making quick progress.
Work out participant numbers
The number of people you need to research with in each round will depend on the method you’re using.
If you need more participants to get clear findings, do more rounds rather than one big round. That way you can adjust after each round.
For methods like surveys, A/B testing and benchmarking, you will need hundreds of participants to produce clear findings.
Whenever you recruit participants from a user group, make sure you include a good variety of the users within that group.
This may not be possible for smaller or more specialist user groups. In this case, plan specific rounds of research to:
- look at the most significant barriers that users with disabilities are likely to face
- identify support needs and test your support model
Procurement can take longer than you think so find out about it early. Ask your budget holder about how to access funding and any processes you need to follow when choosing or appointing suppliers or agencies.
Start booking facilities and sending briefs to suppliers as soon as you can. Don’t wait until you’ve finalised your plans and recruited research participants or it may be too late to make arrangements.
Using appropriate procurement frameworks and call off contracts will make it easier to work with suppliers in an agile way.
Involve your team
Record your plan in a shared document or collaboration tool. Be clear what research questions each round will aim to answer and how it will help the team make decisions.
To help members get the most from your research, involve them in:
- observing research sessions - everyone should observe at least 2 hours of research every 6 weeks
- helping with user research activities (for example, note-taking, pairing on site visits, running workshops)
- making prototypes and other materials - like letters, leaflets or posters
- analysing results
This will help your team stay focused on user needs.
Share your findings
Agree how to feed research findings into your team’s agile tools and practices (like planning and prioritisation meetings, story backlogs, and any other ways that design decisions are made).
Make sure you have space for research on your team wall. Use it to highlight questions the team is exploring and share information about your research activities and findings.
Store your research findings and other research outputs in your team’s collaboration tool or shared folders so it’s easy for everyone to use and share them.
You should also make sure you have regular opportunities at show and tells and other events to share research findings with your team and with wider stakeholders.
Examples and case studies
Read more about choosing the best methods to answer research questions.
You may also find the following guides useful:
Added section on deciding on an approach to recruiting research participants
Added a line about favouring research methods that your team can understand and join in with.
Added guidance on agreeing research questions, identifying participants and mapping out rounds of research.
Guidance first published