Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Analyzing and synthesizing user research data

Analyzing and synthesizing user interview data

It can be tempting to complete a set of interviews or usability tests and think your research project is done. But without a process for systematically reviewing and making sense of the data you've collected, you risk leaving valuable insights on the table. The next step is to zoom out and look at your findings anew through a process called research synthesis.

Synthesis helps us take all of the info we've collected, organize it into patterns and themes, and translate those themes into actionable insights. At the end of this process, you should have answers to the core research questions you set out to answer and evidence that proves or disproves your hypotheses.

Below are some guidelines for how to set yourself up for successful analysis and synthesis before you begin talking with users, while you're conducting research sessions, and after your interviews are complete.

Before interviews: Decide on a collection method

Conducting user research can result in a pretty hefty amount of information. To stay organized throughout this process, spend some time up front deciding where you'll collect your notes. Collect all your research notes for a study into a single Google spreadsheet. Doing this makes it easier for your team to collaborate by adding their own notes and observations, and collecting everything in a central place will keep things organized and consistent.

You should also familiarize yourself with the format of our UXR Insights repo. This will help ensure you've gathered all the information you'll need when it comes time to document your findings there.

Here are some templates you can use, depending on the type of study you're conducting:

During interviews: Gather data and discuss with your team

While capturing your research data, you'll focus on documenting observations (what you saw the user do, or what problems you saw/heard them experience) and quotes (the verbatim of what the user actually said, in quotation marks). You may also want to make notes on early interpretations (what you believe something a user said or did means) and possible solutions (concrete ways to solve the problems identified).

While the bulk of research synthesis happens after you've finished gathering all your data, analysis can start right away. After every user interview, de-brief with your teammates who observed the session about what stood out.

Capturing these insights while the session is fresh in your minds makes the overall process much faster and easier. Discussing observations as a group also leads to more thoughtful analysis, reduces cognitive bias, and helps your team form a strong shared understanding of the problem space you're investigating.

After interviews: Find patterns and themes

Synthesizing user interview data

Affinity diagramming is a way of finding themes in a collection of ideas, quotes, or observations. This method helps you draw out insights from qualitative data quickly and collaboratively. This is traditionally done in person with Post-It notes on a large blank wall or whiteboard. At GitLab, we use a tool called MURAL to recreate this experience remotely.

1. Prep your notes

Spend some time cleaning up and organizing your notes before moving them into MURAL. How you organize your notes in MURAL is up to you and your project goals. Some teams will start by organizing their notes by user, or by interview questions.

Next, copy and paste your notes into MURAL. Each cell in your notes spreadsheet should paste into MURAL as a separate sticky note.

2. Cluster the data into themes

Once all your individual data points are in MURAL, begin by grouping similar stickies together. You may want to start by grouping stickies for themes that stood out to you from your post-session debriefs, then move to surfacing themes that may not have been as obvious the first time around.

Here are some potential ways to group findings:

This process might feel messy, especially if it's your first time doing an affinity diagram. To add more structure to the process, use your original project goals, hypotheses, and research questions as a guide during synthesis. You can copy these right into your MURAL board so you can keep them top-of-mind while you group individual findings into broader themes. You might also reference the questions listed in this article to ask yourself and your team throughout the synthesis process.

As your groupings start to come together, use a text heading to write titles or catch phrases that summarize each cluster of similar stickies.

3. Discuss and revise as needed

Organize and reorganize your findings into meaningful categories until everyone seems to be in agreement. See if you need to adjust any of your themes before moving onto the next step.

This is also a good opportunity to check for possible bias. Try “arguing the other side.” In other words, building a case—from your research—against your key insights, to see if they still stand up.

4. Distill findings into insights

Once you're happy with your groupings, distill your findings into a manageable number of insight statements. Insights you uncover should come from multiple sources in your research. Depending how much research you did, the number of insights you uncover may vary.

Once your synthesis is complete, document your research findings in the UXR_Insights repo.