Walk into any product company and you'll hear the same language about being user-centric. So why does the average person still rage-quit apps weekly?  If everyone's truly putting users at the center, something's not adding up. Most companies aren't lying when they say they're user-centric. They genuinely believe it. Leadership believes it. Product teams believe it. The values are probably painted on the office wall. But there's a massive gap between claiming to be user-centric and actually building products that work for users.

‍

‍

‍

Where user insights go to die

‍

‍

Let's trace what actually happens to user research in most organizations. A researcher conducts a brilliant study. They talk to real users, identify genuine pain points, uncover surprising insights about how people actually use the product. The researcher creates a comprehensive report with clear recommendations. They present to stakeholders and then…nothing happens.

‍

Product moves forward based on roadmap commitments made three months ago. Design tackles the projects already scoped. Engineering builds what's already been spec'd and by the time the next planning cycle rolls around, the research is old news. The context has shifted. New priorities have emerged. The research was great. It just never actually changed anything.

‍

The issue here isn't that teams don't value research. It's that the systems aren't set up to close the gap between insight and implementation. Research lives in one place and product decisions happen somewhere else. There's a handoff required. Someone needs to take the insights from the research and translate them into the specific contexts where decisions get made. But who owns that handoff? Usually nobody explicitly. The researcher assumes product managers will incorporate the findings. Product managers assume researchers will flag critical issues. Designers are caught in the middle, trying to advocate for users while also hitting delivery dates. So insights leak at every transition point.

‍

Even when research does make it into decision-making conversations, it's often in the wrong format for action. Researchers are trained to present thorough findings and all of that is valuable. But it's not always actionable. The gap between what users said and what should be done about it, is a lot bigger than most teams realize, but an even bigger problem is that product decisions can’t wait for perfect information. Product decisions need to happen fast, often in real-time, in contexts where pulling up a research report isn't practical. If research insights aren't immediately accessible in the moment decisions are being made, they effectively don't exist.

‍

‍

‍

So…What actually works?

‍

‍

The companies that successfully put users at the center do something different. They build research into the decision-making flow rather than treating it as a separate activity that informs decisions. They make sure that research insights live where decisions happen, integrated into project management tools, design files, and product specs.

‍

Increasingly, they're also using MCP (Model Context Protocol) to connect AI tools like Claude, ChatGPT, and Cursor directly to their research repository – here's how. Instead of searching through reports, teams can ask questions in natural language to surface relevant findings, user insights, and context exactly when they need them, or generate artifacts and workflows grounded in real user research. Insights are accessible in the moment someone needs them.

‍

At Optimal, our design team embeds research findings directly in their Figma files. Not as links to external reports, but as context right next to the designs. When someone's reviewing navigation options, the tree test results are right there. When they're looking at prototype variations, the usability data is embedded in the file. Decisions and insights exist in the same place.

‍

Another great step is to make sure that all research insights are framed as recommendations, not just observations. Instead of "Users struggled with the checkout flow," the insight could be "Simplify checkout to 3 steps instead of 5, based on usability testing where users abandoned at step 4." The researcher isn't just reporting what happened. They're translating it into clear next steps.

‍

We also firmly believe that research should be continuous instead of episodic. Instead of big studies that take weeks and produce comprehensive reports, teams run smaller tests constantly. This doesn't replace deep foundational research. But it supplements it with rapid feedback loops that keep user input flowing into active work.

‍

And lastly - research should be accessible to all. When only dedicated researchers can conduct studies, research becomes a bottleneck. When product managers and designers can run quick tests themselves, with appropriate guidance and quality standards, research becomes embedded in how the team works rather than something teams have to request and wait for.

‍

Being genuinely user-centric requires infrastructure, not just values. You need tools that make it easy to share findings where people actually work. You need workflows that integrate research into product development rather than treating it as a separate track. You need the ability to run research at the speed decisions happen.

‍

Most importantly, you need to make the gap between insight and action as small as possible. The best research in the world doesn't help users if it never influences what gets built.

So, you’re ready to run a study. It’s designed, you’ve planned your questions, your methodology is sound. Your discussion guide is carefully crafted to avoid leading questions and dig into real user motivations…then you start recruiting participants.

‍

Suddenly, you’ve hit a massive bottleneck. Your perfect study depends entirely on finding the right people, getting them to show up, and hoping they provide thoughtful responses rather than one-word answers and distracted multitasking. You’ve now hit the crunch point that every researcher faces: your insights are only as good as your participants. What happens when participant quality isn’t great? 

