40 ChatGPT Prompts for UX Designers (Research, Copy, and Feedback)
UX designers use AI to draft personas, write usability test scripts, synthesize research, polish microcopy, and prep stakeholder presentations. The design work is yours — these prompts handle the surrounding writing that takes time away from it.
UX design is a discipline that produces as much written output as visual output — personas, research reports, test scripts, UX copy, rationale documents, and stakeholder presentations. These aren't peripheral tasks; they're the communication layer that turns design decisions into shared understanding. These prompts are built around the five writing categories that consume the most UX designer time across research, copy, and communication.
Every prompt uses [BRACKETS] for variables you fill in. Copy, customize, paste into ChatGPT, and edit before use.
Section 1: Persona Creation (Prompts 1–3)
User personas are only as useful as the specificity behind them. These prompts build personas from real research data, define anti-personas to sharpen design scope, and reframe existing personas through the Jobs-to-be-Done lens.
1. User Persona from Research Data
Turn research notes, interview transcripts, or survey data into a structured, actionable persona.
Create a UX user persona based on the following research data. Product / service: [DESCRIBE — e.g. "a project management tool for remote teams," "a mobile banking app"]. Research data: [PASTE OR DESCRIBE — e.g. key quotes from user interviews, survey results, common patterns observed in sessions. Include age range, job types, goals, frustrations, tech comfort level, and any other relevant demographic or behavioral data]. Persona name and role: [SUGGEST ONE — or leave blank for a suggestion]. Create a complete persona with: (1) Name, age, occupation, and one-line bio, (2) Goals — what they're trying to accomplish with this product (3 specific goals), (3) Frustrations — what blocks or frustrates them today (3 specific pain points), (4) Behaviors — how they currently try to solve the problem (what tools or workarounds they use), (5) Motivations — why this matters to them (the underlying driver, not just the task), (6) Tech comfort and device usage, (7) A direct quote that captures their core tension in their own voice. Format: a clearly structured persona document. Under 350 words. Make the persona feel like a real, specific person — not a generalized archetype.2. Anti-Persona (Who This Product Is Not For)
Define who the product is NOT designed for to sharpen design decisions and reduce scope creep.
Create an anti-persona for the following product — a description of the user type this product is NOT designed for. Product: [DESCRIBE]. Primary user persona: [BRIEF DESCRIPTION — who it IS for]. Create an anti-persona with: (1) Name, role, and one-sentence description, (2) Why they might initially seem like a user — what draws them to the product, (3) Why they're not the target user — specific mismatches in goals, behaviors, or context, (4) What they'd want from the product that conflicts with the core design direction, (5) How including this user type in your design process could harm the primary user experience. The purpose: sharpen the team's understanding of who the product serves by making explicit who it doesn't. Under 250 words. Tone: analytical and specific — the anti-persona should be as vivid as the primary persona, with enough detail that the design team can use it to push back on scope creep.3. Jobs-to-be-Done (JTBD) Framework for a User Persona
Reframe a user persona through the Jobs-to-be-Done lens to reveal what users are truly trying to hire the product to do.
Reframe the following user persona using the Jobs-to-be-Done (JTBD) framework. Product: [DESCRIBE]. User persona: [PASTE OR SUMMARIZE THE EXISTING PERSONA]. Apply the JTBD framework to identify: (1) The functional job — the practical task they're trying to accomplish, stated as "When [SITUATION], I want to [MOTIVATION], so I can [EXPECTED OUTCOME]." (2) The emotional job — how they want to feel (or avoid feeling) while doing this. (3) The social job — how they want to be perceived by others while doing this. (4) The underserved job — what aspect of the job is currently not being done well by existing solutions. (5) The switching trigger — what would cause them to "hire" a new product to do this job, stated as a specific moment or event. For each: be specific — not "save time" but "finish the end-of-day status update before leaving the office so I don't have to think about it over dinner." Under 300 words. Tone: analytical — JTBD statements should be precise enough to generate design decisions.Section 2: UX Copy & Microcopy (Prompts 4–5)
UX copy is one of the most underinvested areas of product design — and one of the highest-leverage ones. These prompts generate microcopy for critical UI states and write complete onboarding flow copy that guides users to their first value moment.
4. Microcopy for Key UI Moments
Write microcopy for critical UI states — empty states, error messages, confirmation dialogs, and tooltips.
Write microcopy for the following UI moments. Product: [DESCRIBE]. User persona: [BRIEF DESCRIPTION — who is using this]. Write copy for each of the following states (fill in which ones are relevant): (1) Empty state — [DESCRIBE THE SCREEN — e.g. "the inbox when there are no notifications"]: Write a headline (under 8 words) and supporting sentence (under 20 words) that explains the empty state and encourages the next action, without being patronizing or boring. (2) Error message — [DESCRIBE THE ERROR — e.g. "a failed payment," "an incorrect password"]: Write copy that explains what happened in plain language, tells them what to do next, and avoids technical jargon or blame. (3) Confirmation / success message — [DESCRIBE — e.g. "a form submission," "a completed task"]: Confirm the action, tell them what happens next. Under 20 words. (4) Tooltip — [DESCRIBE THE FEATURE — e.g. "a complex setting the user might not understand"]: Under 15 words. Explains the feature, doesn't just label it. (5) Onboarding first-time hint — [DESCRIBE THE SCREEN]: 1–2 sentences. Invites action without overwhelming. For each: write 2 variations with different tones (e.g. functional vs. warm). Tone reference: [DESCRIBE YOUR PRODUCT'S VOICE — e.g. "approachable and direct," "professional and minimal"].5. Onboarding Flow Copy
Write the full copy for a user onboarding flow — welcome screen through first-value moment.
Write the copy for a user onboarding flow for the following product. Product: [DESCRIBE — what it does, who it's for]. First-value moment (the "aha moment"): [DESCRIBE — e.g. "the moment the user sees their first personalized dashboard," "when they successfully connect their first integration"]. Onboarding steps: [LIST THE SCREENS OR STEPS IN THE FLOW — e.g. "welcome screen, goal selection, account setup, first feature walkthrough, dashboard"]. Tone: [DESCRIBE — e.g. "friendly and encouraging," "minimal and professional"]. Write copy for each step: (1) Screen headline (under 10 words), (2) Supporting copy (1–2 sentences — under 40 words), (3) Primary CTA button text (under 5 words — specific, not "Next" or "Continue"), (4) Secondary option label if applicable (e.g. "Skip for now"). Principles: copy should guide, not overwhelm; every screen should answer "why should I care about this step?"; the first-value moment should be celebrated, not just confirmed. Note: each step should build on the previous — this is a sequence, not a collection of isolated screens.Section 3: Usability Test Scripts (Prompts 6–7)
A poorly written usability test script produces invalid data. A well-written one produces insights that change the product. These prompts write complete moderated test scripts and unmoderated task designs that are clear, neutral, and research-ready.
6. Usability Test Script
Write a moderated usability test script with tasks, probing questions, and a debrief guide.
Write a moderated usability test script for the following product and research goals. Product: [DESCRIBE — what it is, what stage it's at (prototype, beta, live)]. Test objectives: [LIST 2–3 — what specific questions are you trying to answer? E.G. "Can users find the payment settings without prompting?," "Do users understand the difference between a draft and a scheduled post?"]. User profile for participants: [DESCRIBE — who you're recruiting and why]. Test tasks to assign: [LIST 3–5 — the specific tasks participants will try to complete]. Write a complete test script with: (1) Introduction script — what to say at the start, including consent language, explanation of think-aloud protocol, and reassurance that you're testing the product, not them. (2) Warm-up questions — 3 questions to relax the participant and gather context. (3) Task instructions — for each task: the task prompt (written as a natural scenario, not a direction like "click the X button"), success criteria (what counts as task completion), and 2–3 probing questions to ask if the participant gets stuck or completes the task. (4) Post-task questions — 3 questions after each task to capture impressions. (5) Debrief questions — 5 questions at the end of the session to gather overall reactions. Under 600 words. Tone: neutral and facilitative — usability test scripts should not lead the participant toward the "right" answer.7. Unmoderated Usability Test Task Design
Design clear task prompts for an unmoderated usability test where there's no moderator to clarify.
Write task prompts for an unmoderated usability test. Platform: [E.G. "UserTesting, Maze, Lookback"]. Product: [DESCRIBE]. Tasks to test: [LIST 3–5 SPECIFIC FLOWS OR FEATURES]. For each task: (1) A scenario that provides context without leading the participant — written in second person ("Imagine you are..."), under 40 words. (2) The specific task instruction — what they need to do, stated clearly without using the exact UI labels. (3) Success criteria — what counts as task completion (binary if possible: did/did not). (4) A post-task rating prompt (e.g. "On a scale of 1–7, how easy was it to complete that task?"). (5) A short post-task open question (e.g. "What, if anything, was confusing about that process?"). Principle: unmoderated tasks must be completely self-contained — if a participant is confused by the task prompt, the data is invalidated. Every task should be testable with no moderator present.Section 4: Research Synthesis (Prompts 8–9)
Synthesizing user research into actionable insights is one of the most time-intensive parts of the UX process. These prompts turn raw notes into themed findings and generate executive summaries that stakeholders can act on without reading the full report.
8. Affinity Mapping and Theme Synthesis
Synthesize raw user research notes or interview transcripts into themes and design insights.
Synthesize the following user research data into themes and actionable design insights. Research type: [E.G. "6 moderated user interviews," "100 survey responses," "usability test observations"]. Raw data: [PASTE YOUR NOTES — interview quotes, observations, survey responses, or a summary of key findings. The more specific the input, the better the synthesis]. Research questions this data was meant to answer: [LIST]. Synthesize the data by: (1) Identifying 4–6 major themes — group the observations into patterns. For each theme: name it clearly, summarize what the data says in 2–3 sentences, and include 2–3 supporting quotes or observations. (2) Identifying the most significant insight from each theme — what does this mean for the design? Not just an observation, but a design implication. (3) Identifying contradictions or tensions — places where different users said or did conflicting things that need design resolution. (4) Identifying gaps — what did the data NOT answer that you still need to know? Under 500 words total. Tone: analytical and specific — research synthesis should produce things you can act on in the next design sprint, not general observations.9. Research Report Executive Summary
Write a concise executive summary of a research report for stakeholders who won't read the full document.
Write an executive summary of a UX research report for stakeholders who need the key findings without reading the full document. Research type and scope: [DESCRIBE — e.g. "6 user interviews with existing customers, 45–60 minutes each, focused on the onboarding experience"]. Key findings: [LIST YOUR MAIN FINDINGS — 4–6 bullet points or paragraphs]. Most critical insight: [THE SINGLE FINDING THAT SHOULD MOST INFLUENCE UPCOMING DESIGN DECISIONS]. Design recommendations from the research: [LIST 3–5 SPECIFIC RECOMMENDATIONS]. What this research did not cover: [LIST — scope limitations]. Write an executive summary with: (1) A 2-sentence framing of what was researched and why, (2) Top 3 findings (the ones that most matter for product decisions), (3) The single most critical insight and what it means for the design roadmap, (4) Top 3 design recommendations with brief rationale, (5) What to research next. Under 300 words. Tone: direct and decision-ready — this summary will be read by product managers and executives; it should enable decisions, not just report findings.Section 5: Stakeholder Presentation Prep (Prompts 10–11)
Stakeholder alignment is as important as the design itself. These prompts structure research finding presentations that drive decisions and create design rationale documents that make the reasoning behind design choices transparent and durable.
10. Stakeholder Presentation for Research Findings
Structure a stakeholder presentation of UX research findings that drives alignment and decisions.
Create a stakeholder presentation outline for UX research findings. Research conducted: [DESCRIBE]. Audience: [DESCRIBE — e.g. "product team + VP of Product and VP of Engineering," "C-suite executives with limited UX context"]. What decisions this research should inform: [LIST — specific product or roadmap decisions]. Key findings: [LIST YOUR TOP 4–5 FINDINGS]. Recommended design directions: [LIST YOUR RECOMMENDATIONS]. Create a presentation outline with the following structure: (1) Why we did this research — the business question it was answering (1 slide), (2) How we did it — methodology, participants, what we tested (1 slide, keep minimal), (3) Who we spoke to — brief persona summary of participants (1 slide), (4) Top findings — one slide per finding, each with: a clear headline, 2–3 supporting data points, and one design implication, (5) The most important insight — your "hero finding" that deserves its own dedicated moment (1 slide), (6) Recommendations — what the team should do next based on the research (1 slide per recommendation), (7) Open questions — what this research didn't answer and what to do about it (1 slide). For each section: write the slide headline and 3–5 bullet points of talking notes. Under 500 words total. Tone: confident and decision-oriented — stakeholder presentations should drive alignment, not just share information.11. Design Decision Rationale Document
Document the rationale behind a key design decision so it can be communicated clearly to stakeholders and team members.
Write a design decision rationale document for the following design choice. Product: [DESCRIBE]. Design decision: [DESCRIBE — e.g. "we're removing the advanced filter panel and replacing it with a smart default system," "we're changing the primary navigation from a sidebar to a top navigation bar"]. The problem this decision solves: [DESCRIBE — the user need or design problem that motivated this change]. Options considered: [LIST 2–3 — what alternative approaches were evaluated and why they were not chosen]. Evidence or research that supports this decision: [LIST — usability test data, analytics, user feedback, heuristics]. Trade-offs and what we're accepting: [LIST — what is being given up or deprioritized by making this choice]. Who was involved in the decision: [LIST — designer, PM, research, engineering input]. Write a 300–400 word rationale document with: (1) The decision — state it plainly, (2) The problem it solves, (3) What was considered, (4) Why this approach was chosen, (5) Supporting evidence, (6) Trade-offs we're accepting. Tone: clear and confident — design rationale documents should make the reasoning transparent so it can be revisited, challenged, or built on as the product evolves.Get all 40 prompts
Unlock the full list — plus 100+ prompts for every design task — research, copy, and stakeholder communication — for just $19
Unlock Now — $19Instant download · Digital product — no shipping or physical delivery.
Get 100+ Prompts for Every Design Task →
The AI Productivity Prompt Pack includes 100+ copy-paste prompts for UX designers, researchers, product managers, and design teams — from research synthesis to stakeholder communication. One payment, instant download.
Get 100+ prompts for every design task — $19 →The best UX designers are both exceptional researchers and exceptional communicators — they produce insights stakeholders understand, copy users trust, and rationale documents that protect design decisions from being reversed without evidence. These prompts support the written layer of that work across the full design process. For related workflows, see our guide to ChatGPT prompts for designers and our guide to ChatGPT prompts for project managers.