Cases, lifehacks, and stories to make tech community tasks and projects a bit easier.😉
My name is Valeria, and I'm a data keeper in the Parimatch Tech User Research team. When the UX Research team was first set up, we had problems structuring and storing the data we were collecting. It only got worse over time: sharing insights with colleagues was inconvenient, and people kept losing research results on different Google drives.
Fortunately, we found a solution — UX Research Repository. This article explores why a product company needs a UX Research Repository, the issues it solves, and how to create your own repository in Dovetail.
Let’s use our experience as an example. Our UX Research team interviews users from different clusters about their issues or difficulties when interacting with the Parimatch platform. We also collect opinions on our latest innovations, test new features and services, and so on.
Live feedback from the interviews enables us to reach conclusions, formulate hypotheses, carry out A/B testing, and release features to production.
To gain in-depth insights from your data, you need to store it somewhere, structure it, and develop it further. You also need easy access to your insights for you and your colleagues from other departments. Distributing insights is critical: you may have crucial information, but it’s no use to anyone unless you can share it properly.
In the beginning, we stored everything in files and tables on Google Drive without a system, and it was absolute chaos:
Researchers often needed to print interviews to find intersections of user concerns, so they could physically see, highlight, and capture essential points.
You never lose any ideas, and colleagues also have easy access.
All videos, interviews, and images are stored in one place, enabling everyone to find information easily.
Trace the evolution of research on specific topics.
Business priorities, ideas, and problems may change, but with access to old data, you can always track the evolution or degradation of problematic research.
Reduce repetitive research into the same issues.
Or identify gaps in previous research for future reference.
You're always aware of what other researchers are doing.
In big companies, researchers often waste time, effort, and resources testing the same issues their colleagues are testing in other departments. The UX repository keeps everyone on the same page, aware of what other teams are working on.
We get insights from our interview transcripts, then describe them, corroborate the evidence in user quotes and publish them on the main page. Therefore, the main function of the repository is the orderly storage of information in one place with convenient access for all colleagues.
When choosing a tool, we considered more than ten options.
This list is based only on the personal experience of our team:
Each of these tools has its strengths and weaknesses, but we settled on dovetailapp.com. Let me explain why.
We’ll skip getting to know the interface and move on to filling the repository because the Dovetail team’s tips showed us how everything works far better than we can: https://dovetailapp.com/.
Let's begin from the blank page after login.
First, Dovetail takes you to a home page that you can customize to suit your needs. Here, you can use search blocks, write text descriptions, add cards, and display top insights. This page is like the site's main page – your colleagues will come here first, so you need to set up clear navigation to help everyone find what they are looking for.
To begin with, we recommend highlighting the types of data for combining subsequent projects – these can be different business areas, product divisions by OS type, product names, etc.
Search blocks are suitable for grouping projects, which will automatically group by content type, insights, projects, articles, notes, tags, user quotes, etc. You can add similar research topics and then manually add new projects to the block.
For example, on the home page, in addition to the main business goals, we highlighted a "bank of ideas for product improvement," where researchers wrote down their ideas after surveys and interviews.
For a more compact display, you can minimize or expand the insights panel.
All information about the project is collected here, which gives everyone involved a complete understanding of the work done. As mentioned earlier, you can group projects by type of task or business goals and display them in search blocks on the repository home page. Let's have a quick overview of the kind of information we’re using in our projects.
Organizational information on the project:
Comprehensive information on the project:
After uploading the interviews with transcripts to DATA, we proceed to add tags. Until the interview is fully transcribed, it is difficult to say how many tags will be in the end, so we create them on the fly. Select the quote → click the Find or Create tag → write in the name (for example, "Bug"), and Dovetail will highlight the tag in color. You can then use it again by selecting it from the tag list.
To add external tags to the project, click the Extensions field and check the Extension Tags folder. That's it: external tags have been added and will be displayed along with internal tags. Extension tags are convenient because you won’t need to waste time duplicating the same tags in the future.
INSIGHTS → New insight → Create. In the insight card, you can describe the problem in more detail and attach a screenshot or a quote from the respondent.
Congratulations, you have filled your first research project, and now you can share it with your colleagues. And this is just one of the use cases for Dovetail. In fact, the functionality of the app is wider and has several opportunities for a variety of UX Research activities.
Find out more from the "" demo.
As Parimatch Tech is an international company, we have expanded the storage for partners from different regions of operation. Colleagues from other areas research user experiences in other countries, which helps everyone find common product problems and intersections. Also, if projects are repeated, teams do not waste resources on topics already researched.
Product managers and product designers are now the most frequent users of the UX research repository. We also collect presentations and insights from the Business Intelligence department, which we conveniently organize, store, and redistribute for product tasks. The User Research department can easily add important information, as can Analytics, Support, Products, and anyone else who collects user feedback about the product.
The UX repository makes it easier for colleagues to use research results for product improvements. Insights, feedback, hypotheses, ideas – all in one place and accessible to everyone in the company.
If you intend to create a UX department, you’ll very likely need to create a repository as well, so don’t leave it too late because, if you’ve already collected loads of data, it’ll be difficult to structure everything without considerable losses. And we don’t want you to make the same mistake we did!
So, thanks for your attention and good luck!