‍

‍

‍

The hidden cost of "good enough"

‍

‍

Let's be honest about what typically happens with recruitment. You need a minimum number of participants to get statistically significant results (depending on study type). You’ve got a time limit in which you need to get results so they’re still relevant to your product development lifecycle. You start reaching out through your usual channels: customer lists, screening surveys, panel providers, social media posts, begging colleagues to connect you with people who fit your criteria. 

‍

After a week of this, you've got a few confirmed participants, but not enough. Some people have expressed interest but haven't confirmed times and it’s teeming more and more like your study is going to launch late, and you’re going to miss product deadlines. 

‍

So you make compromises.

‍

You accept the participant who sort of fits your criteria but isn't quite in the target demographic. You take the person who can only do a 30-minute session instead of the planned 60 minutes. You keep the flaky participant who's rescheduled twice because you need the numbers. 

‍

Then the sessions happen.

‍

One person no-shows. Another is clearly distracted, giving minimal responses while probably checking email. A third seems to have misunderstood the screening criteria entirely and doesn't actually use the type of product you're researching. The two good participants provide valuable insights, but now you're making conclusions based on a sample size of two.

‍

This isn't research. This is educated guessing with extra steps.

‍

‍

‍

What bad participants cost you

‍

‍

1. Quality  In, Quality Out. Poor participant quality isn't just annoying. It has real consequences that ripple through everything that comes after. The worst outcome isn't getting no data. It's getting bad data that you treat as good data. A participant who doesn't match your target users provides feedback, but that feedback doesn't represent your actual users. If you act on it, you're optimizing for the wrong people. Bad data doesn't just waste research time. It sends product decisions in the wrong direction. 
2. Wasted team time. You spend hours recruiting, scheduling, conducting sessions, and analyzing results. When the research is based on poor-quality participants, all of that time is wasted. Or worse, it's spent acting on misleading information. One bad research study doesn't just cost the time invested in that study. It costs the time spent implementing the wrong solutions based on faulty insights.
3. Damaged credibility. Research teams build credibility over time by providing insights that prove valuable. Stakeholders learn to trust research because it leads to better decisions. But credibility is fragile. When research based on poor participants leads to recommendations that don't pan out, stakeholders start questioning whether research is worth the investment. 
4. Slower velocity. Settling for mediocre participants to move faster actually slows you down. You run your study quickly with whoever you can find. The insights are muddy. You're not quite sure what to conclude. So you run a follow-up study to clarify. Or you make a decision with low confidence and have to course-correct later when it doesn't work. Meanwhile, teams that spend time getting quality participants upfront get clear insights the first time. They make decisions confidently and move forward quickly because they trust what they learned. The bottleneck isn't the time spent recruiting quality participants. It's the back-and-forth that comes from unclear results based on poor participants.

‍

‍

‍

What do we really mean by quality participants? 

‍

‍

When you're under pressure to deliver research quickly, it's tempting to view participants as interchangeable. You need 8 people. Any 8 people who vaguely fit the criteria will do. But that’s not actually the case at all. The whole point of user research is to understand your specific users. Their context, their mental models, their workflows, their pain points. Generic "users" don't exist. There are only specific people with specific needs trying to accomplish specific things. If the participants in your study don't actually represent your target users, you're not doing research. You're doing work that looks like research but doesn't provide real insights. When we say quality participants we mean: 

‍

1. They match your target criteria.  This seems obvious, but it's where most compromises happen. Every compromise in targeting dilutes the relevance of your insights. Quality participants don't just technically qualify. They deeply represent the actual people you're designing for.
2. They're engaged and thoughtful. A quality participant shows up prepared, gives full attention during the session, thinks carefully about questions, and provides detailed responses based on real experience. Engagement matters as much as targeting. A perfectly targeted participant who phones it in provides almost no value.
3. They show up. Seems basic, but no-shows are a massive problem. Quality participants honor their commitments. Consistent show rates mean you can actually plan research without padding your schedule with backup participants and hoped-for reschedules.
4. They're honest. Participants who tell you what they think you want to hear are worse than useless. You need people who'll be direct about confusion, frustration, and problems. Quality participants don't try to be nice or avoid hurting feelings. They give genuine feedback even when it's critical.

‍

‍

‍

The panel problem

‍

‍

