How is AI used in UX design?

AI is used across several stages of the UX design process. Designers use it to synthesise user research faster, generate content and microcopy, produce rough layout variants for review, and identify patterns in large datasets. Tools such as Dovetail, Figma AI, and general-purpose LLMs are now part of many design workflows. The key distinction is that AI accelerates execution tasks - it doesn't replace the judgement required to frame problems, run research with real users, or evaluate whether a design is right for a specific context.

Will AI replace UX designers?

No - not in any near-term timeframe, and not in the ways that matter most. AI can't conduct user research, identify the right problem to solve, or make ethical design decisions about what to build. What it does change is the balance of tasks within the role: the parts that were previously slow and mechanical are now faster, which raises the premium on the skills that remain hard to automate - research with real people, problem framing, and strategic design thinking.

What AI tools do UX designers use?

The most commonly used AI tools in UX design workflows include Dovetail and Notion AI for research synthesis, Figma AI for layout generation and design variants, and general-purpose LLMs such as Claude and ChatGPT for microcopy and ideation. Tools like Galileo and Uizard can generate rough screen layouts from prompts. The landscape is changing quickly; the most useful approach is to evaluate each tool against the quality of work it produces rather than adopting everything at once.

Do UX designers need to learn AI?

Yes, and for two reasons. First, AI tools are now part of standard UX workflows and being unfamiliar with them creates a practical disadvantage. Second, more and more products include AI-powered features - conversational interfaces, generative content, predictive personalisation - and designing these experiences well requires specific knowledge about transparency, user control, and error states that most existing UX frameworks don't cover. Designers who understand both how to use AI tools and how to design AI-powered products are increasingly in demand.

AI in UX Design: What Actually Changes (and What Does Not)

AI is doing something genuine to UX design. It's shifting what the job looks like in practice - and raising the stakes on the skills that have always mattered most.

This post covers two distinct things that often get muddled together: AI as a tool inside the UX workflow, and AI as a product challenge that UX designers now have to solve for. Both matter. They require different thinking.

AI as a tool in the UX workflow

Let's be direct about what AI tools are actually useful for right now.

Research synthesis is where designers are seeing the biggest gains. Analysing interview transcripts, spotting patterns across survey responses, organising affinity data - these are tasks that used to take hours and can now take minutes. Tools like Dovetail, Notion AI, and general-purpose LLMs can surface themes, suggest codes, and flag contradictions in raw data at a speed no human can match.

The important caveat: the synthesis is only as good as the research. AI can't tell you whether you asked the right questions, whether your participant sample was representative, or whether you missed something critical because you were looking in the wrong place. The judgement call still belongs to you.

Ideation and concept generation is genuinely useful at the divergent phase. Feeding a design brief into an LLM and asking for 20 solutions - including ones that feel unreasonable - is a fast way to break out of first-idea thinking. AI doesn't have taste or strategic awareness, but it doesn't run out of ideas the way humans do after a long workshop.

Content and microcopy is another area where AI earns its place. Generating first drafts of error messages, button labels, onboarding copy, and empty states is now a reasonable starting point. Refining them for tone, accuracy, and brand voice still takes a human. But the blank-page problem largely goes away.

Prototyping speed is improving. Tools like Figma AI, Galileo, and others can generate rough layouts from prompts, resize components, and produce variants automatically. These aren't finished designs - they're starting points. But they compress the time between "I have an idea" and "I have something I can put in front of a user."

For a practical rundown of what's worth using today, our guide to AI tools for UX designers covers the current landscape with honest assessments of where each tool earns its place.

None of this is magic, and none of it removes the need for good UX thinking. What it does is compress the time on tasks that were previously just slow. That matters, because it frees up time for the work that's harder to automate - the conversations with real users, the problem reframing, the strategic decisions about what to build at all.

For a grounding in the research skills that remain irreplaceable, see what UX research actually looks like in practice.

How to actually prompt AI for UX work

Using AI well in a UX workflow isn't just about which tool you pick -- it's about how you ask. Natalia Veretenyk, our lead instructor, teaches a simple framework for prompting on design tasks: state the AI task, give it the product context, and state the business goal. Skip the context and the goal, and a prompt tends to come back generic -- technically correct, but not useful for the actual product in front of you.

She walked through this live with a worked example: a fitness app that helps users find workouts tailored to their goals. The starting point was the product context -- a new user who has just joined and isn't sure which workout is right for them -- and the business outcomes that matter: reduce early drop-off, increase repeat workouts, and help a new user activate their account. From there, the prompt itself became specific: ask the AI to suggest onboarding steps for a fitness app that help a first-time user feel more confident about choosing the right workout for their goals, while increasing the number of users who finish onboarding and keep using the app.

That single prompt carries all three pieces at once -- the task (suggest onboarding steps), the product context (a new, unsure user, a fitness app), and the business goal (finish onboarding, keep using the app). Strip any one of those out and the output drifts toward generic advice that could apply to almost any app. Put them all in, and the AI has something real to work with.

Designing AI-powered products

This is where the real design challenge lives, and it's newer territory.

