What gets lost when UX research speeds up
AI has made research workflows faster. Understanding users is a harder problem.
I’ve been working in product research for a while now, and something has shifted noticeably over the past couple of years. The requests we get from stakeholders have changed. The way we conduct research has changed. Even the way teams consume the insights we share has changed. I’ve been talking to friends in UX and they’re noticing similar things. The pace is different, the expectations are different, and the role itself feels like it’s being renegotiated in real time.
Some of this is genuinely positive. But some of it concerns me, and I don’t think we’re talking about it honestly enough.
Everything is faster — including the parts that shouldn’t be
The most immediate change is pace. Timelines for planning and conducting research have shortened dramatically. Stakeholders expect faster turnaround on everything: the research plan, the interview guide, the analysis, the report. AI tools have made some of this possible, and the efficiency gains are real — 58% of product professionals now use AI in their research workflows, up from 44% in 2024 (Maze, 2025), with researchers reporting faster turnaround times and more streamlined analysis.
The problem is that speed and rigour are not always compatible, and some parts of research resist compression more than others.
Thematic analysis is a good example. Done properly, it takes time. You need to sit with the data, read and reread transcripts, let patterns emerge rather than impose them. Many researchers deliberately leave a gap between data collection and analysis for this reason — the patterns you notice on day three are often different from the ones you notice on day one. In many product environments, this kind of reflection can easily appear inefficient or difficult to justify. In reality, this is how qualitative analysis works (e.g., obtaining insight is embedded in a dynamic relationship between researcher and data, Hitch, 2024). Rushing it, or outsourcing it entirely to AI, does not produce the same output faster. It produces a different, shallower output. A series of studies from practitioners(e.g, Luna, 2026) and academics (e.g., Ozuem et al., 2025, Nguyen-Trung, 2025) have repeatedly found that AI-generated themes tend to be surface-level — technically accurate but missing the deeper context behind what participants are actually saying. For example, an AI-generated synthesis might conclude that “users value simplicity” or “participants want clearer workflows”. Technically, those themes may be present in the data, but a human researcher may notice that what participants are actually expressing is anxiety about making expensive mistakes, fear of appearing incompetent, or uncertainty about organisational expectations. The surface theme is not necessarily wrong, but it is often incomplete.
The cumulative effect of this is researchers who are stretched thin, moving from one study to the next without adequate time to think. Add continuous research and non-stop stakeholder demand to the mix and you have a reliable recipe for burnout. Lyssna’s 2026 research trends report based on data from 100 researchers found that 21% identified balancing speed with research quality as their single biggest challenge.
Polished outputs are not the same as good research
There is a related problem with democratisation. AI tools now allow product managers, designers, and other non-researchers to create research artefacts that look professional — surveys, discussion guides, even synthesised insight reports. This sounds like a good thing and it can be. In practice, however, it is not straightforward.
A survey created by someone without research training might look polished while containing leading questions, poorly ordered items, or response options that introduce systematic bias. The problem is that it is increasingly difficult to tell the difference at a glance. Takafoli, Li, and Mäkelä (2024), in interviews with 24 UX practitioners, found that most companies have no formal policy or governance around AI use in research. Individuals are making their own decisions about what constitutes good enough, with limited organisational oversight.
This matters because research quality is not always visible in the output. A well-designed study and a poorly-designed one can produce reports that look similar. The difference shows up in whether the findings are actually valid — and by the time anyone realises that, decisions have already been made on the basis of them.
The slow disappearance of methodological rigour
The changes to how research is communicated worry me in a similar way. Long reports are increasingly unpopular — 71% of researchers experimented with new formats for sharing insights in 2025 (User Interviews, 2025), and the trend is firmly toward shorter, snappier outputs. Slide decks, one-pagers, short video summaries, even podcasts. There is nothing inherently wrong with adapting communication formats to your audience (throwback to my article on UX Research Bingo). Stakeholders are busy. Long reports are boring. Getting findings read and acted on matters as much as conducting good research.
But something is being lost in the process. Traditional research reports, whatever their faults, typically documented methodology, sampling decisions, and limitations. They made explicit what the research could and could not reasonably conclude. Increasingly, these are being dropped in favour of outputs that lead with punchy headlines and actionable recommendations. The result can look like research and sound like research while missing some of the scaffolding that makes research trustworthy.
Research is grounded in the scientific method. Methodology matters. Limitations matter. Not because stakeholders want to read about them — they largely do not — but because they are what distinguish a genuine finding from a plausible-sounding assumption. When we stop including them, we may make research outputs easier to consume, but also harder to interrogate and easier to misuse. We are making it harder to interrogate, and easier to misuse. The risk is that research becomes performative — the appearance of insight without the methodological depth underneath it.
There is also another thing to be mindful of here. Stakeholders are increasingly using AI tools to summarise research outputs rather than reading them directly. A report with its context, caveats, and interpretive framing gets compressed into a bullet-pointed digest. The nuance that distinguishes a useful finding from a misleading one often does not survive that compression. This specific behaviour is not yet well documented in the research literature — it is more observable at the practitioner level — but it has direct consequences for how findings get applied downstream.
The structural picture
None of this is happening in a vacuum. The conditions under which researchers are doing this work have also changed. Whatever the efficiency gains, researcher sentiment tells a different story: 49% of researchers felt negatively about the future of UXR in 2025, a 26-point increase from 2024, with 67% giving a negative outlook on career opportunities (User Interviews, 2025).
The job market reflects this. According to Indeed data analysed by Brookshier and Altenhoff (2026), UX and product design job postings dipped below their pre-pandemic baseline in Q3 2023 and have not meaningfully recovered. Listings for UX research roles specifically fell below 1,000 in early 2025 (Burgess, 2025). 35% of organisations reported reducing UX staff in a MeasuringU survey. Perhaps most telling: the ratio of people who do research to dedicated UX researchers has shifted from 2:1 in 2020 to 5:1 in 2025 (UX Magazine, 2025). More research is happening. Less of it is being done by researchers.
Demand for research outputs is rising — 55% of respondents in Maze’s 2025 report said demand has increased, and 87% of organisations say they use research to inform critical decisions. But rising demand does not automatically mean better conditions for doing research well. When headcount shrinks and timelines compress, the research that gets done tends to be faster and lighter.
What we risk losing
AI is a genuinely useful tool for many parts of research work. The efficiency gains in transcription, recruitment, and initial data organisation are real and valuable. Used well, AI should free researchers to spend more time on the work that requires human judgement — the interpretation, the contextual reading, the synthesis that produces insight rather than just information.
The problem is that this is not necessarily what is happening in practice. Instead of using AI to create space for deeper thinking, we are using it to do more in less time. The deep thinking is what’s at risk of being cut. And that thinking — the unhurried reading of transcripts, the pattern that only becomes visible on reflection, the finding that reframes the whole project — is where the actual value of research lives. For many of us, that interpretive work is part of what made research meaningful in the first place.
Lu et al. (2024), in a systematic review of 359 papers on AI and UX, make this point directly: UX research is fundamentally about building empathy with users, not completing tasks. Automation that treats research as a series of completable tasks misses this. AI may surface statistically probable information about users. That is not the same as understanding them.
The researchers who will be most affected by these trends are not those in senior, embedded roles with strong organisational influence. It is those earlier in their careers, or in organisations where research has always been treated as a support function. The “AI elevates the researcher” story is largely being told by people who were already elevated.
What we can do about it
None of this is straightforward to address. The pressures are structural, not personal, and individual researchers cannot reverse them alone. But there are things worth doing.
The first is to be honest about trade-offs rather than just delivering outputs. If a study was conducted faster than the methodology strictly allows for, say so. Stakeholders who understand the difference between a directional finding and a validated one are better positioned to make decisions. Researchers who are transparent about this are also harder to blame when fast research produces uncertain answers.
The second is to protect methodology even in short outputs. You do not need a five-page methods chapter in every report. You do need enough context for the reader to understand what the findings can and cannot conclude. That is what separates researcher-led work from AI-generated research-shaped content.
The third, and perhaps most important, is to use expertise to advise, not just deliver. Fast and light research is sometimes the right call. Continuous discovery, quick directional studies, lightweight validation — these have a legitimate place in the research toolkit. The problem is not speed itself, it is speed applied indiscriminately. Researchers are best placed to judge what a given question actually requires, and that judgement is worth making explicit. Recommending the right method for the right moment, including sometimes a faster one, is part of the role. So is pushing back when the timeline makes meaningful research impossible.
Picking those battles carefully, and making the case with evidence rather than principle alone, is probably the most useful thing researchers can do right now.
How are you experiencing these changes in your own practice? I’d be interested to hear in the comments.



I was asked to reduce the UX process by at least 30%. We conducted a pilot focused on the login flow of a banking app and successfully achieved the target reduction.
However, the next challenge is aligned with your post: helping stakeholders understand that optimizing a “user login” flow is fundamentally different from designing an “investment onboarding” experience.
A login flow is usually transactional, repetitive, and low-cognitive-load. Opening an investment account involves trust-building, compliance, risk disclosure, financial decision-making, and significantly higher cognitive effort from the user.
In other words, UX optimization is not an assembly-line exercise where every flow can be standardized equally. We are not manufacturing identical processes at scale — we are designing contextual and personalized digital experiences. Sometimes we will be 30% down from a media, and some others 30% up!
I'm thinking on going inside the ux phycholog and reaserch and after reading your substack I'm second guessing my choise
I have written this about my behaviour when watching YT what so you think
https://shikharshukla26.substack.com/p/youtube-is-not-your-problem-tomorrow?utm_source=share&utm_medium=android&r=8h8wp7