Skip to content
A picture of Rachael
Rachael
User researcher

6 min read

Follow Paper on LinkedIn

Module 5: Analysing research findings

These training resources accompany our 2-day practical training course, Learn to do user research.

The course includes conversations and activities to help you apply everything you learn and an opportunity to get feedback from our experienced user researchers. It will give you all the skills you need to start or develop your career as a user researcher.

See more details and sign up for Learn to do user research.

This module is the 5th of 6 modules in Learn to do user research

  1. Framing the right research problem
  2. Planning and designing user research
  3. Recruiting research participants in a mindful and ethical way
  4. Facilitating and observing user research
  5. Analysing research findings
  6. Turning research findings into persuasive and usable outputs

By the end of this module you’ll be able to

  • break down raw research data into clear themes and key findings
  • plan and facilitate effective, efficient group analysis that avoids bias

Note: This module is the most practical of the course, so you’ll learn lots more about clustering insights, defining themes, and running analysis when you take the training. For this article, we’ll focus on planning and preparing for a round of collaborative user research analysis.


Research analysis – What it is and why it matters

The terms analysis and synthesis are often used interchangeably by user researchers to refer to this stage of your research. Whichever term you use, there are 2 important parts to it:

  1. Gathering all your data together to look for meaningful patterns, themes and insights in it – this can be called thematic analysis, affinity mapping or clustering
  2. Deciding the best way to present those themes and insights as outputs

We’ll practise doing both these activities on the Learn to do user research course.

Research analysis is asking “what does this all mean?”. It’s useful because it helps you:

  • prevent impulsive reactions based on one session
  • make informed decisions
  • see what’s wrong (but not necessarily how to fix it)
  • see all the ways in which something is a problem

What analysis is not

Analysis can seem like it’s all about large amounts of data and complex looking analysis boards. It isn’t.

Analysis starts when you first observe something and continues into your debrief sessions, your conversations with colleagues, the time spent reading transcripts and everything that follows.

Analysis isn’t something you do once and it’s finished, it’s about spending time with the data and looking at it from different perspectives.

When to do research analysis and how much time to spend on it

You don’t want to leave analysis until the end of your research project. If you’re working in sprints* we’d suggest an analysis session for every sprint of research. Working iteratively like this is key to keeping a fresh mind for analysis, and means you can add clarifying questions to future sprints of research if you need to.

*A sprint is a chunk of time, often 2 weeks but it’s different for different teams, where you plan, do and review a set of tasks towards an agreed goal.

When you’re doing analysis with other people, you’ll need to block out at least 2 hours of calendar time for analysis. Big chunks of time work better for analysis sessions because it can take a while to get into the right frame of mind for it, and it’s impossible if you’re context switching between analysis and other tasks.

It’s usually helpful to book this time before you’ve even done the research, for 2 reasons:

  • Because otherwise it can be difficult to find a time when a group of people are all available.
  • Because analysis is a step that’s often overlooked by stakeholders – you’ve done the research and now they expect you to tell them what needs to happen. Planning time for it in advance goes some way to setting stakeholders’ expectations about what needs to happen between doing the research and being able to provide a team with some clear guidance on what to do next.

Who to involve in research analysis

Invite anyone who has observed the research to an analysis session as they’ll be able to contribute to the discussion.

If you have people in your team or stakeholders outside your team who so far haven’t engaged with the research by observing a session, be cautious about how you might include them.

Also, be mindful about inviting non-researchers into what can sometimes be quite an intimidating space.

How to use your research data in analysis

You need to decide how to get your data from transcripts into snippets that you can move around and group. This usually involves copying out quotes onto (real or virtual) post-it notes.

If possible, it’s best to get the people who are doing the analysis to share the job of copying out the quotes. This way they’ll get more familiar with the data.

The more time you spend with your data, the more you get from it, so if it helps you could think of this as the first part of analysis.

Try not to fret too much about which information is useful from the interview. Have in the back of your mind the question “Could this piece of data help us solve the problem we set out to solve?” If it feels like it could, take it over to your analysis space. If it doesn’t, leave it for now. Just remember to check your biases as you’re doing this.

You’ll almost definitely end up with quotes that you thought were going to be useful but aren’t and you’ll probably skip over something in the transcript that you then think about in analysis and go back to get.

All of this is fine. You’re just trying to make this big piece of data slightly more manageable.

What to do with ideas that come up in analysis

While you’re going through the data it’s natural for people to:

  • have ideas about how to solve problems
  • spot opportunities to dig deeper into issues with further research

While this can feel exciting and you’ll want to keep hold of these ideas, you don’t want to spend time thinking about them at this stage. Focusing on solutions too early will bias your analysis and thinking about future work will distract you from the task at hand.

It can be useful to set up a couple of ‘parking lot’ spaces, one for noting down ideas for solutions and one where you can pop questions for future research.


Next module →

Go to Module 6: Turning research findings into persuasive and usable outputs.

Sign up for ‘Learn to do user research’

Our 2-day practical training course, Learn to do user research, gives you a complete foundation in key user research skills.

Join experienced user researchers at Paper to learn key skills and put them into practice, with lots of opportunity for questions and feedback.

See dates and sign up