Many teams rely on user research panels, databases of people willing to participate in studies for compensation,  which are often limited by the platform that they’ve purchased to one, proprietary panel for their research. Panels solve the recruitment problem by providing quick access to participants. But panels come with significant limitations.

‍

1. You're limited to who's in the panel. Need product managers at Series B startups in fintech? Need parents of children with specific developmental needs? If they're not in the panel, you can't reach them. You end up compromising your targeting to fit who's available rather than finding who you actually need.
2. Professional participants. Some people do user research studies regularly, almost as a side job. They're good at interviews. They know what researchers want to hear. They've done enough studies to unconsciously game the process. These "professional participants" might give you data, but they don't represent typical users. Their feedback is shaped by their experience participating in dozens of studies.
3. Quality inconsistency.  Panel quality varies dramatically. Some panels carefully vet participants and maintain high standards. Others will provide anyone who roughly matches your screener to hit the numbers you've requested. 

‍

When you're locked into a single panel provider, you're stuck with whatever quality standards they maintain.

‍

‍

‍

The panel ecosystem approach

‍

‍

The alternative to depending on a single panel is having access to multiple sources for participants. This means you're not limited by one panel's database. When you need specific, hard-to-reach audiences, you can access specialized panels that focus on those groups. When you need B2B professionals, you use networks that focus on business users. When you need consumers with specific characteristics, you access consumer panels with better targeting. The ecosystem model provides flexibility, better matching, and higher quality because you're not forcing every recruitment need through the same funnel. By the way, this is the way Optimal has intentionally chosen to offer participant recruitment via our platform for our customers (a panel ecosystem approach). 

‍

‍

‍

What changes when recruitment isn't the constraint

‍

‍

Imagine recruitment takes two days instead of two weeks. Imagine you can specify exactly the targeting you need and trust you'll get quality participants who match. How does your research change?

‍

1. You run more studies. When recruitment isn't a weeks-long process, research becomes more viable for smaller questions. More research means more informed decisions across the board.
2. You're more rigorous about targeting. When getting participants is easy, you don't have to compromise on criteria. You can be specific about exactly who you need and actually get them. Your insights become more reliable because they're based on truly representative participants.
3. You test more variations. Instead of showing 5 participants one design and hoping it works, you can test multiple variations with appropriate sample sizes for each. You can run A/B comparisons. You can validate results across different user segments. Better participant access enables more sophisticated research.
4. You move faster. Your timeline shrinks dramatically when recruitment isn't the bottleneck. Research becomes a viable input for time-sensitive decisions, not just long-term strategic work.

‍

Poor participant quality isn't a minor annoyance. It's the difference between research that drives confident decisions and research that creates false confidence in bad decisions. Quality in, quality out isn't just a principle. It's the foundation that determines whether your research is worth doing at all. 

‍

The recruitment bottleneck is real. But it's solvable. Teams that solve it don't just do more research. They do research that's actually worth acting on.

‍

We spent Research Week in San Francisco listening, taking notes, and talking with the UX and market researchers, research managers, human factors engineers, research operations program managers, and product designers who gathered coast to coast. Sessions covered Advanced Market Research, Growth UXR, Great Research, AI and UXR, Up Up and Away!, and Moonshot Research.

‍

‍

‍

What are the key themes and insights that emerged from Research Week?

‍

‍

• Product defines, marketing communicates,  business captures the value, and researchers are translators and connectors.
• Build a culture of influence because influence isn't a moment, it's a structure.
• The insights alone are not enough; it's how you deliver and socialize them that makes them stick.
• Nothing hits like good UX research: compelling clips, stats, and verbatims.
• AI is transforming workflows, enabling large-scale data processing so researchers can focus on high-value work.

‍

‍

Practical takeaways to implement next week

‍

‍

Know who you're translating for and what matters to them

‍

‍

The gap in research most teams face right now is translation. Every function hears research differently. Each has a completely different "so what," as Apurva Luty puts it, so you need to respond and hear different ways, hearing data science in questions, design in critique, marketing in frameworks, engineering in constraints, and leadership in confidence. No one wants to hear: "we need to do more research”, but when you feel rushed for insights, you can always ask upfront if it’s a quick directional and recognize when you need more time for a comprehensive answer. 

‍

Building that bridge doesn’t mean you’re a gatekeeper. Rachel Ousley has seen democratizing access to data play out through more conversations and approaches with better questions.  Map your stakeholders' "so what" and foster an open line of communication because you are working towards the same goal in the end. 

‍

‍

Design for a culture of influence

‍

‍

