Quantifying the value of User Research in 2024 

In today's fast-paced product development landscape, the ability to quickly gather and act on user insights is more critical than ever. While dedicated UX researchers play a crucial role, there's a growing trend towards democratizing UX research – empowering team members across various functions to contribute to and benefit from user insights. Let's explore how this approach can transform your organization's approach to user-centered design.

‍

Benefits of a democratized UXR approach

‍

Democratizing UX research is a transformative approach that empowers organizations to unlock the full potential of user insights. By breaking down traditional barriers and involving a broader range of team members in the research process, companies can foster a culture of user-centricity, accelerate decision-making, and drive innovation. This inclusive strategy not only enhances the depth and breadth of user understanding but also aligns diverse perspectives to create more impactful, user-friendly products and services. Here are a few of the benefits of this movement:

‍

Increased research velocity

‍

By enabling more team members to conduct basic research, organizations can gather insights more frequently and rapidly. This means that instead of waiting for dedicated UX researchers to be available, product managers, designers, or marketers can quickly run simple surveys or usability tests. For example, a product manager could use a user-friendly tool to get quick feedback on a new feature idea, allowing the team to iterate faster. This increased velocity helps organizations stay agile and responsive to user needs in a fast-paced market.

‍

Broader perspective

‍

Cross-functional participation brings diverse viewpoints to research, potentially uncovering insights that might be missed by specialized researchers alone. A developer might ask questions from a technical feasibility standpoint, while a marketer might focus on brand perception. This diversity in approach can lead to richer, more comprehensive insights. For instance, during a user interview, a sales team member might pick up on specific pain points related to competitor products that a UX researcher might not have thought to explore.

‍

Enhanced user-centricity

‍

When more team members engage directly with users, it fosters a culture of user-centricity across the organization. This direct exposure to user feedback and behaviors helps all team members develop empathy for the user. As a result, user needs and preferences become a central consideration in all decision-making processes, not just in UX design. For example, seeing users struggle with a feature firsthand might motivate a developer to champion user-friendly improvements in future sprints.

‍

Improved research adoption

‍

Team members who participate in research are more likely to understand and act on the insights generated. When people are involved in gathering data, they have a deeper understanding of the context and nuances of the findings. This personal investment leads to greater buy-in and increases the likelihood that research insights will be applied in practical ways. For instance, a product manager who conducts user interviews is more likely to prioritize features based on actual user needs rather than assumptions.

‍

Resource optimization

‍

Democratization allows dedicated researchers to focus on more complex, high-value research initiatives. By offloading simpler research tasks to other team members, professional UX researchers can dedicate their expertise to more challenging projects, such as longitudinal studies, complex usability evaluations, or strategic research initiatives. This optimization ensures that specialized skills are applied where they can have the most significant impact.

‍

Our survey revealed that organizations with a more democratized approach to UXR tend to have higher levels of research maturity and integration into product development processes. This correlation suggests that democratization not only increases the quantity of research conducted but also enhances its quality and impact. Organizations that empower cross-functional teams to participate in UXR often develop more sophisticated research practices over time.

‍

For example, these organizations might:

‍

• Have better-defined research processes and guidelines
• Integrate user insights more consistently into decision-making at all levels
• Develop more advanced metrics for measuring the impact of UXR
• Foster a culture where challenging assumptions with user data is the norm
• Create more opportunities for collaboration between different departments around user insights

‍

By democratizing UXR, organizations can create a virtuous cycle where increased participation leads to better research practices, which in turn drives more value from UXR activities. This approach helps to embed user-centricity deeply into the organizational culture, leading to better products and services that truly meet user needs.

‍

Strategies for upskilling people who do research (PWDRs)

‍

To successfully democratize UXR, it's crucial to provide proper training and support:

‍

1. UXR basics workshops

Offer regular training sessions on fundamental research methods and best practices. These workshops should cover a range of topics, including:

‍

• Introduction to user research methodologies (e.g., interviews, surveys, usability testing)
• Basics of research design and planning
• Participant recruitment strategies
• Data analysis techniques
• Ethical considerations in user research

‍

