Name your groups 

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:

  • photo rules and requirements 
  • using a photo booth or store photographer 
  • taking a photo at home 
  • reasons a photo might be rejected. 

Determine findings 

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:

  • ‘the legal declaration is threatening and difficult to understand’
  • ‘people think they can click the progress bar to navigate’ 
  • ‘users are confused about what they need to do because so many questions are optional’.

Confirm the actions 

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:

  • new design ideas to work on 
  • new questions to include in user research 
  • things you want to change in a prototype and test in another research session 
  • new user stories to add to the product backlog 
  • new details you need to add to an existing story 
  • strategic insights you can use to develop your user needs, proposition or product roadmap. 

Share your findings 

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. 

Next page: Understanding diversity

Next page: Live stage: improving the service

Next page: How to upskill a team

Own the whole user experience

Using a consent form in an interview 

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 with the participant 

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. 

Managing digital investments across the project lifecycle.

Incentives and consent forms

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.

Keep personal information secure

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. 

Help people to share their story widely 

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. 

Next page: Paying incentives for user research

It’s a good idea to create a panel of participants you can reach out to for future research.  

How to write a recruitment brief 

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:

  • research dates and locations
  • time and length of each session 
  • amount sessions you wish to do on each date 
  • recruitment criteria describing who you will include
  • the number of participants you want to recruit 
  • accessibility and inclusivity guidelines 
  • ethical guidelines, policies and procedures 
  • cash incentives to be handled by the agency.

When you create your brief, make it clear that you welcome participants with diverse needs and all levels of digital literacy.  

Create or review the participant screener 

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.

Make your research inclusive 

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:  

  • the type of activity or the tools used to complete it  
  • the time or day you schedule sessions 
  • the location of the user research 
  • the method you use to recruit your users.  

Next page: Interviewing users

Learn how Australian Government is committed to protecting your digital wellbeing and get the latest information on privacy, security and fraud protection.

Next page: Alpha stage: testing hypotheses

Next page: Planning user research

Number of participants

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:

  • family members who help each other 
  • members of a team who work together.

Interview length  

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.

Location for research  

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:  

  • a home or workplace 
  • over the phone 
  • a research studio 
  • a cafe 
  • a public library.  

Recruit research participants 

There are different ways to find people to participate in user research. Include current and future users of the service you’re researching.

Prepare consent forms 

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. 

Connect with the digital community

Share, build or learn digital experience and skills with training and events, and collaborate with peers across government.