AI Prompts for UX Designers: The Ones That Actually Save You Time

Most "AI prompts for UX designers" lists hand you the obvious stuff: write the microcopy, draft a persona, name the button. Useful, but you already knew AI could do that. What actually changes your week are the prompts that surface the flaw you are too close to see, so those are the ones I am leading with. Change the details in brackets and they are yours.

One rule before we start, and it matters: never paste unreleased designs, user-research recordings, or participant PII into a public AI tool. Describe the situation instead ("a first-time user trying to check out on their phone"). You get the same help without handing confidential work or someone's private data to a company. If you want the fuller version of how to talk to these tools well, that is much of what my book, The Beginner's Guide to the AI Galaxy, is about.

The five most UX designers never think to try

Walk your flow as the user who is about to quit. You built the happy path; this finds the moment it breaks.

Walk through this flow as a [frustrated, distracted first-time user on a phone with one bar of signal]. Narrate your thoughts step by step and tell me the exact screen and moment where you would rage-quit and give up. Do not be polite about it. Flow: [describe each screen].

Find the accessibility fails before a real user does. This catches what your sighted, mouse-using eyes skip right over.

List the ways this design likely fails accessibility before a real user hits them. Check color contrast, focus order, keyboard navigation, screen-reader labeling, and anything that ignores reduced-motion or relies on color alone. For each, tell me the fix. Here is the screen: [describe elements, colors, and interactions].

Write the honest microcopy for the state you keep forgetting. The empty, error, and loading states are where trust is won or lost, and they are always the last thing anyone drafts.

Write the microcopy for the [empty state, the error state, and the loading state] of this [saved-searches list]. Be honest and human, not chirpy. Tell the user what happened, why, and the one thing they can do next. Keep each to a sentence or two. Context: [what the screen is for].

Have your toughest stakeholder tear it apart first. Better to hear it now than in the room.

Critique this design in the voice of [a skeptical VP of sales who cares about conversion and thinks the flow has too many steps]. Push on the parts they will actually push on in the review, and be blunt. Then tell me the strongest response I could give to each objection. Design: [describe it].

Turn your research notes into the insight you have been avoiding. Sometimes the finding means redoing work, so you talk yourself out of seeing it.

Here are my raw notes from [6 usability sessions]. Tell me the uncomfortable insight I am probably resisting because acting on it means [reworking the onboarding I just finished]. Back it with the specific moments in the notes. Notes: [paste, names removed].

The everyday time-savers

These are the staples. They will not surprise you, but they will give you your evenings back.

Draft a usability-test script.

Write a [20-minute] usability-test script for [a new appointment-booking flow]. Include a warm-up, [4] realistic tasks phrased as goals not instructions, and neutral follow-up questions that do not lead the participant. Remind me where to stay quiet and just watch.

Generate microcopy variants fast.

Give me [5] versions of the [primary button and its helper text] for [a screen where the user confirms a paid subscription]. Range from plain and reassuring to warmer, all honest about what happens next. Keep each button to [three words] or fewer.

Build a first-draft persona.

Draft a [1] realistic persona for [a busy parent using a grocery-delivery app]. Include their goal, their real constraints, the moment they usually reach for the app, and their biggest frustration. Mark clearly that this is a hypothesis to validate with research, not a fact.

Write up a design rationale.

Help me write the design rationale for [choosing a single-page checkout over a multi-step one]. Explain the user problem, the options I weighed, why I chose this, and the trade-offs I am accepting. Keep it tight enough for a slide. My notes: [paste].

Draft survey and screener questions.

Write [8] survey questions to learn how [small-business owners currently handle invoicing]. Avoid leading and double-barreled questions. Include a short screener up front to filter for [people who invoice at least monthly]. Keep the whole thing under [three minutes].

Run a heuristic evaluation on a screen.

Do a heuristic evaluation of this screen against Nielsen's [10] usability heuristics. For each heuristic, tell me whether it is met, and if not, the specific problem and a fix. Rank the issues by how much they hurt the user. Screen: [describe it].

How to make any of these yours

These prompts are starting points, not magic words. The single biggest upgrade is telling it who your users really are and what you actually want, the way you would brief a designer joining the team. The more of your real product you put in, the better it comes back, which is the whole idea behind talking to AI like a person, not a search box. And if a first answer is close but not right, do not start over, just tell it what to fix, one of the small prompting moves that change everything.

None of this replaces the part only you can do, which is understanding the person on the other side of the screen and deciding what is worth building. AI is a fast, tireless second pair of eyes; the empathy and the final call stay yours. That is the honest promise of AI for a designer.