![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/02\/UX-Research-System-720x481.jpg\" "\\"ux-research-system\\"")
<\/p>\n<\/p>\n
Here\u2019s the thing: the fact that you do UX research is only the first step in creating a bulletproof design method and design team. What needs to come after that, however, is creating a commonly accepted UX research system, where information is stored in a consistent and searchable way.<\/p>\n
In this post, I share with you the story of creating our own UX research system.\u00a0<\/span><\/p>\n A confession: design systems had made me jealous. The idea of the atomic design fascinated me. Having an atomic unit as the foundation, and building something bigger with it forms a perfect analogy for UX research<\/a> as well. But how is this connected to the topic of research systems?<\/span><\/p>\n Let\u2019s take the example of doing a batch of usability tests<\/a>. From my observations on different people, as a UX researcher and part of a research team, I try to form an insight to design better user experience.\u00a0<\/span><\/p>\n Although the journey goes a bit differently, the analogy seems to match.\u00a0<\/span>By adding a UX research system to the method, we aim to scale this up while keeping our research trackable and current.<\/span><\/p>\n Sometimes I feel that building elaborate presentations wastes resources. They usually work great upon presentation but their utility does not last much longer. Backtracking takes effort. <\/span><\/p>\n Also, research reports and presentations contain a lot of information requiring extra time to navigate. So, with the UX research system, we attempt to set up reporting as well avoid making presentations besides the data entry.<\/span><\/p>\n To track all our user research efforts in a consumable way, the basic setup has a kind of archive. While sounding not very exciting, it may prove very useful in the long run. <\/span><\/p>\n It begins with properly storing the information and setting a reference point. But it certainly needs more. In the end, a folder with all the research counts as a kind of research management too, just not a very effective one.<\/span><\/p>\n An open and accessible UX research system helps get everyone on board, communicating our findings clearly. Basically, understanding user research. Dedicated members can even explore our observations when they get interested in something. <\/span><\/p>\n I<\/span>t can help product managers make strategic decisions, designers plan sprints<\/a> properly or marketers learn more about the target audience. Evidence must form the foundation of our user insights so we can avoid basing decisions on anecdotes and opinions.\u00a0<\/span><\/p>\n Qualitative and quantitative data go together. They have to be communicated together to form the best possible insights. The system should allow us to pair them and build strong, evidence-based insights.<\/span><\/p>\n During different projects, we use many different UX research methods<\/a>, gathering all kinds of data with user interviews, user test etc. In many cases, we observe things about our products we can\u2019t use right away. They may contribute to a bigger insight, idea or a new feature later \u2013 so we might use them then. Maybe we don\u2019t even know the question those observations will answer. <\/span><\/p>\n It might happen that our observations do not determine anything yet, and only additional information will validate them. This doesn\u2019t mean we don\u2019t have clear questions when we start the research; it just means that what seems to be noise at one point can become useful information at another.<\/span><\/p>\n UX research<\/a> is an important part of the Product Design process. Check our e-book how you can implement research in your workflows:\u00a0Product Manager\u2019s Guide to UX Design<\/span><\/a>.<\/p>\n During a project here at UX studio, with a bigger team of researchers collaborating on a project for an airline company, we did multiple usability studies. During this process, we used a simple spreadsheet to store information. <\/span><\/p>\n It turned out well but lacked a few key features to make it scalable in the long run. For example, finding common patterns and themes proved difficult. But it stored qualitative data really well and made it accessible for everyone \u2013 to act as a research repository. This resulted in a presentation for the client.<\/span><\/p>\n While exploring ways to use the atomic principles in research, this <\/span>article by Tomer Sharon<\/span><\/a> really opened my eyes and truly inspired the effort to start using some kind of research system. <\/span><\/p>\n We had had the foundation on a small scale, however, this article framed the whole problem really well and gave an idea on how to take it to the next level. Every issue we had faced up to that point \u2013 envying the atomic design, storing the data, working together with other researchers \u2013 fell into place. <\/span><\/p>\n I then experimented with a lot of tools, going from academic to product-oriented approaches. Eventually, we stuck with <\/span>Airtable<\/span>: flexible, reasonably priced and customizable enough while easy enough for everyone to use. My other favorites include <\/span>NomNom<\/span>, <\/span>Aurelius<\/span> and <\/span>Mosaiq<\/span>.<\/span><\/p>\n Airtable looks like a spreadsheet but also has the attributes of a simple database, and most importantly, its observations and insights. <\/span><\/p>\n In the observations<\/em>, we keep everything bite-sized and objective. These are the building blocks of our system. Hard evidence (video, audio, text) supports all the observations \u2013 no reports, no anecdotes, no legends and no exceptions.<\/span><\/p>\n Insights<\/em> represent a synthesis of all the things we learned. Being based on multiple observations, they are absorbed easily. Observations and evidence always link to the insights for more detailed information.\u00a0A lot of other data comes with every insight, enabling us to slice and dice the data later and have research management in the long run.<\/span><\/p>\n We built a common UX research system\u00a0template<\/a> based on our previous experience, which is public and open<\/span>\u00a0in the Airtable universe. Feel free to play around with it, make it yours and use it on projects. Make sure to let us know if you managed to make use of it!<\/span><\/p>\n It takes more time on the first couple of occasions to enter every observation into the system. This can take time and patience in the beginning but we are working on it. <\/span><\/p>\n UX still partly concerns politics. No amount of administration work will make people come to this system in more rigid environments. In any case, it can at least act as an objective reference point. <\/span><\/p>\n The team has to settle on what counts as an observation. Right now, we are trying to break it up for consumable information that can be kept simple and objective.<\/span> Tags are always growing over time as we work together on multiple research projects. A proper taxonomy in the beginning must address this to avoid later miscommunication and to keep observations searchable.<\/span><\/p>\n Once you have set up your own system, promote it during projects and show your clients its benefits. Include as many people as possible. Having the other departments on your side also helps a lot. I<\/span>magine people from marketing or customer service able to use this tool properly. If someone else has data of value, they can include it as well to refresh and enlarge the system.<\/span><\/p>\n We just started this initiative on some of our projects here at UXstudio<\/a>. We have to follow up on its effectiveness for now and in the long run. In the worst case scenario, it functions great storing our findings and tracking our research efforts. <\/span><\/p>\n It can develop into much more than that! It simplifies finding new features, answering recurring questions and identifying knowledge gaps. Even with a fully implemented UX research system, challenges might still arise when implementing it throughout the whole organization.<\/span><\/p>\n We have multiple clients, from huge organizations to smaller startups. At the beginning, I thought that this kind of UX research system would only benefit a bigger organization doing a lot of research. But one day, I had an \u201caha\u201d moment when we were catching up with our product team. <\/span><\/p>\n We are developing our own product to help UX people showcase their work. Our product team had reached a crossroad regarding a feature related to templates, and everybody knew they had made some good research insights for it a few months back. But the team members interpreted them differently and couldn\u2019t find the original source. They couldn\u2019t reach an agreement. We then introduced the system to this project, and we think it will hold out over the long run as well. <\/span><\/p>\n Every UX project can benefit from using the system. It just depends on what kind of mindset and goals you have for the project.\u00a0<\/span><\/p>\n Here at UXstudio<\/a>, we are constantly aiming to improve our processes, including our UX research system. It is not yet perfect, however, what we think is important is to keep on improving existing solutions, while making sure that the whole team is on board and is using the research system in a consistent way. As said above, once it’s implemented, it becomes easier to deal with the rest of the challenges.<\/p>\n As we are still working on ours, we would be happy to hear about your UX research system? Any war-tested tricks and shortcuts? Or, want to let us know if you found our research system template<\/a> useful? Please leave comments below!<\/p>\n UX studio has successfully worked with over 250 companies worldwide.<\/p>\n\n
From atomic research to a UX research system<\/h2>\n
![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/02\/UX-Research-System-Atom-720x504.jpg\" "\\"ux-research-system-atom\\"")
<\/p>\nWhy do you need a UX research system?<\/span><\/h2>\n
1. For UX research management<\/b><\/h3>\n
![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/02\/UX-Research-System_Old-Data-Storage-720x470.jpg\" "\\"ux-research-system-old-data\\"")
2. To make UX research more open and collaborative<\/b><\/h3>\n
3. Getting the bigger picture<\/b><\/h3>\n
Our path to our UX research system<\/span><\/h2>\n
How did we get started?<\/b><\/h3>\n
![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/02\/UX-Research-System_Spreadsheet-720x360.png\" "\\"ux-research-system-spreadsheet\\"")
What examples of UX research systems did we have?<\/b><\/h3>\n
How does our UX research system work? + Template<\/b><\/h2>\n
![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/02\/UX-Research-System_Airtable-Observations-720x387.png\" "\\"ux-research-system-observations\\"")
<\/div>\n![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/02\/UX-Research-System_Airtable-Browsing-Insights.gif\" "\\"ux-research-system-airtable-insights\\"")
What are the challenges of a UX research system?<\/span><\/h2>\n
Starting takes effort.<\/b><\/h3>\n
It still has a learning curve.<\/b><\/h3>\n
Definitions, categorization and taxonomy can prove tricky.<\/b><\/h3>\n
![\"UX](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/02\/UX-Research-System_Tagging-720x476.png\" "\\"ux-research-system-tagging\\"")
How to move forward with a UX research system<\/span><\/h2>\n
1. Take everyone on board.<\/b><\/h3>\n
2. Take time to follow up.<\/b><\/h3>\n
3. Use it in different contexts.<\/b><\/h3>\n
Closing thoughts on our UX research system<\/h2>\n
Searching for the right UX agency?<\/b><\/h2>\n