More and more products now include generative text, conversational interfaces, predictive features, or AI-driven personalisation. Designing these experiences well is a specific skill set - and most of the existing UX playbook doesn't cover it adequately.

Conversational and generative interfaces don't behave like traditional UIs. Users can't see a menu of options; they have to know what to ask for. The interface has no fixed state - outputs vary, and users need to develop a mental model of a system that doesn't always behave consistently. Designing for this means thinking carefully about discoverability, prompt guidance, and how to help users get useful results without requiring them to become prompt engineers.

Designing for trust is now a core UX problem. When a product surfaces a recommendation, generates a summary, or makes a prediction, users need to be able to calibrate how much to trust it. That means showing your working - where did this come from, how confident is the system, what's the basis for this output. Opacity breeds either blind trust or blanket scepticism, neither of which serves users well.

Transparency and explainability aren't just ethical nice-to-haves. They're functional design requirements. A user who doesn't understand why they were shown something, or why the system behaved in a particular way, can't make good decisions about whether to act on it. Designing explanations that are accurate without being overwhelming is genuinely hard.

Error states and failure modes in AI systems are different from conventional software errors. An AI component doesn't return a 404 or crash cleanly - it produces output that may be subtly wrong, overconfident, or simply unhelpful. Designing for this means being honest with users when the system is uncertain, giving them ways to correct or override outputs, and avoiding interfaces that make it easy to accept bad outputs without scrutiny.

User control is the thread running through all of this. Good AI UX gives users meaningful agency over what the system does and doesn't do. That might mean easy opt-outs, persistent preferences, the ability to see and edit what the system knows about them, or simply clear ways to undo AI-generated actions. Control isn't a feature - it's a design principle.

These patterns are still being worked out across the industry. There's no settled canon yet, which is both a challenge and an opportunity for designers entering the field now.

What AI doesn't replace

It's worth being direct about this, because the discourse swings between hype and panic and neither is useful. For a grounded take on the displacement question, see our dedicated post on whether AI will replace UX designers.

Research with real people isn't replaceable. AI can analyse existing data, but it can't have a conversation with a frustrated user and notice the thing they aren't saying. It can't observe someone struggle with a task and understand what that struggle reveals about their mental model. Generative AI produces outputs based on patterns in training data - it can't tell you what your specific users, in your specific context, actually need.

Problem framing is the most valuable UX skill and the hardest to automate. Before you design anything, you need to identify the right problem to solve. That requires talking to people, understanding context, challenging assumptions, and often convincing stakeholders that the problem they think they have isn't the one that needs solving. No prompt does this for you.

Design judgement - knowing when something is good enough, when to push back on a brief, when an interaction pattern is technically correct but experientially wrong - develops through practice and can't be generated. AI tools can produce outputs; they can't evaluate whether an output is right for a given situation.

Ethical reasoning isn't a feature that can be added later. Designers working on AI-powered products are now in a position where the decisions they make about what to surface, when, and how have real consequences for real people. That responsibility requires human judgement.

How designers should adapt

The practical answer is this: use AI to compress the time on tasks that used to be slow, and reinvest that time in the skills that matter more as AI gets better.

Use AI for first drafts, not final outputs. Treat AI-generated research synthesis as a starting point, not a conclusion. Stay curious about new tools, but evaluate them against the quality of work they produce, not the sophistication of the demo.

Double down on research with real people, because that's where the insight gap will open up between designers who take shortcuts and designers who don't. Double down on communication and facilitation, because the ability to involve stakeholders, run good workshops, and present findings clearly becomes more valuable as the "making" part of the job gets faster. Double down on problem framing, because the organisations that use AI well will be the ones that start with the right questions.

If you're learning UX now, or considering a career change into the field, the AI moment isn't a reason to hesitate - it's a reason to develop a broader skill set. Designers who understand both how to use AI tools and how to design AI-powered experiences are increasingly in demand, and that gap isn't going to close quickly.

To understand what the full UX design skill set looks like, what's UX design covers the foundations. The full course catalogue shows how these skills are taught in a structured programme.

The skills that matter now

The headline skills for UX designers in 2026 aren't fundamentally different from what they have always been - they're just more important:

User research - the ability to learn from real people, not just from data
Problem framing - identifying the right question before committing to an answer
Systems thinking - understanding how a design decision affects the broader experience
Communication - presenting findings, building alignment, and advocating for users
Ethical reasoning - recognising when a design decision creates harm or erodes trust

To these, add the capability to evaluate and use AI tools critically, and to design AI-powered experiences with transparency and user control at their core.

None of this is simple. Uncertainty is genuine - the tools are developing faster than the best practices, and some of what looks settled now will look different in two years. The designers who will handle that well are the ones with strong fundamentals.

The UX Academy (myuxacademy.com) Beginner UX (AI) Design course is now open. It covers AI tools in the UX workflow and designing AI-powered product experiences - the two areas this post has explored. Cohorts start on 14 October 2026 and 12 January 2027. Reserve your place from £99 (refundable deposit), with the balance due before the course begins.

If you want to see how we teach before committing, book a free 15-minute call with an advisor to talk through what the field actually looks like and whether a career in UX is the right move for you.