Survey of 521 UX Practitioners Finds AI Saves Time but Breeds Distrust
A survey of 521 UX practitioners found near-universal AI access and real time savings, yet 69% of open comments carried negative sentiment, driven by mandates and unreliable output.
- AuthorTom Whitfield
- ChannelUX Research
- Filed
- Read4 min

- 521 UX practitioners surveyed Aug 24–Sep 11, 2026; over 99% had AI access, 66% used agentic AI.
- Average task-time effect rated 4.2 of 5, but overall sentiment was only 3.57 of 5.
- Top adoption barriers: output quality (54%) and data privacy/security (50%); only 9% reported none.
- 69% of the 226 open-ended comments expressed negative sentiment; 41% purely negative.
- PMs rated job security 3.81/5 versus 2.94 for researchers and 2.99 for designers (p < 0.05).
A survey of 521 UX practitioners, run from August 24 through September 11, 2026, found that AI shortens every task it touches — yet 69% of respondents who left open-ended comments expressed negative sentiment, often about mandates and unreliable output. Access to generative AI was near universal at over 99%, but enthusiasm was not.
The research team collected 2,814 raw responses through a practitioner panel, a newsletter, invite-only Slack communities and LinkedIn advertising. After removing incomplete and bot responses, plus practitioners not currently employed, 521 complete responses remained: 246 designers, 145 researchers, 21 product managers and 109 others, including content designers, ops practitioners and developers. Almost half worked at enterprises; only 4% worked at startups.
What does access look like in practice?
Most respondents (59%) could use only an approved set of tools; just 12% chose tools freely. Agentic AI — agents such as Claude Cowork or coding agents like Cursor — was used by 66%, with each category separately near 48%. Adoption split sharply by organization: 85% at startups and 75% at small and mid-sized businesses, against 36% at nonprofits and 42% in government. Product managers and ops professionals used agentic tools most; researchers and content designers least.
One startup employee explained his choice of employer in a follow-up interview: "I really wanted to go into a company that will be building stuff from the ground up, where AI is embedded everywhere."
What blocks adoption?
Only 9% reported no barriers. Output quality led (54%), followed by data privacy and security (50%). More than a third (34%) cited ethical or sustainability concerns — data-center energy use, job-market effects, surveillance, and training data taken without creators' consent. Lack of executive buy-in ranked last, and the comments explain why: pressure flows the other direction. One respondent wrote: "The biggest change is the constant push from management to use it more and more. I have to actively push against them on things I know AI doesn't do well yet."
Another captured the moral conflict: "It's a strange feeling to be forced to use something that I do not believe in."
Where does AI save time — and where does it not?
Respondents rated AI's effect on task time at 4.2 out of 5 on average, where 3 means no difference. Use concentrated in desk work: 73% often or always used AI for writing or editing code, 69% for desk research, 67% for analyzing their own research data. Around nine in ten users of those tasks reported speed gains.
Human-facing work lagged. Most respondents never used AI for interviewing users (61%) or testing designs with users (51%); sessions themselves resist compression. Only 11% used AI interviewers, and the same share used synthetic users. Design critique similarly benefits little, because judging a design requires context that is hard to convey to a model reliably.
Why does faster work not mean happier workers?
Mean sentiment was 3.57 out of 5 — statistically above neutral, barely. Of 521 respondents, 226 answered the optional final question; 69% of those comments carried some negative sentiment and 41% were purely negative. Researchers left purely negative comments at a significantly higher rate than designers (51% versus 33%).
Of 155 negative comments, coders assigned reasons to 149. The most common was unreliable output and the labor of checking it. Mandated, tracked usage produced performative adoption: "I now sometimes find myself trying to quickly fix completely unusable prototypes made by a product manager." Others cited inflated expectations: "Leadership expects faster work and designers to be able to do more, but AI output quality does not support that yet."
Positive comments (49% of the total) most often cited speed and new capabilities — coding, complex data work, confidence for solo practitioners. Of 61 comments mentioning productivity gains, 26 also carried negative sentiment.
What does this change for job security?
Some 65% expected their roles to remain important or grow; 18% expected shrinkage. Product managers rated their security highest (3.81 out of 5, n=21) versus 2.94 for researchers and 2.99 for designers. Government employees, at 3.86, felt significantly more secure than private-sector peers. One former designer turned PM predicted consolidation: "I see product managers and UX merging. Because one person can do much more. Before, you needed 3/4 people for the same thing."
The authors' conclusion is systemic: task-level speed gains can become system-level losses when a prototype generated in minutes costs a designer days to make usable. They argue leaders should measure whether work reaches users faster and better, treat AI output as a draft, and open room to discuss ethical costs — a baseline they expect to shift as tools and organizational practice mature.
Original: nngroup.github.io
More from Tom Whitfield
Show full bio
Correspondent covering companies, deals and strategy in Product and interaction design, design systems at Interface Wire.
65 articles