March 12, 2025
2

Efficient Research: Maximizing the ROI of Understanding Your Customers

Header graphic for the article 'Efficient Research: Maximizing the ROI of Understanding Your Customers'

Introduction

User research is invaluable, but in fast-paced environments, researchers often struggle with tight deadlines, limited resources, and the need to prove their impact. In our recent UX Insider webinar, Weidan Li, Senior UX Researcher at Seek, shared insights on Efficient Research—an approach that optimizes Speed, Quality, and Impact to maximize the return on investment (ROI) of understanding customers.

At the heart of this approach is the Efficient Research Framework, which balances these three critical factors:

  • Speed – Conducting research quickly without sacrificing key insights.
  • Quality – Ensuring rigor and reliability in findings.
  • Impact – Making sure research leads to meaningful business and product changes.

Within this framework, Weidan outlined nine tactics that help UX researchers work more effectively. Let’s dive in.

1. Time Allocation: Invest in What Matters Most

Not all research requires the same level of depth. Efficient researchers prioritize their time by categorizing projects based on urgency and impact:

  • High-stakes decisions (e.g., launching a new product) require deep research.
  • Routine optimizations (e.g., tweaking UI elements) can rely on quick testing methods.
  • Low-impact changes may not need research at all.

By allocating time wisely, researchers can avoid spending weeks on minor issues while ensuring critical decisions are well-informed.

2. Assistance of AI: Let Technology Handle the Heavy Lifting

AI is transforming UX research, enabling faster and more scalable insights. Weidan suggests using AI to:

  • Automate data analysis – AI can quickly analyze survey responses, transcripts, and usability test results.
  • Generate research summaries – Tools like ChatGPT can help synthesize findings into digestible insights.
  • Speed up recruitment – AI-powered platforms can help find and screen participants efficiently.

While AI can’t replace human judgment, it can free up researchers to focus on higher-value tasks like interpreting results and influencing strategy.

3. Collaboration: Make Research a Team Sport

Research has a greater impact when it’s embedded into the product development process. Weidan emphasizes:

  • Co-creating research plans with designers, PMs, and engineers to align on priorities.
  • Involving stakeholders in synthesis sessions so insights don’t sit in a report.
  • Encouraging non-researchers to run lightweight studies, such as A/B tests or quick usability checks.

When research is shared and collaborative, it leads to faster adoption of insights and stronger decision-making.

4. Prioritization: Focus on the Right Questions

With limited resources, researchers must choose their battles wisely. Weidan recommends using a prioritization framework to assess:

  • Business impact – Will this research influence a high-stakes decision?
  • User impact – Does it address a major pain point?
  • Feasibility – Can we conduct this research quickly and effectively?

By filtering out low-priority projects, researchers can avoid research for research’s sake and focus on what truly drives change.

5. Depth of Understanding: Go Beyond Surface-Level Insights

Speed is important, but efficient research isn’t about cutting corners. Weidan stresses that even quick studies should provide a deep understanding of users by:

  • Asking why, not just what – Observing behavior is useful, but uncovering motivations is key.
  • Using triangulation – Combining methods (e.g., usability tests + surveys) to validate findings.
  • Revisiting past research – Leveraging existing insights instead of starting from scratch.

Balancing speed with depth ensures research is not just fast, but meaningful.

6. Anticipation: Stay Ahead of Research Needs

Proactive researchers don’t wait for stakeholders to request studies—they anticipate needs and set up research ahead of time. This means:

  • Building a research roadmap that aligns with upcoming product decisions.
  • Running continuous discovery research so teams have a backlog of insights to pull from.
  • Creating self-serve research repositories where teams can find relevant past studies.

By anticipating research needs, UX teams can reduce last-minute requests and deliver insights exactly when they’re needed.

7. Justification of Methodology: Explain Why Your Approach Works

Stakeholders may question research methods, especially when they seem time-consuming or expensive. Weidan highlights the importance of educating teams on why specific methods are used:

  • Clearly explain why qualitative research is needed when stakeholders push for just numbers.
  • Show real-world examples of how past research has led to business success.
  • Provide a trade-off analysis (e.g., “This method is faster but provides less depth”) to help teams make informed choices.

A well-justified approach ensures research is respected and acted upon.

8. Individual Engagement: Tailor Research Communication to Your Audience

