How to AI UXR: Crawl, Walk, Run Map for AI in UX Research
Prince Pal Singh · 2026 · An interactive reading

How to AI UXR

A map for building AI-augmented research operations, told as the research workflow changes shape.

Scroll to explore

AI is changing how research gets done.

Not one task at a time.

Across the workflow.

From crawl… to walk… to run.
Chapter 01 — The workflow

Ten familiar stages.

Most research professionals agree the “standard research workflow” has always been inaccurate. Studies rarely progress in a line. Even so, it remains a useful, familiar framework on which to pin something new.

562data points
50research and ResearchOps professionals
3working sessions
5months, Jan–May 2026
{{ s.num }}
{{ s.short }}
Prep · Analysis · Synthesis · Packaging

Linear. Structured. Human-driven. One stage after another.

What happens when AI enters the workflow?

The explosion of Moore’s law
24 months

Moore’s law: computing power doubles roughly every 24 months.

AI agents’ task-solving abilities are doubling roughly every seven months. The workflow compresses with them.

The map is a snapshot in time. Explore the solutions with curiosity and care.

Level 01 Crawl
Level 01 — Crawl

AI augments the individual.

Off-the-shelf LLMs draft, summarise, cluster, and package across the workflow, and serve as a thinking partner.

The work isn’t systematised, and gains are individual and largely unseen at the organisational level. But a significant shift is already under way: steps that used to happen sequentially are being compressed into a single step, or “conversation,” with an AI.

Researcher at the centre
LLM
Transcript
Research plan
Summary
Cluster
Report
Method
Insight

At Crawl, AI behaves like a toolbox, not an autonomous system. Ten tasks, ten accelerators, one researcher.

Crawl · stage by stage Stage 01 / 10
{{ s.num }} Crawl

{{ s.name }}

{{ s.crawl }}

{{ f.arrow }} {{ f.t }}
Human layer {{ s.watch }}
{{ x.t }} {{ x.d }}
The quiet shift

Four stages, one conversation.

“We’re using AI to structurally build and write compelling, actionable insights based on raw transcripts.” A contributor · when research is low-risk, or AI outputs have been properly evaluated

But the gains stay private. Walk begins when private speed becomes shared systems.

Level 02 — Walk

AI becomes a system.

Walk is about building purpose-centred agents, skills, and Retrieval-Augmented Generation (RAG) systems that extend off-the-shelf AI. The focus shifts from individual efficiency to team-level systems, with evaluations, or “evals,” emerging as a discipline in their own right.

Crawl asks “How can AI help me do this task?”
Walk asks “How can we build an environment where research work is continuously supported?”
Agents Skills RAG Repositories Synthetic personas AI moderation Evals
Purpose-built agents

One agent at a time, a network forms.

Custom agents and skills attach to the stages they serve. The gain moves from one person’s speed to the team’s infrastructure.

0agents and skills connected

Teams can query them right where they work, from Slack, without switching platforms.

01Prioritisation
First-pass triageRed-flag planner
02Method
Method selection assistant
03Existing insights
Grounded RAG repositorySubject-matter-expert agent
04Artefacts
Synthetic research assistantInterviewer coaching
05Recruitment
Screener question expertFraud & quality detection
06Collection
Interview copilotBehavioural analysis agent
07Preparation
Makeshift database parsing
08Analysis
Grounded chatbot
09Synthesis
Confidence scoring
10Packaging
Show, don’t tell
Merging into one loop
Grounded RAG repositories

Answers get better when they’re grounded.

Question→ Retrieval→ Evidence→ Grounded response
Research repository
T-04Transcript · trial user, day four
VI-12Validated insight · setup takes longer than expected
S-103Survey · onboarding open responses
MDMetadata · segment, study date, method
A stakeholder asks “What do we already know about why trial users drop off?”
“Probably onboarding friction. Or pricing? Users often find setup confusing.” No sources · untraceable
Two sources point to setup time on day one, rather than pricing.
[T-04] [VI-12]
Every claim links back to its evidence.

RAG systems can make answers more trustworthy, but only if retrieval is good and the system preserves provenance via citations. Illustrative example.

Synthetic personas & AI moderation