Influence isn't a moment, it's a structure. Jess Holbrook breaks down direct influence versus indirect influence where direct influence is the central mechanism you present to senior leadership, and indirect influence is about setting the stage. Get ahead of it: know what your organization needs to understand in three months, six months, nine months, and how do we set ourselves up now to do that? 

‍

Build a culture of influence by giving credit loudly and often, saying people's names in the room by sharing wins and shoutouts. At Optimal, we do this through a celebrations Slack channel and quarterly value awards with open nominations through the company. Bring stakeholders, even ones you might not see eye-to-eye with upfront, into conversations where their perspective is genuinely valued, and anticipate what your team needs.

‍

‍

Continue running thoughtful studies with your users

‍

‍

The value of research is clear: to build better experiences, you must listen to the people who are using the product, service, the thing you’re making, and are affected by it. It is in discovery where you, well, discover what users actually want. As Andrew Chamberlain says, those hack projects and rapid prototypes can scale and become new products, and beyond that, research is how you elevate your brand and get invited into new spaces. 

‍

In discovery, know when to screen for behavior and when to screen for demographics. Maybe you’re looking at how people us mobile devices in homes, where one phone does not necessarily mean one owner or one user and in this case, your questions need to be framed openly and intuitively to get insight into your users’ mental models and actions, often different from your own, with people assigning different meanings to the same words. Nicole Naurath uses the example of asking “Do you share a device?” instead of, “How does someone else access this device?” to capture richer, more accurate insights into actual behavior.

‍

‍

Treat delivery like it's part of the research

‍

‍

Research reporting is socialization. Your decks don't have to change, but the artifacts around it do. A compelling clip, a sharp stat, a well-chosen verbatim – nothing hits like it. Nicole Zeng explains UX research as the thing that silences rooms, changes minds, and redirects roadmaps.

‍

Format your findings and discussion for the spaces people already work. Lauren Lin describes sharing insights as stackable and shareable clips on Slack as well as data cards that are downloadable as Figma components. 

‍

‍

Use AI to buy back your time for the work that matters

‍

‍

AI is enabling large-scale data processing that used to take months, which means you can spend less time in the weeds and more time on the work that moves the needle – the  judgment, translation, organizational, goal setting, and influence-building work. AI can handle the volume and scale of your data. However, everyone has a different comfort level with new tools. Nicole Zeng uses the analogy of a lake: maybe you’re diving in headfirst, maybe you’re watching from the shore, or maybe you’re paddling through the waves. 

‍

Break your workflow and explore novel ways of leveraging AI in UX research, then share out your findings and flows, because that's how we make progress as teams, get deeper customer insights, and ultimately make better decisions. It's why we're constantly evolving Optimal, and Optimal 3.0 is built for exactly this: helping product teams discover, validate, and continuously optimize user experiences that drive real business results.

‍

We're in an exciting time and it's moments like this when our industry comes together that we never forget. Stay connected with us on LinkedIn to get the latest updates on our upcoming events!

Artificial intelligence offers remarkable capabilities for UX research. It can process massive datasets, identify patterns humans might miss, and accelerate insights that traditionally took weeks to uncover. But as the adage goes: with great power comes great responsibility.

‍

As research teams increasingly adopt AI-powered tools, we're facing critical questions about data privacy, algorithmic bias, and ethical use of user information. These aren't just philosophical concerns, they're practical challenges that every research team needs to address.

‍

‍

‍

More data, more risk

‍

‍

AI thrives on data. The more information it can access, the better its pattern recognition and predictive capabilities become. For researchers, this creates a fundamental tension. To gain meaningful insights, you need comprehensive user data, but collecting and processing this data creates privacy risks that traditional research methods didn't face at the same scale.

‍

Think about a typical AI-powered analysis:

‍

• User session recordings processed to identify usability issues
• Behavioral data analyzed to understand user journeys
• Interview transcripts processed for sentiment analysis and theme identification

‍

Each of these activities involves handling sensitive user information. Each creates potential exposure points where data could be misused, breached, or processed in ways users didn't anticipate. The question isn't whether you should use AI but rather how to use it responsibly.

‍

‍

‍

Building privacy into your AI research practice

‍

‍

Privacy can't be an afterthought. It needs to be foundational to how you approach AI-powered research. Collect only the data you actually need. This seems obvious, but AI's hunger for information can encourage overcollection. Before implementing any AI tool, ask: What's the minimum data required to achieve our research goals? Just because you can collect comprehensive behavioral data doesn't mean you should. Be intentional about what you gather and why.

