ChatGPT Prompts for UX Designers

<context> I am a UX designer planning generative research for [PRODUCT], used by [USER] to accomplish [FLOW]. We are in early discovery and want to understand needs, mental models, and pain points without leading the participant. </context> <task> 1. Write a 45-minute semi-structured interview guide with a warm-up, 4-6 thematic sections, and a wrap-up. 2. For each section, provide 3-4 open, non-leading questions plus 2 optional follow-up probes. 3. Map every question to the underlying research objective it answers. 4. Flag any question that risks bias and suggest a neutral rewrite. 5. End with a participant consent and recording-permission script. </task>

<context> I need to recruit qualified participants for research on [PRODUCT]. The ideal [USER] regularly performs [FLOW]; I must screen out professionals, competitors, and people who do not match the behavior we care about. </context> <task> 1. Draft a screener survey of 8-12 questions covering demographics, behavior frequency, and disqualifying criteria. 2. For each question, mark which answer options qualify, disqualify, or quota-balance the sample. 3. Use behavioral questions (what they did) over attitudinal ones (what they think) wherever possible. 4. Recommend target quotas across the key segments. 5. List 3 fraud-detection or attention-check questions to filter low-quality respondents. </task>

<context> I must align stakeholders before researching [PRODUCT] with [USER]. Leadership wants to know why, what, and how this research will inform [FLOW] decisions. </context> <task> 1. Write a one-page research plan with background, problem statement, and 3-5 research questions. 2. Recommend the most appropriate method (interviews, diary study, survey, usability test) and justify the choice. 3. Define participant criteria, sample size, timeline, and required tools. 4. State the decisions this research will unblock and the risk of not doing it. 5. List measurable success criteria for the study. </task>

<context> I just finished interviews about [PRODUCT] with several [USER] participants. I will paste raw notes or transcripts. I need to find patterns about [FLOW] without inventing findings. </context> <task> 1. Wait for me to paste the notes, then cluster observations into 5-8 themes. 2. For each theme, give a short name, a one-line summary, supporting verbatim quotes, and how many participants mentioned it. 3. Separate observations (what was said) from interpretations (what it might mean) and label each. 4. Surface contradictions or outliers worth investigating. 5. Propose 3 prioritized opportunity areas grounded only in the data. </task>

<context> I am writing a survey to measure attitudes and behaviors of [USER] toward [PRODUCT] and the [FLOW] experience. I want valid, unbiased questions and clean scales. </context> <task> 1. Draft 12-15 survey questions mixing single-select, multi-select, and Likert scales. 2. For every Likert item, use a balanced, labeled scale and avoid double-barreled wording. 3. Add 2 open-ended questions for qualitative depth. 4. Order questions to reduce priming and place sensitive items last. 5. Flag any leading, loaded, or ambiguous question and provide a corrected version. </task>

<context> I have research insights about [USER] who use [PRODUCT]. I will paste key findings. I want a behavioral persona grounded in data, not demographic stereotypes. </context> <task> 1. Wait for my research findings, then build a single primary persona. 2. Include goals, motivations, behaviors, frustrations, context of use, and a representative quote. 3. Anchor every persona attribute to a specific finding I provided and note where evidence is thin. 4. Avoid demographic filler that does not affect design decisions. 5. Add a short 'design implications' section translating the persona into 3 actionable UX priorities. </task>

<context> I am mapping how [USER] currently completes [FLOW] with [PRODUCT], including the messy parts before and after they touch our product. </context> <task> 1. Break [FLOW] into 5-8 sequential stages from trigger to outcome. 2. For each stage, describe user actions, thoughts, emotions, touchpoints, and pain points. 3. Plot an emotional curve and call out the lowest moments. 4. Identify the 3 highest-impact friction points and the evidence behind each. 5. Suggest one opportunity per top friction point. </task>

<context> I want to design an improved experience for [USER] completing [FLOW] in [PRODUCT]. I have the current-state pain points and want a credible future-state vision. </context> <task> 1. Re-imagine each stage of [FLOW] showing the ideal user actions, emotions, and touchpoints. 2. For each improvement, name the friction it removes and the design move that enables it. 3. Keep the vision realistic for a mid-size product team, not science fiction. 4. Highlight 3 quick wins versus 2 larger bets. 5. Note assumptions that must be validated before building. </task>

<context> I need an empathy map for [USER] interacting with [PRODUCT] during [FLOW] to align my team on the user's perspective. </context> <task> 1. Produce a four-quadrant empathy map: Says, Thinks, Does, Feels. 2. Populate each quadrant with 4-6 specific, research-grounded entries. 3. Add a Pains and a Gains section beneath the quadrants. 4. Flag any entry that is an assumption versus an observed behavior. 5. End with 3 design questions the empathy map raises. </task>

<context> I have a persona for [USER] of [PRODUCT] with known pains around [FLOW]. I want to connect those pains to potential features without over-promising. </context> <task> 1. List the persona's top 5 pains in priority order. 2. For each pain, propose 1-2 feature or design ideas that directly address it. 3. Rate each idea on user impact and rough effort (high/medium/low). 4. Recommend which ideas to validate first and how. 5. Flag any feature that solves a problem the persona does not actually have. </task>

<context> I am about to wireframe a screen in [PRODUCT] where [USER] performs [FLOW]. I want a clear brief before I open the design tool so the layout serves the task. </context> <task> 1. Define the screen's primary goal and the single most important user action. 2. List required content and UI elements in priority order. 3. Recommend a layout structure and visual hierarchy from most to least important. 4. Note states to design: empty, loading, error, and success. 5. List 3 usability risks for this screen and how the layout can mitigate them. </task>

<context> I am organizing the navigation and content structure of [PRODUCT] so [USER] can easily complete [FLOW] and find related tasks. </context> <task> 1. Propose a top-level navigation with 4-7 primary categories and rationale for each. 2. Outline a sitemap two levels deep showing where key flows live. 3. Apply clear, user-language labels and avoid internal jargon. 4. Flag any content that could belong in multiple places and recommend a home. 5. Suggest a card-sort study to validate the structure with real users. </task>

<context> I need to map the step-by-step user flow for [USER] completing [FLOW] in [PRODUCT], including decision points and error paths. </context> <task> 1. Lay out the happy-path flow as a numbered sequence of screens and actions. 2. Mark every decision point and branch with its condition. 3. Add error and recovery paths for the most likely failure points. 4. Identify steps that could be removed or combined to reduce friction. 5. Output the flow in a format I can recreate in a flow-diagram tool. </task>

<context> I have a content-heavy screen in [PRODUCT] for [USER] doing [FLOW] and I need to decide what to show, hide, or defer. </context> <task> 1. Classify each content element as essential, supporting, or optional for the primary task. 2. Recommend what belongs above the fold versus progressively disclosed. 3. Suggest where to use scanning patterns, grouping, or summarization. 4. Identify content that adds cognitive load without aiding the task. 5. Provide a prioritized content order for both mobile and desktop. </task>

<context> I am designing [FLOW] in [PRODUCT] for [USER] across mobile, tablet, and desktop and want a responsive layout strategy before wireframing. </context> <task> 1. Recommend a layout approach for each breakpoint and what changes between them. 2. Specify how navigation, primary actions, and content reflow per device. 3. Identify touch-target, thumb-reach, and readability considerations for mobile. 4. Note any element that should be hidden, collapsed, or reordered on small screens. 5. List the 3 most likely responsive bugs to test for. </task>