Useful for exploration. Not a substitute for evidence.

Real researchpeople
Customer dataevidence
Personawell-researched
Synthetic personaAI model
Simulationvibe check
Data loop: simulated outputs feed back in as inputs
Grounding + periodic reality checks
Prototype under test · Checkout, step 2 of 3
Synthetic persona · ops lead: “Where do I export this?” AI heuristic evaluator: “Button label is ambiguous.”

Teams build synthetic personas from existing, well-researched personas, so designers and PMs can “vibe check” work before building the wrong thing. AI moderators host interviews, with an option for a human to join.

“It can catch simple things we sometimes miss.”A contributor, on AI heuristic evaluators

The risk: black-box insights, and loops that quietly reduce contact with real customer evidence.

The big merge

Analysis, synthesis and packaging become one loop.

Researchers converse with the data through RAG-grounded chatbots, and purpose-built pipelines theme the research and draft actionable insights. AI evals are increasingly crucial.

“The amount of time I spend ‘conversing with my data.’ I think I’ve actually developed a deeper understanding of our users.”A contributor
Level 03 — Run

Research arrives before anyone asks.

Run changes the shape of a research practice entirely. The focus is production-grade research systems designed to anticipate organisational needs and push insights to stakeholders, rather than respond to a brief.

Multi-agent pipelines, automated workflows, and analytics integrations condense the standard workflow into far fewer steps. Because the reasoning behind AI outputs is often invisible, evals become a key operational requirement.

Proactive research

Fromreactiveto proactive.

Product analytics
Customer feedback
Support tickets
Sales notes
NPS
Call transcripts
Research repository
Reddit, App Store
Agent system Monitors for signals across the business. Tagging and data governance keep the stream from turning into noise.
SignalTrial drop-off rises on day four
GapNothing in the library covers enterprise trials
Research opportunityRequest rerouted to the research team, sorted by strategic fit
ActionRelevant insight pushed to the PM before the planning meeting

Illustrative flow, built from the map’s Run practices: continuous insight streams, proactive push delivery, and “Nothing in the library?” rerouting.

Proactive meeting interventions

The research comes to the meeting.

Agents “listen in” to stakeholder meetings and chime in with existing insights or suggest new research initiatives. If a search finds nothing in the library, the agent reroutes the person to request original research.

Product sync · meeting chat · illustrative
PMWhy do trial users drop off on day four?
DesignerWe should really do some research on that.
Research agentThis was studied in February. Three main reasons are in the linked report. There’s a gap on enterprise trials. Request a new study?Open reportRequest study
Multi-agent systems

One agent writes. Two agents argue.

“I created an agentic system with Claude Code: one agent extracts findings from interviews, another generates insights, another checks interviews for missing evidence, and another checks for alternative interpretations.”A contributor
Agent 01 · executionExtracts findingsfrom interview transcripts
Agent 02 · reasoningGenerates insightsfrom the extracted findings
Agent 03 · auditingChecks for missing evidencebuilt to doubt
Agent 04 · auditingChecks alternative interpretationsbuilt to doubt
Agent 05 · executionWrites the reportand learns the researcher’s tone
Agent 06 · executionCreates presentationsposted to repository, chat, or wiki

Agents take functional roles: reasoning, execution, and auditing. The doubt is designed in.

The black box

When steps merge, the reasoning goes dark.

Input →
EVALS TRACEABILITY GROUNDING HUMAN REVIEW
→ Insight

In several places, the sequential steps of the workflow merge into “black box” steps, in which the reasoning that produced the insights is opaque.

The more automated the workflow becomes, the more its outputs must be understood, evaluated, and governed.

Evals · grounding · verification

An AI answer isn’t a finding. Yet.

Claim ↳ Source ↳ Evidence ↳ Review ↳ Validated insight

Grounding constrains output to verified sources: a practical antidote to confident but untraceable output.

Verification checks outputs against original quotes, numbers, claims, and attribution.