Not all stakeholders consume research the same way. Weidan recommends adapting insights to fit different audiences:

  • Executives – Focus on high-level impact and key takeaways.
  • Product teams – Provide actionable recommendations tied to specific features.
  • Designers & Engineers – Share usability findings with video clips or screenshots.

By delivering insights in the right format, researchers increase the likelihood of stakeholder buy-in and action.

9. Business Actions: Ensure Research Leads to Real Change

The ultimate goal of research is not just understanding users—but driving business decisions. To ensure research leads to action:

  • Follow up on implementation – Track whether teams apply the insights.
  • Tie findings to key metrics – Show how research affects conversion rates, retention, or engagement.
  • Advocate for iterative research – Encourage teams to re-test and refine based on new data.

Research is most valuable when it translates into real business outcomes.

Final Thoughts: Research That Moves the Needle

Efficient research is not just about doing more, faster—it’s about balancing speed, quality, and impact to maximize its influence. Weidan’s nine tactics help UX researchers work smarter by:


✔️  Prioritizing high-impact work
✔️  Leveraging AI and collaboration
✔️  Communicating research in a way that drives action

By adopting these strategies, UX teams can ensure their research is not just insightful, but transformational.

Watch the full webinar here

Share this article
Author
Optimal
Workshop

Related articles

View all blog articles
Learn more
1 min read

5 ways to increase user research in your organization

Co-authored by Brandon Dorn, UX designer at Viget.As user experience designers, making sure that websites and tools are usable is a critical component of our work, and conducting user research enables us to assess whether we’re achieving that goal or not. Even if we want to incorporate research, however, certain constraints may stand in our way.

A few years ago, we realized that we were facing this issue at Viget, a digital design agency, and we decided to make an effort to prioritize user research. Almost two years ago, we shared initial thoughts on our progress in this blog post. We’ve continued to learn and grow as researchers since then and hope that what we’ve learned along the way can help your clients and coworkers understand the value of research and become better practitioners. Below are some of those lessons.

Make research a priority for your organization

Before you can do more research, it needs to be prioritized across your entire organization — not just within your design team. To that end, you should:

  • Know what you’re trying to achieve. By defining specific goals, you can share a clear message with the broader organization about what you’re after, how you can achieve those goals, and how you will measure success. At Viget, we shared our research goals with everyone at the company. In addition, we talked to the business development and project management teams in more depth about specific ways that they could help us achieve our goals, since they have the greatest impact on our ability to do more research.
  • Track your progress. Once you’ve made research a priority, make sure to review your goals on an ongoing basis to ensure that you’re making progress and share your findings with the organization. Six months after the research group at Viget started working on our goals, we held a retrospective to figure out what was working — and what wasn’t.
  • Adjust your approach as needed. You won’t achieve your goals overnight. As you put different tactics into action, adjust your approach if something isn’t helping you achieve your goals. Be willing to experiment and don’t feel bad if a specific tactic isn’t successful.

Educate your colleagues and clients

If you want people within your organization to get excited about doing more research, they need to understand what research means. To educate your colleagues and clients, you should:

  • Explain the fundamentals of research. If someone has not conducted research before, they may not be familiar or feel comfortable with the vernacular. Provide an overview of the fundamental terminology to establish a basic level of understanding. In a blog post, Speaking the Same Language About Research, we outline how we established a common vocabulary at Viget.
  • Help others understand the landscape of research methods. As designers, we feel comfortable talking about different methodologies and forget that that information will be new to many people. Look for opportunities to increase understanding by sharing your knowledge. At Viget, we make this happen in several ways. Internally, we give presentations to the company, organize group viewing sessions for webinars about user research, and lead focused workshops to help people put new skills into practice. Externally, we talk about our services and share knowledge through our blog posts. We are even hosting a webinar about conducting user interviews in November and we'd love for you to join us.
  • Incorporate others into the research process. Don't just tell people what research is and why it's important — show them. Look for opportunities to bring more people into the research process. Invite people to observe sessions so they can experience research firsthand or have them take on the role of the notetaker. Another simple way to make people feel involved is to share findings on an ongoing basis rather than providing a report at the end of the process.

Broaden your perspective while refining your skill set