‍

Data security basics also become even more critical when AI is involved. Encryption, secure storage, access controls, these aren't optional. But security goes beyond technology. It includes policies around who can access data, how long it's retained, and what happens when a project concludes. AI systems often retain data to improve their algorithms. Make sure you understand your tools' data retention policies and ensure they align with your privacy commitments. A good example of this is how some tools, like Optimal, offer PII redaction on user interviews to ensure data security and privacy. 

‍

‍

‍

Be transparent with users

‍

‍

Users deserve to know how their data is being used. This goes beyond the standard privacy policy checkbox. When conducting research with AI-powered tools, you need to clearly communicate:

‍

• What data you're collecting
• How AI will process that data
• What insights you're hoping to gain
• How long you'll retain the information
• Who else might have access to it

‍

Give users meaningful control. If they're uncomfortable with AI analysis, offer alternatives. If they want their data deleted, make that process straightforward. Transparency builds trust. And trust is the foundation of good research.

‍

‍

‍

The bias problem

‍

‍

Something that all teams who incorporate AI into their research practices need to be aware of is that AI systems can perpetuate and amplify bias. Machine learning algorithms learn from training data. If that data contains biased patterns, and most data does, the AI will replicate those biases in its analysis. This can lead to research insights that systematically overlook certain user groups or misinterpret their needs. For researchers, this creates a serious challenge. You're using AI to understand users, but the AI itself might have blind spots that skew your understanding. Eliminating bias entirely is probably impossible. But you can take concrete steps to minimize its impact.

‍

1. Diversify your training data. If you're building custom AI models, ensure your training data represents the full diversity of your user base. This includes obvious factors like demographics, but also less visible ones like technical proficiency, language preferences, and usage contexts.
2. Use multiple analytical approaches. Don't rely solely on AI-generated insights. Combine algorithmic analysis with traditional qualitative methods. When AI flags a pattern, validate it through direct user research. When you see a trend in the data, talk to actual users to understand the context.
3. Interrogate unexpected findings. When AI produces surprising insights, don't accept them at face value. This skepticism isn't about distrusting AI. It's about using it thoughtfully.
4. Ensure diverse perspectives on your research team. Bias is easier to spot when you have people from different backgrounds reviewing the work. Build research teams that bring varied perspectives and life experiences. They'll be more likely to notice when AI-generated insights don't ring true for certain user segments.

‍

‍

‍

Navigating third-party AI tools

‍

‍

Most research teams don't build their own AI systems. They use third-party tools that come with built-in AI capabilities. This creates an additional layer of privacy and ethical considerations. Before adopting any AI-powered research tool you need to understand the vendor's data practices. Not all vendors handle data the same way. Choose partners who take privacy seriously.

‍

‍

‍

Stay current with regulations

‍

‍

Data privacy regulations are evolving rapidly. GDPR, CCPA, and emerging laws around AI governance create complex compliance requirements.nEnsure your AI-powered research practices align with relevant regulations in the jurisdictions where you operate. This isn't just about legal compliance, it's about respecting user rights.

‍

‍

‍

The most Important Ethical AI Component: Human judgment 

‍

‍

Here's what ties all of these considerations together: Human judgment must remain central to AI-powered research. AI can process data faster than any human, but it can't recognize when an algorithm is producing biased results or understand the ethical implications of a particular insight. These responsibilities fall to human researchers. And they can't be automated.

‍

At Optimal, we believe AI should enhance research capabilities while respecting user privacy and maintaining ethical standards. That's why we're committed to transparent data practices, secure infrastructure, and tools that put researchers in control. Because the goal isn't just better insights. It's better insights achieved responsibly.

The UX research landscape is shifting. While design thinking has always championed human-centered approaches, empathy, iteration, and deep user understanding, artificial intelligence is introducing new capabilities that are fundamentally changing how we work.

‍

But here's the thing: AI isn't replacing the design thinking process. It's amplifying it.

‍

Recent research into the synergies between design thinking and AI reveals something fascinating. When these two approaches combine, they create something more powerful than either could achieve alone. AI handles the heavy lifting of data processing and pattern recognition, while human researchers bring irreplaceable skills like empathy, contextual understanding, and ethical judgment.

‍

Here’s how we think this partnership is reshaping each stage of the design thinking process.

‍

‍

‍

Deeper insights at scale

‍

‍

