Ready-to-use ChatGPT prompts for UX designers who need client design briefs written and sent today. Each prompt produces a finished brief you can customize and deliver within minutes.
These prompts pair well with Jasper AI for UX Designers-specific tone control, or Copy.ai for fast iteration.
Project Kickoff Briefs
You are a UX designer writing a design brief for a new project kickoff meeting with a client.
Project: {project_name} Client: {client_company_name} Timeline: {project_duration_weeks} weeks Budget range: {budget_range} Key stakeholders: {stakeholder_names_and_roles} Main business objective: {primary_goal} Target users: {user_demographic_description} Current pain points: {three_specific_problems} Success metrics: {how_success_measured}
Write a 400-500 word project design brief that opens with the business context, defines the design challenge in one clear sentence, outlines scope boundaries, and closes with next steps for the first sprint. Use confident, solution-focused language that demonstrates expertise while staying accessible to non-designers.
When to use it: Right after your sales call when the client says yes and you need to document what you agreed to before memories fade.
Pro tip: Always include one constraint they didn’t mention but you know will come up - like mobile responsiveness or accessibility requirements.
You are a UX designer creating a brief for a website redesign project with tight budget constraints.
Client: {client_name} Current website: {existing_site_url} Industry: {business_sector} Budget: {total_budget_amount} Timeline: {weeks_to_completion} Must-keep elements: {features_to_preserve} Biggest complaint: {main_user_frustration} Conversion goal: {what_users_should_do} Competitor benchmark: {competitor_site_example}
Write a 300-350 word design brief that acknowledges budget realities upfront, prioritizes high-impact changes, and sets realistic expectations. Frame limitations as focused strategy, not corners cut. Include three specific deliverables and timeline milestones.
When to use it: When a small business client loves your work but has champagne taste and beer budget.
Pro tip: Lead with what you can accomplish rather than what you can’t - clients remember the first frame you set.
You are a UX designer writing a brief for an e-commerce checkout flow optimization project.
Client: {ecommerce_brand} Platform: {shopify_woocommerce_custom} Current conversion rate: {existing_percentage} Target improvement: {goal_percentage} Major drop-off point: {where_users_abandon} Payment methods: {available_options} Average order value: {typical_purchase_amount} Mobile traffic: {percentage_mobile_users} Technical constraints: {platform_limitations}
Write a 350-400 word brief focused on conversion optimization. Start with current state data, identify the biggest opportunity, propose specific UX improvements, and end with testing methodology. Use metrics-driven language that speaks to ROI concerns.
When to use it: When an online store is bleeding money at checkout and needs immediate improvements that show measurable results.
Pro tip: Include estimated revenue impact in dollars, not just percentage improvements - executives think in money, not conversion rates.
You are a UX designer creating a brief for a mobile app prototype for user testing.
App concept: {app_idea_description} Target users: {primary_user_group} Core feature: {main_functionality} Platform: {ios_android_both} Testing timeline: {weeks_until_user_testing} Prototype fidelity: {low_medium_high} User scenarios: {three_key_use_cases} Business hypothesis: {assumption_to_validate} Success criteria: {testing_goals}
Write a 280-320 word brief for a prototype project. Focus on what needs to be validated, not what needs to be built. Specify exactly which screens are required, what level of interactivity is needed, and how results will inform next decisions. Keep language hypothesis-driven and experiment-focused.
When to use it: When stakeholders want to build everything and you need to focus them on testing one core assumption first.
Pro tip: Always specify what you’re NOT building in the prototype - clients assume if it’s not mentioned, it’s included.
You are a UX designer writing a brief for a SaaS dashboard redesign with multiple user types.
Product: {saas_product_name} User types: {admin_manager_enduser_roles} Current biggest complaint: {main_usability_issue} Key metrics dashboard shows: {data_types_displayed} Technical stack: {frontend_framework} Design system status: {existing_none_outdated} Deadline driver: {why_timeline_fixed} Success measurement: {user_satisfaction_metric} Handoff format: {figma_sketch_code}
Write a 450-500 word brief that addresses multi-user complexity upfront. Explain how you’ll prioritize competing needs, validate designs with each user type, and maintain consistency. Include specific deliverables for design system components and user flow documentation.
When to use it: When a SaaS client says “make the dashboard more intuitive” but has three different user types with conflicting needs.
Pro tip: Propose separate testing sessions for each user type - mixed groups create political dynamics that skew feedback.
Scope Change Documentation
You are a UX designer documenting a mid-project scope change request from a client.
Original scope: {initial_deliverables} Requested addition: {new_feature_or_change} Reason for change: {client_justification} Impact on timeline: {additional_weeks_needed} Budget implications: {extra_cost_amount} Current project phase: {discovery_design_testing_dev} Risk to launch date: {high_medium_low} Alternative solutions: {two_lighter_options} Decision deadline: {when_client_must_decide}
Write a 250-300 word scope change brief that acknowledges the request positively, explains implications clearly, and offers options. Present the full addition, a lighter version, and a post-launch option. End with a clear decision point and timeline for response.
When to use it: When the client says “just one more thing” halfway through the project and you need to document impact professionally.
Pro tip: Always offer a “Phase 2” option - it shows you’re thinking long-term and often becomes the preferred choice.
You are a UX designer explaining why a client’s requested design change would hurt user experience.
Requested change: {specific_design_modification} Client’s reasoning: {why_they_want_it} UX principle it violates: {usability_heuristic} User research that contradicts it: {data_or_findings} Potential negative impact: {user_experience_consequence} Your recommended alternative: {better_solution} Compromise position: {middle_ground_option} Reference example: {competitor_or_case_study}
Write a 200-250 word brief that respectfully pushes back on the request. Lead with understanding their goal, explain the UX concern with specific user impact, propose an alternative that meets their need differently. Use collaborative language that positions you as a partner, not an obstacle.
When to use it: When the client wants a carousel, popup, or other conversion-killing element because they saw it on a competitor’s site.
Pro tip: Reference a brand they admire that does it the right way - social proof works better than UX theory.
You are a UX designer creating a brief for emergency design changes due to user feedback.
Original launch date: {planned_go_live} Critical feedback: {main_user_complaint} Feedback source: {beta_users_support_tickets_reviews} Severity level: {blocks_workflow_confusing_annoying} Quick fix available: {yes_no_partial} Time to implement: {hours_or_days_needed} Delay consequences: {impact_of_postponing_launch} Stakeholder preference: {fix_now_or_ship_then_fix} Resource availability: {team_member_capacity}
Write a 180-220 word emergency brief that presents the situation, impact, and options clearly. Recommend either fixing before launch or shipping with a hotfix timeline. Include specific task assignments and timeline for resolution. Use urgent but calm language that shows control of the situation.
When to use it: When user testing reveals a critical issue 48 hours before launch and everyone’s asking “what do we do now?”
Pro tip: Always have a rollback plan ready - mention it in the brief to show you’re thinking about risk management.
You are a UX designer briefing stakeholders on scaling design work for additional market segments.
Original target market: {primary_user_segment} New market opportunity: {additional_segment} Key differences: {how_needs_vary} Design implications: {what_must_change} Research requirements: {user_interviews_needed} Timeline addition: {extra_weeks_required} Resource needs: {additional_team_members} Revenue potential: {business_opportunity_size} Risk assessment: {what_could_go_wrong}
Write a 400-450 word brief that frames expansion as strategic opportunity while being realistic about complexity. Explain why one-size-fits-all won’t work, what research is needed, and how to phase the work. Position yourself as the expert on user diversity and localization needs.
When to use it: When initial success makes the client want to expand to enterprise customers, different countries, or new user types.
Pro tip: Propose a small pilot with the new segment before full expansion - it reduces risk and gives you real data to work with.
You are a UX designer creating a brief for post-launch optimization based on analytics data.
Launch date: {when_site_went_live} Traffic volume: {monthly_users_or_sessions} Key metric underperforming: {conversion_signup_engagement} Current performance: {actual_numbers} Expected performance: {original_projections} Biggest drop-off point: {where_users_leave} Device breakdown: {mobile_desktop_tablet_split} User behavior insight: {surprising_finding} Optimization timeline: {weeks_for_improvements}
Write a 320-360 word brief for post-launch optimization work. Start with what’s working well, identify the biggest opportunity, propose specific tests, and outline measurement approach. Use data-driven language that connects UX changes to business metrics.
When to use it: Six weeks after launch when the initial excitement wears off and stakeholders want to know how to improve the numbers.
Pro tip: Celebrate the wins first - stakeholders need to hear what succeeded before they’ll trust your recommendations for improvement.
User Research Integration
You are a UX designer creating a brief that incorporates new user research findings into an existing design.
Research method: {interviews_surveys_usability_testing} Key finding: {most_important_discovery} Users affected: {percentage_or_segment} Current design assumption: {what_we_thought_was_true} Reality discovered: {what_research_revealed} Design changes needed: {specific_modifications_required} Implementation complexity: {easy_moderate_major_rebuild} Timeline impact: {days_or_weeks_affected} Confidence level: {how_sure_we_are}
Write a 300-340 word brief that presents research findings and design implications. Explain what changed your understanding, what stays the same, and what needs to be modified. Use confident language that shows research expertise while acknowledging what you learned.
When to use it: When user interviews reveal that your beautiful design solves the wrong problem entirely.
Pro tip: Include one quote from research that captures the insight perfectly - stakeholders remember stories better than statistics.
You are a UX designer writing a brief for accessibility improvements based on user testing with disabled users.
Testing participants: {user_disabilities_represented} Current accessibility level: {wcag_compliance_status} Major barriers found: {top_three_issues} Quick wins available: {easy_fixes} Complex problems: {issues_requiring_dev_work} Legal compliance risk: {high_medium_low} User impact severity: {how_much_it_affects_usage} Implementation priority: {what_to_fix_first} Timeline estimate: {weeks_for_full_compliance}
Write a 280-320 word brief that balances user impact with business reality. Present accessibility as user experience improvement, not just compliance. Prioritize changes by impact and effort, include specific WCAG guidelines referenced. Use inclusive language throughout.
When to use it: When accessibility testing reveals your design excludes users and you need buy-in for remediation work.
Pro tip: Frame accessibility as expanding market reach - “15% more potential customers” resonates better than compliance requirements.
You are a UX designer creating a brief for design changes based on customer support ticket analysis.
Support tickets analyzed: {number_of_tickets_reviewed} Time period: {months_of_data} Most common complaint: {primary_user_issue} Frequency of issue: {tickets_per_week} Support time per ticket: {average_resolution_minutes} Current design element causing confusion: {specific_ui_component} Proposed solution: {design_change_to_reduce_tickets} Expected ticket reduction: {percentage_decrease_estimate} Implementation effort: {design_hours_dev_hours}
Write a 260-300 word brief that connects UX improvements to support cost reduction. Calculate potential savings from reduced ticket volume, explain the design solution clearly, and show ROI of the change. Use business-focused language that appeals to operations teams.
When to use it: When the support team forwards you the same user confusion question for the 50th time this month.
Pro tip: Get support team buy-in first - they become your biggest advocates when they see UX improvements reduce their workload.
You are a UX designer briefing a client on internationalization requirements discovered through user research.
Target markets: {countries_or_regions} Language requirements: {languages_needed} Cultural considerations: {important_differences_found} Text expansion impact: {how_much_longer_translations_are} Right-to-left needs: {yes_no_partial} Local compliance: {legal_or_regulatory_requirements} User behavior differences: {how_usage_patterns_vary} Technical complexity: {implementation_challenges} Phased rollout plan: {which_markets_first}
Write a 380-420 word brief that explains internationalization complexity without overwhelming the client. Break down work by market priority, explain cultural adaptation needs, include timeline and resource requirements. Position international expansion as growth opportunity requiring proper investment.
When to use it: When the client says “just translate it” and you need to explain why successful international expansion requires design adaptation.
Pro tip: Show examples of their competitors’ international sites - both good and bad examples help illustrate the importance of proper localization.
You are a UX designer creating a brief for persona updates based on recent user research.
Original personas: {existing_user_types} Research findings: {what_changed_your_understanding} New user segment discovered: {unexpected_user_group} Outdated assumptions: {what_we_got_wrong} Confirmed behaviors: {what_research_validated} Design implications: {how_changes_affect_current_design} Priority