For example, a monthly "UXR 101" workshop could be organized, where different aspects of UX research are covered in depth. These sessions could be led by experienced researchers and include practical exercises to reinforce learning.

‍

Check out our 101 Guides

‍

2. Mentorship programs

‍

Pair non-researchers with experienced UX researchers for guidance and support. This one-on-one relationship allows for personalized learning and hands-on guidance. 

‍

Mentors can:

• Provide feedback on research plans
• Offer advice on challenging research scenarios
• Share best practices and personal experiences
• Help mentees navigate the complexities of user research in their specific organizational context

‍

A formal mentorship program could be established with clear goals, regular check-ins, and a defined duration (e.g., 6 months), after which mentees could become mentors themselves, scaling the program.

‍

3. Research playbooks

‍

Develop standardized templates and guidelines for common research activities. These playbooks serve as go-to resources for non-researchers, ensuring consistency and quality across studies. 

‍

They might include:

‍

• Step-by-step guides for different research methods
• Templates for research plans, screeners, and report structures
• Best practices for participant interaction
• Guidelines for data privacy and ethical considerations
• Tips for presenting and socializing research findings

‍

For instance, a "Usability Testing Playbook" could walk a product manager through the entire process of planning, conducting, and reporting on a usability test.

‍

Check out Optimal Playbooks

‍

4. Collaborative research

‍

Involve non-researchers in studies led by experienced UX professionals to provide hands-on learning opportunities.

‍

This approach allows non-researchers to:

‍

• Observe best practices in action
• Contribute to real research projects
• Understand the nuances and challenges of UX research
• Build confidence in their research skills under expert guidance

‍

For example, a designer could assist in a series of user interviews, gradually taking on more responsibility with each session under the researcher's supervision.

‍

5. Continuous learning resources

‍

Provide access to online courses, webinars, and industry events to foster ongoing skill development. This could include:

‍

• Subscriptions to UX research platforms and tools
• Access to online course libraries (e.g., Coursera, LinkedIn Learning)
• Budget for attending UX conferences and workshops
• Internal knowledge sharing sessions where team members present on recent learnings or projects

‍

An internal UX research resource hub could be created, curating relevant articles, videos, and courses for easy access by team members.

‍

As one UX leader in our study noted, "It's been exciting to see [UXR] evolve as a discipline and see where it is today, and to see the various backgrounds and research specialisms that [user] researchers have today is not something I'd have expected."

‍

This quote highlights the dynamic nature of UX research and the diversity it now encompasses. The field has evolved to welcome practitioners from various backgrounds, each bringing unique perspectives and skills. This diversity enriches the discipline and makes it more adaptable to different organizational contexts.

‍

For example:

‍

• A former teacher might excel at educational research for EdTech products
• A psychologist could bring deep insights into user behavior and motivation
• A data scientist might introduce advanced analytical techniques to UX research

‍

By embracing this diversity and providing comprehensive support for skill development, organizations can create a rich ecosystem of UX research capabilities. This not only democratizes the practice but also elevates its overall quality and impact.

‍

The key to successful democratization lies in balancing accessibility with rigor. While making UX research more widely practiced, it's crucial to maintain high standards and ethical practices. The strategies outlined above help achieve this balance by providing structure, guidance, and ongoing support to those new to UX research, while leveraging the expertise of experienced researchers to ensure quality and depth in the organization's overall research efforts.

‍

Tools and platforms enabling broader participation

‍

The democratization of UXR has been greatly facilitated by comprehensive, user-friendly research platforms like Optimal Workshop. Our all-in-one solution offers a suite of tools designed to empower both seasoned researchers and non-researchers alike:

‍

Surveys

‍

Our intuitive survey creation tool allows anyone in your organization to quickly design and distribute surveys. With customizable templates and an easy-to-use interface, gathering user feedback has never been simpler.

‍

Tree Testing and Card Sorting

‍

These powerful tools simplify the process of conducting information architecture and card sorting studies. Non-researchers can easily set up and run tests to validate navigation structures and content organization.

‍

Qualitative Insights

‍