Insight · AI-generated · illustrative
Needs review Verified by researcher
“Users struggle with onboarding.”
Evidence
Transcript 04“I gave up setting it up on day one.”
Transcript 12“It asked for things I didn’t have yet.”
Survey 103Open responses mention setup time
Ticket 18Import failed during onboarding
ConfidenceModerate. Criteria: 4 sources, 3 methods
Alternative interpretationDay-four pricing reveal, not setup (T-12)
Contradictory evidenceSeveral Survey 103 respondents describe setup as quick.
Every quote links to its source and timestamp. A researcher signs off.
AI system
Output
Evaluation
Human
Approve · correct · investigate
Back to the system
{{ hitlTitle }} {{ hitlMsg }}
Human-in-the-loop

Where judgement stays essential.

A person must review, approve, or correct AI outputs at particular points before they’re finalised or acted upon. That puts accountability back into the system, especially for high-risk decisions.

Judge.Editor.Researcher.Strategist.Guardian of evidence.
Step into the loop. Decide what happens to the finding.
{{ b.label }}
Risk and quality

Seven risks to manage as you scale AI.

Teams at the cutting edge aren’t anti-AI. They’re building “AI antidotes” into their systems, because skilled humans must remain in the loop.

More automationSpeed. Scale. Efficiency.
=
More operational responsibilityQuality. Consent. Privacy. Bias. Traceability. Verification.
{{ r.d }} Antidote: {{ r.a }}
What changes

Five shifts, from crawl to run.

01Task→SystemFrom “How do I use AI?” to “How does our organisation build research that is faster, safer, and more reusable?”
02Reactive→Proactive“The insights are great, but too late” becomes a complaint of the past.
03Individual→OrganisationGains move from private chat windows to team- and organisation-level systems.
04Sequential→MergedPreparation merges with analysis, then analysis, synthesis, and packaging become one loop.
05Answer→Evaluated insightBlack-box outputs require systematic evaluation before they become findings.
The researcher’s role

The role is changing. It isn’t disappearing.

CrawlResearcher using AI toolsOff-the-shelf tools augment individual tasks. The workflow stays largely intact.
WalkResearcher designing AI-supported systemsAgents, skills, and RAG built for the team, with evals as a discipline in their own right.
RunResearcher designing, evaluating and governing agentic systemsFrom moderator to agentic system designer. ResearchOps can no longer work from the sidelines: it needs a clear understanding of research craft.
Threads that run through every level
The emergent make phase
Insight→Prototype→Change→Measure→New signal↺
Researchers vibe-code functional prototypes, co-create with participants, fix low-risk UI issues, and share insights in the language of designers and PMs.
Democratisation
ResearchDesignerPMEngineerMarketingLeadership
Agents, repositories and self-serve tools widen access to research. Governance, evidence and research craft still decide what’s trustworthy.
ResearchOps: the operating layer
Governance · data · repositories · templates · agents · evaluation · metadata · privacy · workflow · automation The map has no separate ResearchOps section, because AI makes the whole workflow systematisable. It’s all operations.
The full map

Crawl, walk, run: one control.

Drag across the maturity levels and watch ten stages connect, merge, and collapse into an agentic system. Select a stage to compare what changes at each level.

{{ l.n }}
Crawl · toolsWalk · systemsRun · ecosystem
{{ s.short }}
Analysis · Synthesis · Packaging
Agentic systemHITL · evals · grounding
Stage {{ cur.num }} · viewing {{ lvlName }} {{ cur.name }}
Watch for{{ cur.watch }}
Practices at {{ lvlName }}
{{ e.t }}
{{ l.n }} {{ l.text }}
Glossary

The words that decide what you can trust.

Read the glossary as a set of warning labels: almost every entry comes with a “but.” Select a term to see what it connects to.

Where it appears · {{ gsel.where }} {{ gsel.t }} {{ gsel.def }}
Why it matters{{ gsel.why }}
Connected to

AI isn’t simply accelerating research tasks.

It’s changing the shape of the research system.

And the deeper the automation goes, the more judgement, evidence, evaluation, and research craft matter.

How to AI UXR Explore the workflow

Source: How to AI UXR, produced by Kate Towsey for The ResearchOps Review with the support of Strella. 562 data points gathered January–May 2026. © The ResearchOps Review, 2026.

This is an interactive reading of the map. The original map remains the source of truth. Scenario examples marked “illustrative” were written to demonstrate practices described in it.