The empathize stage has always been about understanding users. Understanding their needs, pain points, and motivations. Traditionally, this meant conducting interviews, observations, and surveys, then manually analyzing the results. In this situation, AI changes the scale at which we can operate. 

‍

Machine learning algorithms can now process vast amounts of user data, demographics, behavioral patterns, interaction histories, to identify trends that might take researchers weeks to uncover manually. This doesn't replace the need for human empathy. Instead, it provides a foundation of data-driven insights that researchers can build upon with qualitative methods. Think of it this way: AI can tell you what users are doing and identify patterns across thousands of interactions. But only human researchers can understand why those patterns exist, what they mean in context, and how they connect to deeper human needs.

‍

The result? More comprehensive user personas, informed by both quantitative rigor and qualitative depth.

‍

‍

‍

Clarity through data

‍

‍

Once you understand your users, you need to define the problem you're solving. This stage requires synthesizing diverse insights into a clear, actionable problem statement. In this scenario AI-powered analytics can accelerate this process by helping you:

‍

• Identify which user pain points appear most frequently
• Spot correlations between different user behaviors
• Prioritize problems based on impact and frequency

‍

But defining the right problem still requires human judgment. AI might flag that users abandon a particular workflow, but it takes a researcher to understand whether that's due to poor usability, lack of trust, or a fundamental mismatch between the product and user needs. The partnership between AI insights and human interpretation ensures you're not just solving problems efficiently, you're solving the right problems.

‍

‍

‍

AI as a collaborator

‍

‍

Ideation is where things get interesting. This stage is all about generating diverse solutions without prematurely narrowing options. In this situation, AI can support ideation in unexpected ways. Generative algorithms can analyze existing design patterns and generate alternative solutions based on specific parameters. They can provide design references, identify emerging trends, and even suggest approaches you might not have considered. But AI still can't bring lived experience to the table. It can't draw on intuition developed through years of research. It can't make creative leaps that connect seemingly unrelated concepts.

‍

The most effective ideation happens when AI serves as a creative assistant, offering options, inspiration, and data-backed suggestions, while human researchers provide direction, judgment, and that spark of creative insight that can't be automated.

‍

‍

‍

Faster iteration cycles

‍

‍

Prototyping has always been about quick, low-fidelity tests to validate ideas. AI can now speed up this process dramatically. AI-powered tools can automate the creation of initial prototypes based on design specifications. They can generate multiple layout options, suggest color schemes, and even produce variations for different user segments, all in a fraction of the time manual prototyping would require. This speed enables more iterations in less time.

‍

Instead of spending days creating a single prototype, researchers can now generate multiple versions quickly, test them with users, and incorporate feedback into the next iteration. The result is a more refined, user-validated design in a compressed timeline. The human role here shifts from manually creating every prototype element to making strategic decisions about which variations to pursue and how to interpret user feedback.

‍

‍

‍

Insights at scale, empathy in interpretation

‍

‍

Testing is where AI's capabilities shine brightest, and where human judgment becomes most critical. AI can process user testing data at scale. It can analyze session recordings, identify usability issues, track where users struggle, and flag patterns across hundreds or thousands of test sessions. Tools, like Optimal,  with AI-powered features can analyze video interviews, identifying themes and sentiment across participant responses. But interpreting what those patterns mean requires human insight.

‍

A user might abandon a task because the interface is confusing or because they received a phone call. They might rate an experience negatively due to a specific design element or because they're having a bad day. AI can flag the behavior, but researchers must understand the context. The combination of AI-powered analysis and human interpretation creates a testing process that's both comprehensive and nuanced.

‍

‍

‍

The new researcher skill set

‍

‍

As AI becomes integrated into the research process, the skills that define excellent researchers are evolving. Technical skills matter more than before. Understanding how AI tools work, what data they need, and how to interpret their outputs is increasingly essential. Researchers need to think critically about AI limitations, where algorithms might introduce bias, when data-driven insights need human validation, and how to ensure ethical use of user data. But the core of great research remains unchanged. Empathy, curiosity, critical thinking, and the ability to tell compelling stories with data, these fundamentally human skills aren't being automated. They're becoming more valuable.

‍

‍

‍

What does this mean for research teams? 

‍

‍

The integration of AI into design thinking isn't a distant future scenario. It's happening now.

‍

Research teams that embrace this shift, learning to work alongside AI rather than seeing it as a threat, will find themselves capable of work that was previously impossible. Deeper insights from larger datasets. Faster iteration cycles. More refined designs. Better user experiences.