Our powerful qualitative analysis tool enables team members across your organization to efficiently analyze and synthesize user interview data. With its user-friendly interface, our Qualitative Insights tool makes deriving meaningful insights from qualitative research accessible to researchers and non-researchers alike.

‍

First-click Testing

This easy-to-use first-click testing tool empowers anyone in your team to quickly set up and run tests to evaluate the effectiveness of their designs. First-click Testing simplifies the process of gathering initial user impressions, allowing for rapid iteration and improvement of user interfaces.

‍

These tools, integrated into a single, user-friendly platform, make it possible for non-researchers to conduct basic studies and contribute to the overall research effort without extensive training. The intuitive design of the Optimal Workshop UXR and insights platform ensures that team members across different functions can easily engage in user research activities, from planning and execution to analysis and sharing of insights.

‍

By providing a comprehensive, accessible platform, Optimal Workshop plays a crucial role in democratizing UX research, enabling organizations to build a more user-centric culture and make data-driven decisions at all levels.

‍

Balancing democratization with expertise

‍

While democratizing UXR offers numerous benefits, it's crucial to strike a balance with professional expertise. This balance involves establishing quality control measures, reserving complex research initiatives for trained professionals, maintaining strategic oversight by experienced researchers, providing clear guidelines on research ethics and data privacy, and leveraging dedicated researchers' expertise for insight synthesis. 

‍

Our survey revealed that organizations successfully balancing democratization with expertise tend to see the highest impact from their UXR efforts. The goal of democratization is not to replace dedicated researchers but to expand the organization's capacity for generating user insights. By empowering cross-functional teams to participate in UXR, companies can foster a more user-centric culture, increase the velocity of insight generation, and ultimately create products that better meet user needs. 

‍

As we look to the future, the trend towards democratization is likely to continue, and organizations that can effectively balance broad participation with professional expertise will be best positioned to thrive in an increasingly user-centric business landscape.

‍

Ready to democratize your UX research? Optimal Workshop's platform empowers your entire team to contribute to user insights while maintaining professional quality. Our intuitive tools accelerate research velocity and foster a user-centric culture. 

‍

Start your free trial today and transform your UXR practice. 

‍

Simply put, ResearchOps is about making sure your research operations are robust, thought through and managed. 

‍

Having systems and processes around your UX research and your team keep everyone (and everything) organized. Making user research projects quicker to get started and more streamlined to run. And robust sharing, socializing, and knowledge storage means that everyone can understand the research insights and findings and put these to use - across the organization. And even better, find these when they need them. 

‍

Using the same tools across the team allows the research team to learn from each other, and previous research projects and be able to compare apples with apples, with everyone included. Bringing the team together across tools, research and results.

‍

We go into more detail in our ebook ResearchOps Checklist about exactly what you can do to make sure your research team is running at its best. Let’s take a quick look at 5 way to ensure you have the grounding for a successful ResearchOps team.

‍

1. Knowledge management 📚

‍

What do you do with all of the insights and findings of a user research project? How do you store them, how do you manage the insights, and how do you share and socialize?

‍

Having processes in place that manage this knowledge is important to the longevity of your research. From filing to sharing across platforms, it all needs to be standardized so everyone can search, find and share.

‍

2. Guidelines and process templates 📝

‍

Providing a framework for how to run research projects is are important. Building on the knowledge base from previous research can improve research efficiencies and cut down on groundwork and administration. Making research projects quicker and more streamlined to get underway.

‍

3. Governance 🏛

‍

User research is all about people, real people. It is incredibly important that any research be legal, safe, and ethical. Having effective governance covered is vital.

‍

4. Tool stack 🛠

‍

Every research team needs a ‘toolbox’ that they can use whenever they need to run card sorts, tree tests, usability tests, user interviews, and more. But which software and tools to use?

‍

Making sure that the team is using the same tools also helps with future research projects, learning from previous projects, and ensuring that the information is owned and run by the organization (rather than whichever individuals prefer). Reduce logins and password shares, and improve security with organization-wide tools and platforms. 

‍

5. Recruitment 👱🏻👩👩🏻👧🏽👧🏾

‍