Our commitment to testing assumptions led us to challenge ourselves to do research on every project. While we're dogmatic about this goal, we're decidedly un-dogmatic about the form our research takes from one project to another. To pursue this goal, we seek to:

  • Expand our understanding. To instill a culture of research at Viget, we've found it necessary to question our assumptions about what research looks like. Books like Erika Hall’s Just Enough Research teach us the range of possible approaches for getting useful user input at any stage of a project, and at any scale. Reflect on any methodological biases that have become well-worn paths in your approach to research. Maybe your organization is meticulous about metrics and quantitative data, and could benefit from a series of qualitative studies. Maybe you have plenty of anecdotal and qualitative evidence about your product that could be better grounded in objective analysis. Aim to establish a balanced perspective on your product through a diverse set of research lenses, filling in gaps as you learn about new approaches.
  • Adjust our approach to project constraints. We've found that the only way to consistently incorporate research in our work is to adjust our approach to the context and constraints of any given project. Client expectations, project type, business goals, timelines, budget, and access to participants all influence the type, frequency, and output of our research. Iterative prototype testing of an email editor, for example, looks very different than post-launch qualitative studies for an editorial website. While some projects are research-intensive, short studies can also be worthwhile.
  • Reflect on successes and shortcomings. We have a longstanding practice of holding post-project team retrospectives to reflect on and document lessons for future work. Research has naturally come up in these conversations, and many of the things we've discussed you're reading right now. As an agency with a diverse set of clients, it's been important for us to understand what types of research work for what types of clients, and when. Make sure to take time to ask these questions after projects. Mid-project retrospectives can be beneficial, especially on long engagements, yet it's hard to see the forest when you're in the weeds.

Streamline qualitative research processes 🚄

