UX design is one of the most communication-intensive roles in tech. You're constantly translating between user research and engineering constraints, between business goals and human needs, between data and narrative. You write more than most designers realize: research plans, interview guides, usability test scripts, design rationale docs, stakeholder presentations, and handoff specs.
ChatGPT doesn't have taste. It can't evaluate whether a design is intuitive or delightful. But it can help you write faster, structure your thinking, and communicate your decisions more clearly to the people who need to act on them.
These 35 prompts are built around the actual work of UX — from discovery through delivery.
1. Research Planning and Synthesis
Prompt 1 — Research Plan Draft
Write a user research plan for a [generative / evaluative] study on [product area or feature]. Include: research objectives, methodology (interviews / usability testing / survey), participant criteria, session structure overview, and how findings will be used. Audience: cross-functional team and stakeholders approving the plan.
Prompt 2 — Interview Guide
Write a semi-structured interview guide for researching [user behavior/problem: e.g., how people currently manage their finances / why users abandon the checkout flow]. Include: opening script, 8–10 main questions (open-ended), 3–4 follow-up probes for each, and a closing section. Avoid leading questions.
Prompt 3 — Usability Test Script
Write a moderated usability test script for [product/feature]. Include: welcome and consent intro, 3–5 tasks with realistic scenario framing, observation prompts (think-aloud reminder), post-task questions, and a debrief section. Tone: warm, neutral, non-leading.
Prompt 4 — Research Synthesis Framework
I've completed [N] user interviews on [topic]. My raw notes contain: [describe themes or paste anonymized excerpts]. Help me structure an affinity mapping exercise: what categories to use, how to cluster observations, and what insights to prioritize. Format as a synthesis guide I can share with my team.
Prompt 5 — Research Report Executive Summary
Write an executive summary of user research findings for a stakeholder audience. Key insights: [list 4–5 findings from your research]. The research method was: [describe]. Format: 1 page max. Lead with implications for the product, not with methodology. Use clear, non-jargon language.
2. Persona and Journey Mapping
Prompt 6 — Persona Draft
Create a user persona based on these research themes: [describe what you learned about a user segment — goals, frustrations, behaviors, context of use]. Include: name, role/context, primary goals, key frustrations, relevant behaviors, and a quote that captures their mindset. Make it grounded — no stock photo clichés.
Prompt 7 — Anti-Persona
Write an anti-persona (who this product is NOT for) based on our target user description: [describe your primary persona]. Include: who this person is, why they're out of scope, and what misalignment they'd create if we designed for them. This is for internal team alignment.
Prompt 8 — Journey Map Narrative
Write a narrative journey map for [persona name] going through [experience: e.g., onboarding to the app / filing an insurance claim / scheduling a medical appointment]. For each stage: [list stages]. Include: what they're doing, thinking, feeling, and where the pain points and opportunity areas are. Format as a table with rows for each dimension.
Prompt 9 — Jobs-to-Be-Done Statement
Help me articulate the Job-to-Be-Done for [user type] in [context]. Based on what I know: [describe user goals and frustrations]. Write 3 JTBD statements in this format: "When [situation], I want to [motivation], so I can [expected outcome]." Make them functional, not feature-based.
Prompt 10 — Problem Statement
Write a UX problem statement for the design challenge I'm working on. Context: [describe user, their situation, and the problem]. Use the "How might we..." format for 3 different problem framings: one narrow, one medium, one broad. I'll choose which level of scope fits the project.
3. Design Rationale and Documentation
Prompt 11 — Design Decision Write-Up
Write a design decision document for this UI choice: [describe what you designed and the key decision]. Include: context (what problem we're solving), the options considered, why we chose this approach, trade-offs acknowledged, and how we'll know it's working. Audience: engineers and product manager.
Prompt 12 — Design Critique Agenda
Create an agenda for a 60-minute internal design critique session for [project/feature]. Include: goal of the session, how to give structured feedback (what the presenter needs input on), a timer-based format, and a synthesis activity at the end. The presenter should leave with clear next steps.
Prompt 13 — Annotation for Handoff
Help me write handoff annotations for this screen. The screen is: [describe the UI component or interaction]. For each element, the annotation should explain: what it is, how it behaves (states, interactions, edge cases), and any design decisions the engineer needs to know. Format as numbered annotation notes.
Prompt 14 — Accessibility Checklist
Create a design-phase accessibility review checklist for a [web app / mobile app / dashboard]. Cover: color contrast, typography, touch target sizing, keyboard navigation, screen reader considerations, motion/animation, and form design. Format as a checklist with the WCAG criterion reference where applicable.
Prompt 15 — Design System Documentation
Write the documentation for a [button / modal / form field / navigation component] design system component. Include: component name, variants (with descriptions), usage guidelines (when to use / when not to use), accessibility notes, and implementation notes for engineers.
4. Stakeholder Communication
Prompt 16 — Design Review Presentation Outline
Create a presentation outline for a design review with [stakeholder audience: leadership / engineering / product / cross-functional]. Project: [describe]. The presentation should cover: framing the problem, the design decision(s) we're reviewing, the options considered, our recommendation, and what we need from this group. Length: [N] minutes.
Prompt 17 — Pushback Response Script
I'm facing pushback on a design decision. The stakeholder said: "[quote or paraphrase the objection]." My rationale for the design is: [explain]. Write a response that: acknowledges their concern, explains the design rationale with evidence or user insight, and proposes a way to move forward (e.g., test it, adjust a specific element).
Prompt 18 — Research Finding as Slack Message
I need to share a key research finding with my team in Slack. The finding: [describe what you learned and why it matters]. Write a concise Slack message (under 150 words) that: leads with the insight, provides brief evidence, explains the implication for the product, and ends with a clear next step or question.
Prompt 19 — Design Tradeoff Summary for PM
Write a brief summary of a design tradeoff I'm navigating. Option A: [describe]. Option B: [describe]. For each: list the key benefits and the key risks. End with my recommendation and what data or input would change my decision. Keep it to half a page — my PM reads fast.
Prompt 20 — Scope Reduction Recommendation
I need to recommend cutting [feature/element] from the v1 scope. Write a short recommendation memo explaining: what we're cutting, why (complexity, timeline, research signal), what the impact will be, and how we can add it back in a future iteration. Audience: product manager and engineering lead.
5. Writing for the Product
Prompt 21 — UX Copy: Error Messages
Write error messages for these states in our [web / mobile] app: [list 3–5 error scenarios: e.g., form validation failure, network error, empty state]. For each: write a heading (under 8 words), body text (under 25 words), and call-to-action label. Tone: [brand voice: e.g., direct and friendly / professional / casual].
Prompt 22 — Onboarding Flow Copy
Write the copy for a [3 / 4 / 5]-step onboarding flow for [product/feature]. Each step should have: a headline, a 1–2 sentence explanation of the value the user gets from this step, and a CTA button label. Tone: [describe]. Avoid: jargon, passive voice, and generic phrases like "Get started!"
Prompt 23 — Microcopy Audit
Review the following UI strings and suggest improvements for clarity, tone, and user guidance: [paste list of strings — button labels, tooltips, help text, confirmation messages]. For each: flag any issues (vague, technical, inconsistent tone) and suggest an improved version.
Prompt 24 — Confirmation Dialog
Write the copy for a confirmation dialog for the action: [describe irreversible or significant action]. Include: dialog title, body text explaining what will happen, primary CTA (confirm action), and secondary CTA (cancel). Make the consequences clear without being alarming.
6. Usability Evaluation
Prompt 25 — Heuristic Review Checklist
Create a heuristic evaluation checklist based on Nielsen's 10 usability heuristics for reviewing a [type of interface: web app / mobile app / dashboard]. For each heuristic: provide 3–5 specific things to look for when reviewing the UI. Format as a reviewable checklist.
Prompt 26 — Usability Finding Write-Up
Write a usability finding report entry for an issue I observed during testing. What I saw: [describe user behavior]. The task was: [describe the task]. Format: finding title, severity rating (1–4 scale), description of the issue, evidence (what participants did/said), and recommendation.
Prompt 27 — Prioritization Framework for Usability Issues
I have [N] usability findings from recent testing. Here they are: [list issues]. Help me create a prioritization matrix based on: severity (impact on task completion), frequency (how often we observed it), and implementation effort. Recommend the top 3 to fix immediately.
Prompt 28 — Survey Question Design
Write a post-task survey for [task/feature being tested]. Include: 1 task success self-rating question, 3–5 specific follow-up questions about the experience, and 1 open-ended "anything else" question. Avoid leading questions and double-barreled questions. Use a consistent scale format throughout.
7. Career and Professional Development
Prompt 29 — Portfolio Case Study Outline
Create a case study outline for my UX portfolio for this project: [describe project briefly]. Include sections for: project overview, my role, the problem/goal, research process, key insights, design decisions (with rationale), final outcome, and lessons learned. Each section should have 2–3 sentences of guidance on what to write.
Prompt 30 — UX Interview Question Prep
I'm preparing for a UX interview at a [product company / agency / startup]. Generate 10 likely behavioral and portfolio questions, plus 3–4 system/process questions I should expect. For each, give me a framework for answering it, not a scripted answer.
Prompt 31 — Job Description Analysis
Analyze this UX job description: [paste JD]. Identify: the core skills they're prioritizing, what kind of team/culture this sounds like, any red flags in the role description, and 3 questions I should ask in the interview to evaluate fit. Then map my experience to the key requirements.
Prompt 32 — Critique Request to a Senior Designer
Write a message to a senior UX designer asking for feedback on my portfolio or a specific project. Include: a brief context on who I am, what I'm looking for (specific vs. general feedback), how much of their time I'm asking for, and a clear easy-to-respond format. Make it respectful and time-aware.
Prompt 33 — Design Leadership Escalation
I'm dealing with a situation where [describe: e.g., design work is being overridden without explanation / I'm not being included in early product decisions / stakeholders are requesting design changes that I believe will hurt users]. Write a professional email to my design lead or manager framing the situation, the impact on design quality, and what I'm asking for. Tone: constructive, not complaining.
Prompt 34 — 30-60-90 Day Plan for a New UX Role
Write a 30-60-90 day plan for a UX designer starting a new role at a [startup / mid-size / enterprise] company. Include: what to prioritize in each phase (learning, first contribution, broader impact), key relationships to build, and what "done" looks like at each milestone.
Prompt 35 — Retrospective Facilitation Guide
Create a facilitation guide for a UX team retrospective after [describe project or sprint]. Include: a warm-up activity (5 min), a structured reflection exercise (15 min), group synthesis (10 min), and action item capture (10 min). The goal is psychological safety and actionable takeaways, not venting.
Getting the Most From These Prompts
Give it the audience. "Explain this to a PM" and "explain this to an engineer" yield very different outputs. Always name who you're writing for.
Use it to draft, then edit. ChatGPT can produce a serviceable first draft of a research plan or stakeholder memo in 30 seconds. Your job is to make it accurate, specific, and yours — not to write from scratch.
Don't use it for user quotes or research findings. AI-generated "user insights" aren't insights — they're hallucinations. Only use ChatGPT to help you structure and communicate real findings from real research.
Prompt the tone explicitly. "Write this for a skeptical VP who doesn't read past the first paragraph" is a better prompt than "write an executive summary."
Your Complete UX Designer Prompt Toolkit
Want all 35 prompts organized by workflow and ready to use in your next research session?
The ChatGPT Prompt Toolkit for UX Designers includes:
- All 35 prompts in a clean PDF and Notion dashboard
- Fill-in-the-blank templates for research plans, design rationale docs, and handoff notes
- Bonus section: 10 prompts for service design and enterprise UX contexts
- Prompt chaining guide: from user interview to stakeholder presentation in 4 steps
Get the UX Designer Prompt Toolkit — $14.99
Designed for working UX practitioners, not students.
Top comments (0)