Key to great UX research is the ability to recruit quality participants - fast! Having strong processes in place for screening, scheduling, sampling, incentivizing, and managing participants needs to be top of the list when organizing the team.

‍

Wrap Up 💥

‍

Each of these ResearchOps processes are not independent of the other. And neither do they flow from one to the other. They are part of a total wrap around for the research team, creating processes, systems and tools that are built to serve the team. Allowing them to focus on the job of doing great research and generating insights and findings that develop the very best user experience. 

‍

Afterall, we are creating user experiences that keep our users engaged and coming back. Why not look at the teams user experience and make the most of that. Freeing time and space to socialize and share the findings with the organization. 

In UX research we are told again and again that to ensure truly user-centered design, it’s important to test ideas with real users as early as possible. There are many benefits that come from introducing the voice of the people you are designing for in the early stages of the design process. The more feedback you have to work with, the more you can inform your design to align with real needs and expectations. In turn, this leads to better experiences that are more likely to succeed in the real world.It is not surprising then that paper prototypes have become a popular tool used among researchers. They allow ideas to be tested as they emerge, and can inform initial designs before putting in the hard yards of building the real thing. It would seem that they’re almost a no-brainer for researchers, but just like anything out there, along with all the praise, they have also received a fair share of criticism, so let’s explore paper prototypes a little further.

‍

What’s a paper prototype anyway? 🧐📖

‍

Paper prototyping is a simple usability testing technique designed to test interfaces quickly and cheaply. A paper prototype is nothing more than a visual representation of what an interface could look like on a piece of paper (or even a whiteboard or chalkboard). Unlike high-fidelity prototypes that allow for digital interactions to take place, paper prototypes are considered to be low-fidelity, in that they don’t allow direct user interaction. They can also range in sophistication, from a simple sketch using a pen and paper to simulate an interface, through to using designing or publishing software to create a more polished experience with additional visual elements.

‍

‍

‍

Showing a research participant a paper prototype is far from the real deal, but it can provide useful insights into how users may expect to interact with specific features and what makes sense to them from a basic, user-centered perspective. There are some mixed attitudes towards paper prototypes among the UX community, so before we make any distinct judgements, let's weigh up their pros and cons.

‍

Advantages 🏆

‍

• They’re cheap and fastPen and paper, a basic word document, Photoshop. With a paper prototype, you can take an idea and transform it into a low-fidelity (but workable) testing solution very quickly, without having to write code or use sophisticated tools. This is especially beneficial to researchers who work with tight budgets, and don’t have the time or resources to design an elaborate user testing plan.
• Anyone can do itPaper prototypes allow you to test designs without having to involve multiple roles in building them. Developers can take a back seat as you test initial ideas, before any code work begins.
• They encourage creativityFrom both the product teams participating in their design, but also from the users. They require the user to employ their imagination, and give them the opportunity express their thoughts and ideas on what improvements can be made. Because they look unfinished, they naturally invite constructive criticism and feedback.
• They help minimize your chances of failurePaper prototypes and user-centered design go hand in hand. Introducing real people into your design as early as possible can help verify whether you are on the right track, and generate feedback that may give you a good idea of whether your idea is likely to succeed or not.

‍

Disadvantages 😬

‍

• They’re not as polished as interactive prototypesIf executed poorly, paper prototypes can appear unprofessional and haphazard. They lack the richness of an interactive experience, and if our users are not well informed when coming in for a testing session, they may be surprised to be testing digital experiences on pieces of paper.
• The interaction is limitedDigital experiences can contain animations and interactions that can’t be replicated on paper. It can be difficult for a user to fully understand an interface when these elements are absent, and of course, the closer the interaction mimics the final product, the more reliable our findings will be.
• They require facilitationWith an interactive prototype you can assign your user tasks to complete and observe how they interact with the interface. Paper prototypes, however, require continuous guidance from a moderator in communicating next steps and ensuring participants understand the task at hand.
• Their results have to be interpreted carefullyPaper prototypes can’t emulate the final experience entirely. It is important to interpret their findings while keeping their limitations in mind. Although they can help minimize your chances of failure, they can’t guarantee that your final product will be a success. There are factors that determine success that cannot be captured on a piece of paper, and positive feedback at the prototyping stage does not necessarily equate to a well-received product further down the track.