‍

The key is approaching AI as a tool that enhances human capabilities rather than replaces them. At Optimal, we're thinking deeply about how AI can support researchers without compromising the human-centered principles that make great research possible. Because at the end of the day, understanding users isn't just about processing data. It's about connecting with people, understanding their needs, and creating experiences that genuinely improve their lives.

‍

Read more about Optimal’s AI features and our approach to incorporating AI into our platform here. 

‍

59% of teams say that without research, their decisions would be based on assumptions. Yet only 16% of organizations have user research fully embedded in how they work.

‍

That gap explains why so much research never influences what gets built.

‍

Teams do the work – they run studies, gather insights, document findings. But when research tools are too complex for most people to use, when getting insights takes weeks instead of days, when findings arrive after decisions are already made, research becomes documentation, not direction.

‍

The problem isn't research quality. It's that most user research processes don't match how product teams actually make decisions. Research platforms are too complex, so only specialists can run studies. Analysis takes too long, so teams ship before insights are ready. Findings arrive as 40-slide decks, so they get filed away instead of acted on.

‍

The teams getting research to influence decisions aren't running more studies. They're running connected workflows that answer the right questions at the right time, with insights stakeholders can't ignore.

‍

Here are five workflows that make this happen.

‍

‍

‍

1. Understand what competitors get right (and wrong)

‍

‍

Your team is redesigning checkout, and leadership wants competitive intelligence. But screenshot comparisons and assumptions won't cut it when you're trying to justify engineering time.

‍

Here's the workflow:

‍

Start with Live Site Testing to observe how real users navigate competitor experiences. Watch where they hesitate, what they click first, where they abandon the process entirely. You're not analyzing what competitors built, you're seeing how users actually respond to it.

‍

Follow up with Interviews to understand the why behind the behavior. Upload your live site test recordings and use AI analysis to surface patterns across participants. That random dropout? It's actually a theme: users don't trust the security badge placement because it looks like an ad.

‍

Validate your redesign with Prototype Testing before you commit to building it. Test your new flow against the competitor's current experience and measure the difference in task success, time on task, and user confidence.

‍

What stakeholders see: Video evidence of where competitors fail users, quantitative data proving your concept performs better, and AI-generated insights connecting behavior to business impact. 

‍

‍

‍

2. Ship features users will actually use

‍

‍

Product wants to launch a new feature. You need to make sure it won't just join the graveyard of functionality nobody touches.

‍

Here's the workflow:

‍

Use Surveys to understand current user priorities and pain points. Deploy an intercept survey on your live site to catch people in context, not just those who respond to email campaigns. Find out what problems they're actually trying to solve today.

‍

Build it out in Prototype Testing to see whether users can find, understand, and successfully use the feature. Validate key interactions and task flows before engineering writes a line of code. Where do users expect to find this feature? Can they actually easily complete the task you're building it for? Do they move through a flow as intended?

‍

Conduct Interviews to explore the edge cases and mental models you didn't anticipate. Use AI Chat to query across all your interview data: "What concerns did users raise about data privacy?" Get quotes, highlight reels, and themes that answer questions you didn't think to ask upfront.

‍

What stakeholders see: Evidence that this feature solves a real user problem, proof that users can find it where you're planning to put it, and specific guidance on what could cause adoption to fail.

‍

‍

‍

3. Fix navigation without rebuilding blindly

‍

‍

Your information architecture is a mess. Years of adding features means nobody can find anything anymore. But reorganizing based on what makes sense to internal teams is how you end up with labels or structures that don’t resonate with users.

‍

Here's the workflow:

‍

Run Card Sorting to understand how users naturally categorize your content. What your team calls "Account Settings," users call "My Profile." What seems logical internally could be completely foreign to the people who actually use your product.

‍

Validate your structure with Tree Testing before you commit to rebuilding. Test multiple organizational approaches and use the task comparison tool to see which structure helps users complete critical tasks. Can they find what they need, or are you just rearranging deck chairs?

‍

Use Live Site Testing to see how people struggle with your current navigation in practice. Watch them hunt through menus, resort to search as a last-ditch effort, give up entirely. Then test your new structure the same way to measure actual improvement, not just theoretical better-ness.

‍

Upload recordings to Interviews for AI-powered analysis. Get clear summaries of common pain points, highlight reels of critical issues, and stakeholder-friendly video clips that make the case for change.

‍

