Once you’ve sorted your observations, agree on a title that represents the cluster. From there, you can break large groups into smaller themes by matching observations.
For example, if users need to supply a photo to use your service, you might have a ‘photos’ group that could broken down into:
The final part of the analysis is determining what the observations mean. When you agree on what you’ve learned, write it as a finding or insight and add it to the relevant group on your affinity map. Write findings as short statements that summarise what you’ve learned, for example:
Use your findings to make decisions about what to work on or change. This supports the agile method of continuous planning with new facts or requirements. As a group, discuss if there are any actions you want to take. Write these on sticky notes in another colour. Add them to the relevant group on your affinity map.
Actions might include:
Collate your findings so you can share them with the wider team and stakeholders. This is sometimes called a shareback.
You can share insights in different ways. If you've been testing prototypes you might show printouts with comments on sticky notes. If you've only just started, you might read out quotes and observations.
Use an electronic presentation to share your findings or whatever medium suits your team.
You should start interviews with users by explaining the purpose of the research. Show participants the consent form.
Explain that they have a choice about what they wish to consent to. Get permission before starting any form of recording, audio, visual or written.
Sometimes a participant may say something that they don’t feel comfortable sharing. After the interview, ask them again if they are happy for the conversation to be used as part of the research. Make sure they still consent to you using the information.
Leave a copy of the consent form with the participant at the end of the session. This gives them a record of what they have agreed to. It also lets them know how they can withdraw consent if they want to later.
Consent forms and incentive receipts are separate parts of the research process.
Make sure you treat consent as a separate discussion from giving the incentive payment and the receipt, otherwise participants may feel a financial obligation to consent to the research.
There are rules around how the government can use personal information.
You need to make sure the information you collect is secure from misuse or unauthorised access.
It’s important to allow people to protect their privacy. It's also important to help people to share their stories more widely. Many people are very keen for their experiences with governments to be shared with anyone who can help improve them.
It’s a good idea to create a panel of participants you can reach out to for future research.
A recruitment brief is a set of instructions sent to an agency to recruit user research participants.
You should send an agency a written brief, even if they’re happy to take instructions over the phone. This will act as a record to look back on if there's problems with the recruitment.
Include in the brief:
When you create your brief, make it clear that you welcome participants with diverse needs and all levels of digital literacy.
A recruitment screener is used to interview potential participants and include the correct mix of people in your research. If you're working with a recruitment agency, you need to decide who is responsible for creating the screener.
If the screener is created by the agency make sure it captures what you need. It’s common for there to be misunderstandings.
To make your research inclusive, anticipate barriers for your users and find ways to overcome them. You can overcome barriers by hosting sessions across different times, days or locations. You can also provide multiple research activities and options.
Barriers to your research can include:
You will typically interview 1 participant at a time. However, if you’re interviewing people that use a service together, it may be helpful to speak to them as a pair or in a small group.
For example, you might interview:
Interviews usually take between 30 minutes and 2 hours. The length depends on the complexity of the subject and the number of questions you have.
Longer interviews will give you more detail, but they may make it harder to recruit participants. For long interviews, plan breaks to avoid fatigue or consider splitting the session.
Interviews can take place almost anywhere. You should make sure the participants can access the location. They may need to know how to contact you for entry to the building or use a lift rather than stairs.
Example interview locations:
There are different ways to find people to participate in user research. Include current and future users of the service you’re researching.
Before your interview goes ahead, make sure you have informed consent from the participants
Think about whether you need to record the session. If you do, make sure the consent forms cover the recording.