The research process is broken. These 3 plays fix it

Posted on June 4, 2026
6 min read

Share

AI is accelerating software development. Discover 5 must-haves modern research teams need to keep up, from faster recruiting to better insights.

A familiar scene plays out in product organizations every day.

A team is wrestling with an important decision. Perhaps they're debating a new feature, trying to understand a sudden drop in engagement, or exploring a promising new direction for the product. 

The researcher in the room faces a choice. They can insist on following the process: scope the study, write the discussion guide, recruit participants, run sessions, synthesize findings, and present recommendations several weeks later. Or they can acknowledge what everyone already knows: by the time the research is complete, the decision will almost certainly have been made.

For years, we've accepted that good research takes time. But that assumption is becoming harder to defend.

AI has compressed nearly every stage of product development. Teams can move from idea to prototype in a matter of hours. Concepts that once took weeks to visualize can now be generated in a single afternoon. Product organizations have become dramatically faster.

This doesn't mean research quality has declined. In many cases, the opposite is true. Researchers are producing thoughtful work, asking better questions, and generating richer insights than ever before.

Yet many are still finding themselves further from the decisions that matter most. But we don’t think they need better research. 

They need better workflows to integrate with the rest of the organization.

During our conversations with research leaders at Microsoft AI, Instacart, Carta, and Google Ventures, a different pattern emerged. The teams gaining influence weren't producing dramatically more research than everyone else, nor were they sacrificing rigor in pursuit of speed. They had simply redesigned their workflows around a reality most organizations are still struggling to accept: product development has accelerated, and research has to accelerate with it. Three practices surfaced repeatedly.

 

DOWNLOAD

Get the playbook

We partnered with the team at Design Better to create a Research as Organizational Intelligence, a comprehensive playbook for how to transform your research team to thrive in the age of AI

The Two-User Gut Check

Researchers spend a lot of their careers explaining why small sample sizes can be misleading. Which makes it somewhat uncomfortable to advocate for a method built around talking to only two people.

Yet the research leaders we interviewed kept returning to the same observation: in fast-moving organizations, the comparison is rarely between a two-person study and a thirty-person study.

More often, it's between a two-person study and no study at all.

Imagine a product team facing a decision that needs to be made by Friday. Everyone agrees user input would be valuable. There simply isn't time to recruit a large sample, conduct a full study, and synthesize the results. As a result research disappears from the conversation at that point and the decision proceeds on instinct.

The Two-User Gut Check offers another option.

Recruit two participants who closely match the target audience. Run focused sessions around the question at hand. Be explicit about what the output represents: not validated findings, but directional input.

That distinction matters.The goal is not certainty. The goal is to expose assumptions before they harden into decisions.

Two conversations can reveal surprising blind spots. They can surface obvious points of confusion. They can challenge a team's confidence in an idea that looked promising in a planning meeting but falls apart when confronted with real users.

Nobody should mistake those conversations for a comprehensive study. But in many situations, they are enough to change the quality of the discussion.Research leaders who use this approach well aren't lowering the bar for evidence. They're recognizing that influence often depends on being present before certainty is possible.

The Bullseye Customer Sprint

If the Two-User Gut Check challenges our assumptions about sample size, the Bullseye Customer Sprint challenges our assumptions about recruiting.

Most teams spend considerable energy debating how many participants they need. Far fewer spend the same energy defining exactly who those participants should be. As a result, recruitment criteria often remain surprisingly broad.

"Enterprise software users."

"Small business owners."

"Knowledge workers."

The categories sound precise until you start recruiting against them.

One of the strongest ideas we encountered during our interviews came from a simple observation: participant quality matters far more than most teams realize.

Before recruiting begins, define the target participant with enough specificity that two different recruiters would find essentially the same people.

Not just “enterprise software users,” but “Operations managers at companies with 200 to 500 employees who currently manage workflows in spreadsheets.”

Not “online shoppers” but “Parents of children under ten who purchase specialty dietary products at least twice a month.”

