35 ChatGPT Prompts for Product Designers (Systems, Handoffs, and Stakeholders)

Write documentation for a [component name: button / modal / form input / navigation bar / card / tooltip] design system component. Include: component description, variants and states (with 1-sentence description of each), usage guidelines (when to use / when NOT to use), accessibility requirements, content guidelines, and implementation notes for developers. Format for a Figma component description or a Notion/Storybook documentation page.

Write documentation for a design token set. Token category: [color / typography / spacing / elevation / motion]. For each token group: explain what it represents, when to use it, any edge cases or anti-patterns, and how it relates to adjacent tokens. Audience: both designers (Figma usage) and developers (code implementation).

Write a pattern library entry for the [pattern name: e.g., empty state / error handling / confirmation dialog / progressive disclosure / inline validation]. Include: pattern description, when to use, when not to use, key principles for good implementation, common mistakes, related patterns, and 2–3 example scenarios with recommended and not-recommended approaches.

Write a contribution guide for designers and developers adding new components or patterns to our design system. Include: how to propose a new component, the criteria for inclusion, the review process, what documentation is required, how to submit for review, and how decisions are made. Make it welcoming but clear about standards.

Write release notes for a design system update. Changes: [list what was added, updated, or deprecated]. Audience: designers and developers across the product team. For each change: what it is, what's different from before, any migration steps required, and a link placeholder to updated docs. Format: scannable, with clear "action required" flags where applicable.

Create an agenda for a [30 / 60]-minute design review meeting. The design being reviewed: [describe feature/flow]. Attendees: [list roles]. Include: a structured time allocation, what type of feedback is needed at each stage (divergent exploration vs. specific decisions), how to prioritize feedback, and a synthesis activity at the end. The presenter should leave with clear next actions.

Write a facilitation guide for a design critique session for [project/feature]. Include: how to frame the problem before showing designs, the structured feedback format to use (I like / I wish / what if, or similar), how to handle strong conflicting opinions, how to stay focused on user outcomes vs. personal preferences, and how to capture action items. Time: [45 / 60 minutes].

Create a self-critique checklist for a product designer to review their own work before presenting it. Include questions across: does it solve the stated problem, is the interaction pattern consistent with design system, are all states handled (empty / loading / error / success), is it accessible, does it work at different viewport sizes, and what am I uncertain about that I need input on?

Help me write a professional response to design critique feedback I received in a recent review. The feedback was: [describe]. My initial reaction: [describe honestly]. Write a response that: acknowledges the feedback genuinely, separates what I agree with from what I need to push back on, asks a clarifying question where the feedback was vague, and proposes a next step.

Write a message to post alongside a design file I'm sharing for async review. The design: [describe feature/flow]. What I need reviewers to focus on: [describe specific questions — not "general feedback"]. What decisions I've already made (and why): [brief list]. Response format requested: [written comments / Figma annotations / video walkthrough]. Deadline: [date].

Write a design decision document for [a specific design choice]. Include: context (why this decision needed to be made), options considered (at least 2, with pros/cons), the decision made, the reasoning (tied to user needs and business goals), what we're not doing and why, and open questions for future follow-up. Audience: PM, engineering lead, and design leadership.

Write a presentation script for presenting a design solution to [engineers / product managers / business stakeholders / executives] who don't have design backgrounds. The design: [describe]. Structure: the user problem (2 min), the design solution (5 min), key decisions and trade-offs (3 min), what I need from this group (2 min). Avoid jargon. Lead with outcomes.

Write a brief summary of a design vs. business tradeoff I'm navigating. The design recommendation: [describe — what would be best for the user]. The business constraint: [describe — what limits what's possible]. For each option: the user impact, the business impact, and my recommendation. One page max, written for a PM or leadership audience who needs to make a call.

Write a design recommendation for what to include and exclude from a v1 [feature name]. My recommendation: include [list], defer to v2 [list]. For each decision: 1-sentence rationale tied to user needs or implementation complexity. This will be shared with the product team in a planning meeting. Keep it to half a page.

I'm dealing with a misalignment between design and [product / engineering / leadership] on [describe the disagreement]. Write a professional email that: names the disagreement clearly, explains the design rationale without being defensive, proposes a way to resolve it (data, user testing, structured decision criteria), and requests a time to align. Tone: collaborative problem-solver, not escalation.

Write handoff documentation for [feature/component] to be shared with the engineering team in [Figma / Zeplin / Notion / Jira]. Include: feature overview (what and why), component breakdown, interaction specifications (states, transitions, micro-interactions), content requirements, accessibility requirements, edge cases and error states, and open questions. Make it self-serve — engineers should be able to build without a meeting.

Write a detailed interaction specification for [interaction: e.g., a dropdown menu / a drag-and-drop interface / a multi-step form / a toast notification system]. Include: trigger, animation details (duration, easing, direction), all states (default, hover, focus, active, disabled, loading, error), keyboard navigation behavior, and screen reader behavior. Format for developer implementation.

