The unglamorous half of UX work is where AI helps most: transcribing interviews, tagging quotes, writing the fourth version of an error message, building the throwaway prototype for a usability test. A chat assistant clusters 40 interview quotes into cited themes in a minute. Figma's AI features draft a first-pass screen and rename your layers, and prompt-to-app tools such as v0, Lovable, and Figma Make produce a working prototype for tomorrow's session (availability moves fast; check your plan).
What it does not do is know your users. Models produce the average interface for a problem, the average persona, and the average copy, and they will invent research findings if you let them. The craft shifts toward asking better questions, running honest studies, and editing generated work with taste and an accessibility checklist in hand.
Two obligations come with the tools. Research participants must consent to how their recordings and words are processed, including by AI vendors. And generated interfaces need the same accessibility rigor as any other, because they routinely ship with poor contrast, missing labels, and keyboard traps.
Quick wins this week
- Paste a consented, anonymized interview transcript and ask for themes, each backed by verbatim quotes with timestamps, plus the questions the interview raised but did not answer.
- Give the assistant a screenshot of a flow and ask for the friction points a first-time user would hit, the error states you have not designed, and the microcopy that needs work; then decide which are true.
- Draft five versions of an empty-state, error, or confirmation message at different tones and lengths, and pick the one that fits your voice guide.
- Build a clickable prototype with v0, Lovable, or Figma Make for a usability session, then throw it away afterward; it is a research instrument, not the product.
What AI can do for ux designers, task by task
Research synthesis and affinity mapping
Give anonymized transcripts and your research questions and ask for themes with supporting quotes, counter-evidence, and the participants behind each theme, so you can see whether a theme is three people or one loud one. Check every quote against the source; models paraphrase and occasionally fabricate. Miro's AI features can cluster sticky notes as a starting point for the affinity map.
UX writing and microcopy
Paste your voice and tone guide, the screen context, the user's likely emotional state, and the constraints (character limits, localization, reading level) and ask for options with rationale. Check for plain language, no instructions that rely on color or position, and no promises the product cannot keep. Read it aloud; models write copy that scans but sounds like no one.
Flows, states, and first-draft screens
Describe the task, the user, the entry points, and the edge cases, and ask for a step-by-step flow with decision points and the states each screen needs (empty, loading, error, success, permission denied). In Figma, AI can draft a first-pass layout to react to; treat it as a sketch, not a design. Watch for flows that skip the unhappy paths.
Prototyping for tests with prompt-to-app tools
Describe the screens and the one interaction you want to test and let v0, Lovable, or Figma Make build a clickable version; iterate by prompt until it is good enough for a session. Use fake data, never real customer records, and run an accessibility check before testing with participants who use assistive technology. Prototype code does not become the product without an engineer's review.
Usability test planning and analysis
Paste the research goals and the prototype description and ask for a moderator guide with tasks, success criteria, follow-up probes, and a consent script that names the tools that will record and process the session. Afterward, give the transcripts and ask for task-by-task findings with severity and evidence. Set severity yourself; the model does not know which failures block real work.
Accessibility review and design QA
Give the screen, its states, and the intended keyboard and screen-reader behavior and ask for a WCAG 2.2 AA review: contrast, focus order, labels, target size, error identification, motion. Then run a real checker (axe, a Figma contrast plugin, a screen reader), because the model cannot see rendered contrast or tab order; it reasons from your description. Use it to draft alt text and annotations for engineers.
Prompts for ux designers
Replace the bracketed placeholders, paste into any chat assistant, and iterate on the result.
Synthesize interviews into evidence-backed themes
You are a senior UX researcher. Research questions: [LIST THE QUESTIONS]. Below are anonymized transcripts from [NUMBER] participants, labeled P1 onward. Identify the themes that answer each question. For each theme: a one-sentence statement, the participants who support it, two verbatim quotes with participant label and timestamp, any counter-evidence, and your confidence given how many raised it. Then list surprising findings that do not fit the questions, and the questions the data cannot answer. Do not paraphrase quotes or infer feelings that were not stated. Transcripts: [PASTE THE ANONYMIZED TRANSCRIPTS]
Tip: Spot-check three quotes per theme against the recording; paraphrase creeps in.
Generate screen states and flow edge cases
You are a product designer reviewing a flow before handoff. Feature: [FEATURE NAME AND GOAL]. User: [WHO, THEIR CONTEXT, AND DEVICE]. Entry points: [WHERE THEY COME FROM]. Happy path as I have it: [DESCRIBE THE STEPS]. List every screen state I need (empty, loading, partial, error types, success, permission, offline, limits) with what the user sees and can do in each. Then list edge cases and unhappy paths in order of how often real users will hit them, and the decision points where the flow branches. Flag anything in my happy path that would confuse a first-time user. Output as a table I can paste into Figma or Miro.
Tip: The state list becomes your handoff checklist; engineers will thank you.
Write microcopy options in our voice
You are a UX writer. Voice and tone guide: [PASTE OR SUMMARIZE THE GUIDE]. Screen: [DESCRIBE THE SCREEN AND WHAT JUST HAPPENED]. User state: [WHAT THEY ARE TRYING TO DO AND HOW THEY LIKELY FEEL]. Constraints: [CHARACTER LIMIT, READING LEVEL, LOCALIZATION NOTES]. Write five options for [ELEMENT, FOR EXAMPLE THE ERROR MESSAGE OR EMPTY STATE], each with a one-line rationale. Use plain language, say what happened and what to do next, make no promises the product cannot keep, and do not rely on color or position words. Then say which option you would ship and why.
Tip: Read the winner aloud; if it sounds like a robot apologizing, keep editing.
Plan a usability test with a consent script
You are a UX researcher planning a moderated usability test. Goals: [WHAT WE NEED TO LEARN]. Prototype: [DESCRIBE IT AND WHAT WORKS]. Participants: [WHO AND HOW MANY]. Session length: [MINUTES]. Recording and tools: [WHAT WILL BE RECORDED AND WHICH AI TOOLS WILL PROCESS IT]. Write: a consent script covering recording, data storage, which AI tools process it, how to withdraw, and that participation is voluntary; a warm-up; four to six tasks with scenarios, success criteria, and follow-up probes; a debrief. Tasks must not lead the participant or use the interface's own labels. Add a note on accommodations for participants who use assistive technology.
Tip: Have legal or research ops review the consent language; requirements vary by organization and jurisdiction.
Review a screen against WCAG 2.2 AA and heuristics
You are an accessibility specialist and UX reviewer. Screen: [DESCRIBE THE SCREEN, ITS ELEMENTS, COLORS WITH HEX VALUES, AND STATES]. Intended keyboard behavior: [DESCRIBE]. Intended screen-reader behavior: [DESCRIBE THE ANNOUNCEMENTS]. Review against WCAG 2.2 AA (contrast, focus order and visibility, labels and names, target size, error identification and suggestion, motion, timing) and against Nielsen's heuristics. For each issue: criterion, what fails, who it affects, a fix, severity. Say what you cannot assess from a description and must be tested with a tool or a screen reader. End with alt text and ARIA annotations for the engineer.
Tip: A checklist generator, not a compliance check; run axe and a screen reader before you sign off.
Want a prompt for something else? Use the Prompt Builder.
Skills to build
Research ethics for AI-processed data
Why: Participants consented to talk to you, not necessarily to have their recording processed by a third-party model, and trust is the whole basis of research.
How: Name the tools in your consent form, anonymize before pasting, use vendors with no-training terms, store transcripts under your retention policy, and let participants opt out of AI processing.
Accessibility as a default check
Why: Generated screens, code, and copy routinely fail contrast, labeling, focus order, and target size, and the model cannot see what it produced.
How: Keep a WCAG 2.2 AA checklist next to every generated artifact, test with a screen reader and keyboard, and learn to read the ARIA in prototype code.
Prompting with evidence, not adjectives
Why: 'Make it modern and clean' returns the same interface everyone else got; findings, constraints, and examples return something for your users.
How: Paste research findings, brand and voice guides, and two examples of what good looks like into every generation prompt, and keep them in a Claude Project or a custom GPT.
Editing generated work with taste
Why: The model's output is the median; your value is knowing which parts to keep, cut, and rethink.
How: Generate several options, critique them against your design principles before picking, and keep a file of the edits you made so you can see your own patterns.
Reading prototype code
Why: Prompt-to-app tools produce real code, and engineers will ask whether it can ship; you should be able to say what it does and where it is fragile.
How: Ask the assistant to explain the generated component tree and state handling, learn the basics of HTML semantics and ARIA, and pair with an engineer on the first handoff.
Tools worth knowing
Figma
The standard interface design tool, now with AI for prototypes, layout chores, and copy
Claude
A careful writing and analysis assistant that shines on long documents.
ChatGPT
The general-purpose AI assistant most of your coworkers already use.
Miro
Shared whiteboard for workshops and planning, with AI to cluster, summarize, and draft
v0
Describe a web interface and get working React code you can preview, edit, and deploy
Lovable
Describe a web app in chat and get a working, hosted product with a database and login
Cautions for ux designers
Interview recordings, transcripts, and screen captures are personal data from identifiable people, sometimes customers under contract. Get explicit consent that names the AI tools you use, anonymize before processing, use vendors with no-training or zero-retention terms, honor opt-outs, and never paste research data into a consumer AI tool unless your organization has approved it.
Ask for a persona, a survey result, or a quote and the model will produce one that never existed. Synthetic users are not research participants, and generated findings presented as research is misconduct in most organizations. Require evidence labels on every generated claim and keep AI-drafted artifacts clearly marked until they are validated.
Generated screens and code frequently ship with low contrast, unlabeled controls, missing focus states, small targets, and motion without a reduce-motion path, and the model cannot see rendered output. Test every generated artifact with an automated checker, a keyboard, and a screen reader, and put accessibility in the prompt as a requirement rather than a cleanup step.
Generated designs and images can echo existing products and copyrighted work, and pasting a competitor's screens into a prompt to 'make ours like this' raises the same issue. Use generated output as sketches, check image tools' commercial-use terms, keep brand assets out of consumer tools, and follow your organization's policy on AI-generated visuals in shipped products.
Your 30-day plan
- Week 1: Update your research consent language to name AI tools and opt-outs, confirm which assistants and plans are approved, and load your voice guide and design principles into a project or custom assistant.
- Week 2: Synthesize one past study with the themes prompt and compare against your original findings to see where it helps and where it fabricates.
- Week 3: Generate states and microcopy for one feature in progress, run the accessibility review prompt, then verify with axe, a keyboard, and a screen reader.
- Week 3: Build a throwaway prototype with v0, Lovable, or Figma Make and run one usability session with it, using the consent script.
- Week 4: Write your team's norms: what AI may draft, what must carry evidence labels, how prototypes are handled at handoff, and where generated visuals are off limits. Share the prompts that worked.
Frequently asked questions
Will AI replace UX designers?
Can I use AI to synthesize user interviews?
Are synthetic users a substitute for user research?
How do I make sure AI-generated interfaces are accessible?
Terms used on this page
Related roles
- AI for Graphic DesignersGenerative tools now live inside Photoshop, Illustrator, Canva, and Figma. Here is how working designers use them for exploration and production grunt work, and how to answer the client who asks who owns the result.
- AI for Product ManagersAI turns forty interview transcripts into themes, a rough idea into a PRD draft, and a napkin sketch into a clickable prototype, and it will also confidently invent a customer need that does not exist. Here is how product managers get the first without the second.
- AI for Software DevelopersCoding assistants write, refactor, test, and explain code, and agentic tools run the whole loop. Treat every generated line as a pull request from a fast, overconfident junior: useful, never merged unread.
- AI for Content WritersAI can research, outline, draft, and edit alongside you. The writers who thrive with it use it to reach the interesting part faster, keep their own voice, and are straight with clients about how they work.