Learning to be more efficient at planning, conducting, and analyzing research has helped us overturn the idea that some projects merit research while others don't. Remote moderated usability tests are one of our preferred methods, yet, in our experience, the biggest obstacle to incorporating these tests isn't the actual moderating or analyzing, but the overhead of acquiring and scheduling participants. While some agencies contract out the work of recruiting, we've found it less expensive and more reliable to collaborate with our clients to find the right people for our tests. That said, here are some recommendations for holding efficient qualitative tests:

  • Know your tools ahead of time. We use a number of tools to plan, schedule, annotate, and analyze qualitative tests (we're inveterate spreadsheet users). Learn your tools beforehand, especially if you're trying something new. Tools should fade into the background during tests, which Reframer does nicely.
  • Establish a recruiting process. When working with clients to find participants, we'll often provide an email template tailored to the project for them to send to existing or potential users of their product. This introductory email will contain a screener that asks a few project-related demographic or usage questions, and provides us with participant email addresses which we use to follow-up with a link to a scheduling tool. Once this process is established, the project manager will ensure that the UX designer on the team has a regular flow of participants. The recruiting process doesn't take care of itself – participants cancel, or reschedule, or sometimes don't respond at all – yet establishing an approach ahead of time allows you, the researcher, to focus on the research in the midst of the project.
  • Start recruiting early. Don't wait until you've finished writing a testing script to begin recruiting participants. Once you determine the aim and focal points of your study, recruit accordingly. Scripts can be revised and approved in the meantime.

Be proactive about making research happen 🤸

As a generalist design agency, we work with clients whose industries and products vary significantly. While some clients come to us with clear research priorities in mind, others treat it as an afterthought. Rare, however, is the client who is actively opposed to researching their product. More often than not, budget and timelines are the limiting factors. So we try not to make research an ordeal, but instead treat it as part of our normal process even if a client hasn't explicitly asked for it. Common-sense perspectives like Jakob Nielsen’s classic “Discount Usability for the Web” remind us that some research is always better than none, and that some can still be meaningfully pursued. We aren’t pushy about research, of course, but instead try to find a way to make it happen when it isn't a definite priority.

World Usability Day is coming up on November 9, so now is a great time to stop and reflect on how you approach research and to brainstorm ways to improve your process. The tips above reflect some of the lessons we’ve learned at Viget as we’ve tried to improve our own process. We’d love to hear about approaches you’ve used as well.

Header graphic for the article 'Figma + Optimal: Design, Test, Iterate Faster'
Learn more
1 min read

Figma + Optimal: Design, Test, Iterate Faster

Figma has long been the go-to tool for UI/UX designers, known for its intuitive interface and real-time collaboration. In fact, over 95% of Fortune 500 companies rely on Figma, and 13 million monthly active users trust it to design and prototype digital experiences.

If you’re already designing in Figma, integrating with Optimal can help to validate your ideas early, reduce costly mistakes, and deliver experiences users actually want.

The Hidden Cost of Skipping Design Validation

Validating designs before development and catching usability issues early has a measurable impact on both users and the business. Research consistently shows that:

Figma + Optimal: Prototype Testing and Design Validation

Instead of waiting for post-launch analytics or expensive redesigns, you can test your Figma prototypes with real users in hours, not weeks with Optimal. Get quantitative data, watch recordings, analyze heatmaps, and actually see where users struggle, all before a single line of code is written.

Here’s a look into 4 practical ways teams use Figma and Optimal together.

4 Ways to Test Figma Designs with Optimal

1. Preference Testing: Let Users Pick the Winner

Ever had a debate with your team about which design direction to take? Let data decide.

Here's how:

  • Create a Figma frame with two designs side-by-side (think: two homepage variations, competing button styles, different navigation approaches)
  • Copy your Figma link and drop it into an Optimal first-click test
  • Ask participants: "Which design do you prefer?"
  • Watch the results roll in with heatmaps showing exactly where users clicked

2. Concept Testing: Does Your Idea Actually Make Sense?

You've got a bold new concept. It makes perfect sense to you. But will users get it?

The process:

  • Build wireframes or mockups in Figma (they don't need to be pixel-perfect)
  • Import your Figma link into an Optimal first-click or prototype test
  • Create tasks like “Click the option that best matches what you’re trying to do.” or “Click where you would sign up.”
  • Analyze whether users successfully understand and navigate your concept

3. Prototype Testing: Find the Friction Before Development

You've built a clickable prototype with multiple screens and interactions. It looks polished. But does it actually work for users?

Step-by-step:

  • Build a complete interactive prototype in Figma
  • Ensure all frames and flows are complete in Figma before importing into Optimal.
  • Copy your Figma prototype URL (works even with password-protected links)
  • Paste it into an Optimal prototype test
  • Define realistic tasks: "You want to buy running shoes under $100. Complete the purchase."
  • Watch video recordings and analyze usability metrics, clickmaps, misclicks, successes/failures, and heatmaps

What you'll discover might surprise you. Users will:

  • Click on things you never intended to be clickable
  • Miss obvious CTAs you thought were perfectly placed
  • Get lost in navigation that seemed intuitive to your team
  • Abandon tasks at friction points you didn't know existed

4. AI Prototype Testing: Validate AI-Generated Designs

The rise of AI design tools like Figma Make has changed the game. You can now generate a functional prototype from a text prompt in minutes. But just because AI can create it doesn't mean users can use it.

Quick workflow:

  • Generate a prototype using Figma Make
  • Copy the URL and drop it into an Optimal live site test
  • Add your testing tasks
  • Review recordings to spot usability issues

This is perfect for rapid experimentation. 

Getting Started Is Simple

  1. Prep your Figma file - Have a prototype or design ready
  2. Copy the link - Grab your Figma share URL
  3. Create your test - Choose first-click, prototype test, or live site test in Optimal
  4. Paste and configure - Add your Figma URL and write your test tasks
  5. Launch - Use your own participants or tap into Optimal's panel or Managed Recruitment services
  6. Analyze - Review results and iterate

Launch Designs Users Love

Figma gives you the power to design and prototype rapidly, while Optimal gives you the insights to make sure those designs actually work for real users. Together, they create a workflow built on real insights, not guesswork.

By testing early and often, teams can reduce risk, build confidence in their designs, and move into development knowing their work has already been validated by users. Gather insights quickly, collaborate more effectively, and keep projects moving forward with evidence-backed decisions.

Ready to validate your next Figma prototype? Use Optimal as part of your workflow and start testing with real users today.

Header graphic for the article 'A beginner’s guide to qualitative and quantitative research'
Learn more
1 min read

A beginner’s guide to qualitative and quantitative research

In the field of user research, every method is either qualitative, quantitative – or both. Understandably, there’s some confusion around these 2 approaches and where the different methods are applicable. This article provides a handy breakdown of the different terms and where and why you’d want to use qualitative or quantitative research methods.

Qualitative research

Let’s start with qualitative research, an approach that’s all about the ‘why’. It’s exploratory and not about numbers, instead focusing on reasons, motivations, behaviors and opinions – it’s best at helping you gain insight and delve deep into a particular problem. This type of data typically comes from conversations, interviews and responses to open questions. The real value of qualitative research is in its ability to give you a human perspective on a research question. Unlike quantitative research, this approach will help you understand some of the more intangible factors – things like behaviors, habits and past experiences – whose effects may not always be readily apparent when you’re conducting quantitative research. A qualitative research question could be investigating why people switch between different banks, for example.

When to use qualitative research

Qualitative research is best suited to identifying how people think about problems, how they interact with products and services, and what encourages them to behave a certain way. For example, you could run a study to better understand how people feel about a product they use, or why people have trouble filling out your sign up form. Qualitative research can be very exploratory (e.g., user interviews) as well as more closely tied to evaluating designs (e.g., usability testing). Good qualitative research questions to ask include:

  • Why do customers never add items to their wishlist on our website?
  • How do new customers find out about our services?
  • What are the main reasons people don’t sign up for our newsletter?

How to gather qualitative data

There’s no shortage of methods to gather qualitative data, which commonly takes the form of interview transcripts, notes and audio and video recordings. Here are some of the most widely-used qualitative research methods:

  • Usability test Test a product with people by observing them as they attempt to complete various tasks.
  • User interview Sit down with a user to learn more about their background, motivations and pain points.
  • Contextual inquiry – Learn more about your users in their own environment by asking them questions before moving onto an observation activity.
  • Focus group – Gather 6 to 10 people for a forum-like session to get feedback on a product.

How many participants will you need?

You don’t often need large numbers of participants for qualitative research, with the average range usually somewhere between 5 to 10 people. You’ll likely require more if you're focusing your work on specific personas, for example, in which case you may need to study 5-10 people for each persona. While this may seem quite low, consider the research methods you’ll be using. Carrying out large numbers of in-person research sessions requires a significant time investment in terms of planning, actually hosting the sessions and analyzing your findings.

Quantitative research

On the other side of the coin you’ve got quantitative research. This type of research is focused on numbers and measurement, gathering data and being able to transform this information into statistics. Given that quantitative research is all about generating data that can be expressed in numbers, there multiple ways you make use of it. Statistical analysis means you can pull useful facts from your quantitative data, for example trends, demographic information and differences between groups. It’s an excellent way to understand a snapshot of your users. A quantitative research question could involve investigating the number of people that upgrade from a free plan to a paid plan.

When to use quantitative research

Quantitative research is ideal for understanding behaviors and usage. In many cases it's a lot less resource-heavy than qualitative research because you don't need to pay incentives or spend time scheduling sessions etc). With that in mind, you might do some quantitative research early on to better understand the problem space, for example by running a survey on your users. Here are some examples of good quantitative research questions to ask:

  • How many customers view our pricing page before making a purchase decision?
  • How many customers search versus navigate to find products on our website?
  • How often do visitors on our website change their password?

How to gather quantitative data

Commonly, quantitative data takes the form of numbers and statistics.

Here are some of the most popular quantitative research methods:

  • Card sorts Find out how people categorize and sort information on your website.
  • First-click tests See where people click first when tasked with completing an action.
  • A/B tests – Compare 2 versions of a design in order to work out which is more effective.
  • Clickstream analysis – Analyze aggregate data about website visits.

How many participants will you need?

While you only need a small number of participants for qualitative research, you need significantly more for quantitative research. Quantitative research is all about quantity. With more participants, you can generate more useful and reliable data you can analyze. In turn, you’ll have a clearer understanding of your research problem. This means that quantitative research can often involve gathering data from thousands of participants through an A/B test, or with 30 through a card sort. Read more about the right number of participants to gather for your research.

Mixed methods research

While there are certainly times when you’d only want to focus on qualitative or quantitative data to get answers, there’s significant value in utilizing both methods on the same research projects.Interestingly, there are a number of research methods that will generate both quantitative and qualitative data. Take surveys as an example. A survey could include questions that require written answers from participants as well as questions that require participants to select from multiple choices.

Looking back at the earlier example of how people move from a free plan to a paid plan, applying both research approaches to the question will yield a more robust or holistic answer. You’ll know why people upgrade to the paid plan in addition to how many. You can read more about mixed methods research in this article:

Where to from here?

Now that you know the difference between qualitative and quantitative research, the best way to build confidence is to start testing. Hands-on experience is the fastest path to deeper insight. At Optimal, we make it easy to run your first study, no matter your role or research experience.

Seeing is believing

Explore our tools and see how Optimal makes gathering insights simple, powerful, and impactful.