Write an accessibility specification for [component/feature]. Cover: WCAG 2.1 AA requirements (specific criteria that apply), ARIA roles and labels required, keyboard navigation flow (tab order, focus management, keyboard shortcuts), color contrast requirements (with specific ratios), screen reader behavior, and any motion/animation considerations (prefers-reduced-motion).

Create a design QA checklist for verifying implementation of [feature] against design specs. Include checks for: visual fidelity (spacing, typography, color), interaction behavior (states, animations, transitions), responsive behavior across breakpoints, accessibility (keyboard, screen reader, contrast), edge cases (empty states, long content, error states), and cross-browser consistency.

Create an agenda for a 30-minute design-engineering sync for [project/feature]. Include: open design questions that need engineering input (10 min), implementation concerns from engineering that affect design (10 min), and alignment on any open edge cases or ambiguities (10 min). The goal: resolve blockers and close open loops — not a status update meeting.

I've completed user research on [topic]. Key findings: [list 4–5 insights]. Convert these research findings into design requirements: for each insight, write a corresponding design requirement that specifies what the product must do (or avoid) to address that user need. Format: "Users [finding] → Design must [requirement]."

Convert this user story into a design brief: "[paste user story]." The brief should include: what the user is trying to accomplish, what success looks like from their perspective, what constraints apply, key questions to answer before designing, and what existing patterns or components to start with.

Write a usability finding report entry for an issue I observed in testing. Observation: [describe what the user did or said]. Task: [describe the task]. Severity: [1–4]. Write the entry in standard format: finding title, severity rationale, description of the issue, evidence (quote or behavior description), design recommendation, and implementation effort estimate (low/medium/high).

Write a research request for a UX researcher. I need to answer: [describe the design question]. Context: [describe the design decision I'm making]. Proposed research approach: [interview / usability test / survey / diary study — suggest if unsure]. What I need back: [describe deliverable]. Timeline needed: [describe]. What decisions this will unlock: [describe].

Create a case study structure for a product design portfolio project for [describe project: type, company, problem, solution]. Include sections for: project context and your role, the design challenge, your process (research, ideation, iteration), key decisions with rationale, final solution with outcome metrics, and personal reflection. Each section should have a brief prompt for what to write.

Write the narrative section of a senior/lead product designer portfolio. The focus: demonstrating design leadership, not just craft. My experience to highlight: [describe: team leadership, system thinking, cross-functional influence, mentorship, strategic impact]. Tone: authoritative but grounded. Under 300 words. For a portfolio intro or a senior role application.

I'm interviewing for a [senior / lead / staff] product designer role at a [company type]. Generate: 5 portfolio presentation questions I should be ready for, 5 design process questions, 5 collaboration/cross-functional questions, and 3 leadership/impact questions for senior levels. For each, give me a framework for answering — not a script.

Write a 30-60-90 day plan for a product designer starting a new role at a [startup / mid-size / enterprise]. Include: what to prioritize in each phase (learning the product and users, first design contribution, broader influence), key relationships to build, what deliverables to target, and what "success" looks like at each milestone. Adapt for a [IC / lead] level.

Write a 3-month mentorship plan for a junior product designer I'll be mentoring. Their growth goal: [describe — e.g., improve interaction design craft / get better at stakeholder communication / develop systems thinking]. Include: monthly focus areas, specific exercises or projects, resources to share, check-in structure, and how to measure growth. Time commitment: 1 hour/week.

Write a performance review self-assessment for a product designer. My accomplishments this period: [list]. Areas of growth: [list]. Areas to develop: [describe honestly]. Format: structured narrative covering impact on users and the business, collaboration effectiveness, design quality and craft, and growth goals for next period. Tone: honest and confident — not underselling.

Create a condensed facilitation guide for a [1-day / 2-day] design sprint on [problem area]. Include: objectives, participants needed, day-by-day agenda (with time blocks), facilitation notes for each session, materials needed, and common failure modes to watch for. This is for a first-time design sprint facilitator.

Write a set of [5 / 6] product design principles for [product/company]. Each principle should: have a short memorable name (2–4 words), a 1-paragraph explanation of what it means in practice, and an example of how it guides a real design decision. The principles should be specific enough to resolve trade-offs — not generic feel-good statements.

Write a proposal for improving design operations at [company type/size]. Current state: [describe pain points — slow handoffs, inconsistent processes, documentation gaps, etc.]. Proposed improvements: [describe]. The proposal should: diagnose the root cause, propose specific changes, estimate the impact, and outline an implementation plan. Audience: design leadership or VP Product. 1 page.

Write a cross-functional process document for how design and engineering collaborate on [feature development / design system contribution / accessibility review / design QA]. Include: who is responsible for what at each stage, decision-making authority, handoff checkpoints, how to escalate disagreements, and what "done" looks like for both teams.

Draft an AI tool usage policy for a product design team. Cover: approved use cases (ideation, documentation, accessibility checks, copy drafting), areas requiring human review (final design decisions, accessibility implementation, user research synthesis), what NOT to input (real user data, proprietary designs, confidential product information), and how to document AI-assisted work. I'll have legal review before finalizing.