This level of specificity changes the entire study because recruiting becomes easier and findings become clearer. Stakeholders spend less time arguing about whether participants were representative and more time discussing what was learned.

Several leaders described situations where five carefully recruited participants generated more useful insight than fifteen loosely matched ones. The competitive advantage isn't running more sessions. It's talking to the right people.

The Hybrid Study

If there was one theme that surfaced in every conversation, it was caution about automation.

The leaders we spoke with were enthusiastic about AI's ability to accelerate research workflows. Many were actively experimenting with AI-assisted moderation, synthesis, and analysis.

But they also worried about a subtle risk.As AI becomes more capable, researchers may gradually lose the hands-on experience required to evaluate its output. The danger isn't that AI produces obviously bad work. It's that it produces work that sounds convincing. 

The strongest teams have developed a simple response. Before scaling a study with AI, they conduct the first sessions themselves. Five sessions came up frequently as a useful benchmark.

These early conversations accomplish several things at once. They reveal weaknesses in the discussion guide. They surface unexpected themes. Most importantly, they help researchers develop an intuitive understanding of what the data actually looks and feels like.

Only then do they begin introducing automation.

One research leader described those initial sessions as “quality infrastructure.” Without that foundation, researchers risk outsourcing not just execution but judgment.

With it, they can scale confidently, knowing they have a reference point against which to evaluate AI-generated outputs.

The future of research is unlikely to be fully manual.

It's equally unlikely to be fully automated.

The organizations finding success are learning how to combine the strengths of both.

WEBINAR

How UXR Leaders Can Shape the Role of Research in the Age of AI

Watch this on-demand webinar to learn from how research leaders at Slack, Salesforce, Adobe and Siemens are transforming the way their teams operate in the age of AI.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer vel massa nec orci consectetur maximus. Phasellus tempor eros sit amet imperdiet hendrerit. Duis mollis, sapien nec molestie elementum, velit ante rhoncus leo, sit amet suscipit massa nulla quis neque. Nam vulputate dui posuere urna congue posuere. Nunc tristique condimentum mauris. Nullam elementum orci magna, congue efficitur nulla vulputate elementum. Ut ultrices quam molestie, laoreet diam id, facilisis eros. Etiam metus massa, ultrices non ornare non, facilisis nec lorem. Proin gravida efficitur metus, vel dapibus velit facilisis quis. Aenean ullamcorper purus tellus, sit amet accumsan augue mollis sit amet. Nam vitae lacus condimentum sapien ullamcorper sollicitudin. Ut sollicitudin velit felis, quis pharetra ante molestie sit amet. Ut vulputate, ante at gravida venenatis, lorem leo venenatis urna, nec mollis leo justo vel ipsum. Duis semper, est sed semper ornare, massa odio hendrerit nibh, vel tincidunt sem velit eget erat.

Duis convallis vulputate arcu, vel lacinia urna tempor sodales. Nullam commodo, magna in lobortis semper, lectus risus rutrum elit, eget feugiat arcu elit non turpis. Sed eu fermentum arcu, porttitor bibendum tellus. Curabitur quam nulla, euismod eget sem a, dapibus consectetur arcu. Aliquam erat volutpat. Fusce fringilla porttitor scelerisque. Etiam sodales elit condimentum eleifend pharetra. Mauris blandit enim id felis convallis, ut finibus justo hendrerit.

In this Article

    Read more

    • At Crafted Seattle, leaders explored why human understanding—not AI alone—will determine who builds the products people actually want.

      Blog

      The most valuable skill in the age of AI isn't what you think

      The race to build faster may be obscuring a more important question: Are we...
    • People collaborating while looking at a computer screen

      Blog

      With UserTesting’s MCP server, researchers can stop switching between AI analysis and research tools

      You shouldn’t have to rebuild the same research workflow across five different tools just...
    • person looking at large work screen

      Blog

      How smarter targeting and flexible incentives are advancing research recruitment

      Recruiting and incentivizing the right participants has long been a challenge for researchers—62% of...