What stakeholders see: Your redesign isn't based on internal preferences. It's based on how users think about your content, validated with task completion data, and backed by video proof of improvement.

‍

‍

‍

4. Boost conversions with evidence from users

‍

Leadership wants to know why conversion rates are stuck. You have theories about friction points, but theories don't justify engineering sprints.

‍

Here's the workflow:

‍

Deploy Surveys with intercept snippets on your live site. Ask people in the moment what they're trying to accomplish and what's stopping them. Surface objections and confusion you wouldn't discover through internal speculation. This solves two problems: you get feedback from actual users in context, and you avoid the participant recruitment challenge that 41% of researchers cite as a top obstacle.

‍

Run Live Site Testing to watch users actually attempt to convert. See where they hesitate before clicking "Continue," what makes them abandon their cart, which form fields cause them to pause and reconsider.

‍

Run First-Click Testing to identify navigation barriers to conversion. Test whether users can find the path that leads to conversion - like locating your pricing page, finding the upgrade plan button, identifying the right product category, or comparing different products to each other. Users who make a correct first click are 3X more likely to complete their task successfully, so this quickly reveals when poor navigation or unclear signage is killing conversion.

‍

Test proposed fixes with Prototype Testing before rebuilding anything. If you think the problem is an unclear value proposition, test clearer messaging. If you think it's a trust issue, test different social proof placements. Compare task success rates between your current flow and proposed changes.

‍

Use Interviews to understand the emotional and practical barriers underneath the behavior. AI analysis helps you spot patterns: it's not that your pricing is too high, it's that users don't understand what they're getting for the price, or why your option is better than competitors.

‍

What stakeholders see: Exactly where users drop off, why they drop off, and measured improvement from your proposed solution, all before engineering builds anything.

‍

‍

‍

5. Make research fast enough to actually matter

‍

‍

Your product team ships every two weeks. Research that takes three weeks to complete is documentation of what you already built, not input into decisions.

‍

Here's the workflow:

‍

Build research into your sprint cycles by eliminating the manual overhead. Use Surveys for quick pulse checks on assumptions. Deploy a tree test in hours to validate a navigation change before sprint planning, not after the feature ships. Invite your own participants, use Optimal's on-demand panel for fast turnaround, or leverage managed recruitment when you need specific, hard-to-reach audiences.

‍

Leverage AI to handle the time-consuming work in Interviews. Upload recordings and get automated insights, themes, and highlight reels while you're planning your next study. What used to take days of manual review now takes minutes of focused analysis. AI also automatically surfaces patterns in survey responses and pre/post-task feedback across your studies, so you're finding insights faster regardless of method.

‍

Test current and proposed experiences in parallel. Use Live Site Testing and Prototype Testing to baseline the problem with your current experience, while simultaneously testing your solution. Compare results side-by-side to show measurable improvement, not just directional feedback. Tree testing has built-in task comparison so you can directly measure navigation performance between your existing structure and proposed changes.

‍

Share results in tools your team actually uses. Generate highlight reels for stand-ups, pull specific quotes for Slack threads with AI Chat, export data for deeper stakeholder analysis. Research findings that fit into existing workflows get used. Research that requires everyone to change how they work gets ignored.

‍

What stakeholders see: Research isn't the thing slowing down product velocity. It's the thing making decisions faster and more confident. Teams do more research because research fits their workflow, not because they've been told they should.

‍

‍

‍

The pattern: What actually makes user research influential

‍

‍

Most organizations struggle to embed user research into product development. Research happens in disconnected moments rather than integrated workflows, which is why it often feels like it's happening to teams rather than with them.

‍

Closing that gap requires two shifts: building a user research process that connects insights across the entire product cycle, and making research accessible to everyone who makes product decisions.

‍

That's the workflow advantage: card sorting reveals how people naturally categorize and label content, tree testing validates structure, surveys surface priorities, live site testing shows real behavior, prototype testing confirms solutions, interviews provide context, and AI analysis handles synthesis. Each method is designed for speed and simplicity, so product managers can validate assumptions, designers can test solutions, and researchers can scale their impact without becoming bottlenecks.

‍

The workflows we covered - reducing churn, validating roadmaps, boosting conversions, proving impact, and matching product velocity - all follow this same pattern: the right combination of UX research methods, deployed at the right moment, analyzed fast enough to matter, and accessible to the entire product team.

‍

Ready to see how these user research workflows work for your team? Explore Optimal's platform or talk to our team about your specific research challenges.

‍