‍

Improving the interface of card sorting, one prototype at a time 💡

‍

We recently embarked on a research project looking at the user interface of our card-sorting tool, OptimalSort. Our research has two main objectives — first of all to benchmark the current experience on laptops and tablets and identify ways in which we can improve the current interface. The second objective is to look at how we can improve the experience of card sorting on a mobile phone.

‍

Rather than replicating the desktop experience on a smaller screen, we want to create an intuitive experience for mobiles, ensuring we maintain the quality of data collected across devices.Our current mobile experience is a scaled down version of the desktop and still has room for improvement, but despite that, 9 per cent of our users utilize the app. We decided to start from the ground up and test an entirely new design using paper prototypes. In the spirit of testing early and often, we decided to jump right into testing sessions with real users. In our first testing sprint, we asked participants to take part in two tasks. The first was to perform an open or closed card sort on a laptop or tablet. The second task involved using paper prototypes to see how people would respond to the same experience on a mobile phone.

‍

‍

Context is everything 🎯

‍

What did we find? In the context of our research project, paper prototypes worked remarkably well. We were somewhat apprehensive at first, trying to figure out the exact flow of the experience and whether the people coming into our office would get it. As it turns out, people are clever, and even those with limited experience using a smartphone were able to navigate and identify areas for improvement just as easily as anyone else. Some participants even said they prefered the experience of testing paper prototypes over a laptop. In an effort to make our prototype-based tasks easy to understand and easy to explain to our participants, we reduced the full card sort to a few key interactions, minimizing the number of branches in the UI flow.

‍

This could explain a preference for the mobile task, where we only asked participants to sort through a handful of cards, as opposed to a whole set.The main thing we found was that no matter how well you plan your test, paper prototypes require you to be flexible in adapting the flow of your session to however your user responds. We accepted that deviating from our original plan was something we had to embrace, and in the end these additional conversations with our participants helped us generate insights above and beyond the basics we aimed to address. We now have a whole range of feedback that we can utilize in making more sophisticated, interactive prototypes.

‍

Whether our success with using paper prototypes was determined by the specific setup of our testing sessions, or simply by their pure usefulness as a research technique is hard to tell. By first performing a card sorting task on a laptop or tablet, our participants approached the paper prototype with an understanding of what exactly a card sort required. Therefore there is no guarantee that we would have achieved the same level of success in testing paper prototypes on their own. What this does demonstrate, however, is that paper prototyping is heavily dependent on the context of your assessment.

‍

Final thoughts 💬

‍

Paper prototypes are not guaranteed to work for everybody. If you’re designing an entirely new experience and trying to describe something complex in an abstracted form on paper, people may struggle to comprehend your idea. Even a careful explanation doesn’t guarantee that it will be fully understood by the user. Should this stop you from testing out the usefulness of paper prototypes in the context of your project? Absolutely not.

‍

In a perfect world we’d test high fidelity interactive prototypes that resemble the real deal as closely as possible, every step of the way. However, if we look at testing from a practical perspective, before we can fully test sophisticated designs, paper prototypes provide a great solution for generating initial feedback.In his article criticizing the use of paper prototypes, Jake Knapp makes the point that when we show customers a paper prototype we’re inviting feedback, not reactions. What we found in our research however, was quite the opposite.

‍

In our sessions, participants voiced their expectations and understanding of what actions were possible at each stage, without us having to probe specifically for feedback. Sure we also received general comments on icon or colour preferences, but for the most part our users gave us insights into what they felt throughout the experience, in addition to what they thought.

‍

Further reading 🧠

‍

• Why You Only Need To Test With 5 Users - Nielsen Norman Group’s Jakob Nielsen explains reveals his thoughts on only using five users when conducting usability testing.
• Sketching for better mobile experiences - Lennart Hennigs explains how to sketch and why you should do it in an article for Smashing Magazine.
• Paper prototypes work as well as software prototypes -  Bob Bailey explains why he thinks paper prototypes are just as good as software prototypes for usability testing.