Working UX designers who need presentation-ready case study content without the hours of staring at blank slides. These prompts generate polished sections you can drop straight into your portfolio presentation and ship to stakeholders or hiring managers.
These prompts pair well with Jasper AI for UX Designers-specific tone control, or Copy.ai for fast iteration.
Executive Summary Slides
You are writing an executive summary slide for a UX case study presentation.
Project: {project_name} Problem solved: {core_problem_in_one_sentence} Timeline: {project_duration} Team size: {team_composition} Key metric improved: {primary_success_metric} Business impact: {revenue_users_or_efficiency_gain} Target audience: {stakeholders_or_hiring_managers} Presentation tone: {confident / collaborative / data_driven}
Write a 150 to 200 word executive summary that opens with the business problem, states your role clearly, and closes with the measurable outcome. Structure it as: Problem → Approach → Impact. Use bullet points for the three main achievements.
When to use it: When you’re presenting to senior stakeholders who need the full story in 60 seconds before diving into details.
Pro tip: Lead with the metric that matters most to your audience—conversion rate for product teams, task completion time for usability studies, or cost savings for enterprise clients.
You are creating a project overview slide for a portfolio presentation to hiring managers.
Project: {project_name} Your role: {ux_researcher / product_designer / ux_designer} Duration: {weeks_or_months} Platform: {web / mobile / desktop_app} User type: {target_user_description} Main challenge: {design_or_research_challenge} Solution approach: {methodology_used} End result: {what_shipped_or_recommended}
Write a 120 to 180 word project snapshot that positions you as the problem-solver. Open with what users couldn’t do before. Explain your approach in one clear sentence. End with what changed after your work. Keep the tone professional but engaging.
When to use it: When presenting your portfolio to potential employers who need to understand your impact quickly.
Pro tip: Mention specific tools or methods (Figma prototypes, usability testing with 12 participants) to demonstrate hands-on experience, not just strategic thinking.
You are writing a case study introduction for a complex B2B redesign project.
Client/Company: {company_name} Industry: {industry_sector} Project scope: {what_got_redesigned} User pain points: {top_three_user_frustrations} Business constraints: {budget_timeline_or_tech_limitations} Your contribution: {specific_deliverables_you_owned} Success criteria: {how_success_was_measured} Stakeholder buy-in challenge: {resistance_you_overcame}
Write a 200 to 250 word introduction that frames this as a strategic challenge, not just a visual refresh. Start with the business context that triggered the project. Show you understood both user needs and business constraints. End by previewing the structured approach you took.
When to use it: When presenting enterprise or B2B projects where stakeholder management and business impact matter as much as user experience.
Pro tip: Quantify the scope early (“supporting 2,000 daily active users” or “processing $50K in transactions weekly”) to establish the project’s significance.
You are summarizing a failed or pivoted UX project for a case study presentation.
Original goal: {what_you_set_out_to_achieve} Pivot moment: {when_and_why_direction_changed} Key learning: {biggest_insight_from_failure} Stakeholder reaction: {how_team_responded_to_pivot} Revised approach: {what_you_did_instead} Final outcome: {what_actually_shipped_or_learned} Your growth: {skill_or_perspective_gained} Audience: {hiring_managers / team_leads / peers}
Write a 180 to 220 word honest summary that shows maturity and learning agility. Open with the original vision. Explain the pivot as data-driven, not a mistake. Close with how this experience improved your process. Tone should be reflective but confident.
When to use it: When you want to show intellectual honesty and adaptability, especially to senior roles where strategic thinking matters.
Pro tip: Frame the pivot as “we discovered” rather than “we failed”—it positions you as someone who responds to evidence, not someone who makes mistakes.
You are creating a case study teaser for a presentation where time is limited.
Project: {project_name} Challenge in 6 words: {core_problem_ultra_concise} Your method: {research_design_or_testing_approach} Breakthrough moment: {key_insight_that_changed_everything} Deliverable: {prototype_recommendations_or_final_design} Impact number: {specific_metric_improvement} Audience attention span: {5_minutes / 10_minutes / 20_minutes} Follow-up availability: {detailed_case_study_available_yes_no}
Write a punchy 100 to 140 word teaser that makes them want the full story. Start with a hook that connects to their world. Give just enough process to show competence. End with the outcome and offer to dive deeper. Use short sentences and active voice throughout.
When to use it: When presenting in lightning rounds, portfolio reviews, or any situation where you need to grab attention fast.
Pro tip: End with a question that invites engagement: “Want to see how we increased task completion by 40%?” rather than just stating the outcome.
Problem Definition & Research
You are explaining user research findings for a case study presentation to product stakeholders.
Research method: {user_interviews / surveys / analytics_review / usability_testing} Participant count: {number_of_users_studied} Key finding 1: {most_critical_user_pain_point} Key finding 2: {second_most_important_insight} Key finding 3: {third_insight_or_opportunity} Surprising discovery: {unexpected_finding_that_changed_assumptions} Data support: {metrics_or_quotes_that_prove_findings} Stakeholder concern: {business_worry_your_research_addresses}
Write a 200 to 280 word research summary that connects user problems to business impact. Start with your method and sample size. Present findings as insights that drive action, not just observations. Include one direct user quote. End by linking the biggest finding to a business opportunity.
When to use it: When you need to justify design decisions with research evidence and show stakeholders why user problems matter to the bottom line.
Pro tip: Pair each user insight with a business implication—“Users couldn’t find the pricing page (UX problem) which likely contributed to our 23% drop-off rate at consideration stage (business problem).”
You are presenting persona insights derived from user research to a cross-functional team.
Primary persona: {persona_name_and_role} Core motivation: {what_drives_this_user} Main frustration: {biggest_pain_point_with_current_solution} Context of use: {when_where_why_they_use_product} Technical comfort: {low / medium / high} Decision-making style: {analytical / intuitive / collaborative} Success metric: {how_they_measure_success} Quote that captures them: {actual_user_quote_from_research}
Write a 180 to 240 word persona summary that feels like a real person, not a demographic profile. Start with a day-in-the-life moment. Explain their relationship to your product or service. Focus on behaviors and motivations over demographics. End with how understanding this persona shaped your design approach.
When to use it: When you need to build empathy with stakeholders who haven’t interacted directly with users and help them make user-centered decisions.
Pro tip: Include a small behavioral detail that makes the persona memorable—“Always has 15+ browser tabs open” or “Checks email during every meeting”—something your team will reference later.
You are explaining a competitive analysis for a UX case study presentation.
Competitors analyzed: {three_to_five_competitor_names} Analysis focus: {onboarding / checkout / navigation / feature_set} Standout competitor: {who_does_this_best} Their key strength: {what_they_nail_that_others_miss} Common weakness: {gap_all_competitors_share} User preference insight: {what_users_expect_based_on_competition} Opportunity identified: {white_space_you_can_exploit} Design implication: {how_this_influenced_your_solution}
Write a 220 to 280 word competitive analysis summary that focuses on user experience insights, not feature comparisons. Open with why you chose these specific competitors. Highlight patterns across competitors that reveal user expectations. Close with the strategic opportunity this analysis revealed for your project.
When to use it: When you need to show stakeholders that your design decisions were informed by market context and user expectations set by existing solutions.
Pro tip: Focus on interaction patterns and user flows rather than visual design—“three of four competitors require account creation before checkout” is more actionable than “most use blue CTAs.”
You are presenting usability testing results that revealed critical design flaws.
Testing method: {moderated_remote / in_person / unmoderated} Participant profile: {user_type_and_experience_level} Number of participants: {participant_count} Task tested: {core_user_flow_evaluated} Success rate: {percentage_who_completed_task} Critical failure point: {where_most_users_got_stuck} User quote: {frustrated_or_confused_user_quote} Business impact: {cost_of_this_usability_problem}
Write a 200 to 260 word testing summary that shows the severity of usability problems without being alarmist. Start with what you tested and why. Present the failure rate and main blocker clearly. Use one user quote to make it real. End with the business case for fixing these issues immediately.
When to use it: When you need to convince stakeholders to prioritize UX improvements by showing them real users struggling with current designs.
Pro tip: Convert usability problems into business language—“60% task failure rate” becomes “6 out of 10 potential customers abandon their purchase attempt.”
You are explaining how user journey mapping revealed experience gaps.
Journey mapped: {end_to_end_user_process} Key stages: {three_to_five_main_journey_phases} Highest friction stage: {where_users_struggle_most} Emotional low point: {most_frustrating_user_moment} Current workaround: {how_users_cope_with_bad_experience} Missed opportunity: {moment_where_you_could_delight} Supporting data: {metric_that_proves_the_friction} Cross-channel complexity: {where_online_offline_disconnect_happens}
Write a 240 to 300 word journey analysis that connects user emotions to business opportunities. Start by setting the scope of the journey. Walk through the key friction points as a story. Highlight the gap between user expectations and current reality. End with the biggest opportunity for improvement you identified.
When to use it: When you need to show stakeholders how individual UX problems connect into larger experience issues that hurt customer relationships.
Pro tip: Focus on one journey end-to-end rather than multiple partial journeys—the power is in showing how problems compound across touchpoints.
Design Process & Solutions
You are explaining your design process for a mobile app redesign case study.
Design challenge: {core_ux_problem_you_solved} Constraints: {platform_timeline_or_technical_limitations} Design principles: {three_principles_that_guided_decisions} Ideation approach: {sketching / workshops / design_sprints} Iteration cycles: {how_many_rounds_of_refinement} Stakeholder feedback: {key_input_that_changed_direction} User validation: {how_you_tested_concepts_with_users} Final solution: {what_you_delivered}
Write a 250 to 320 word process explanation that shows structured thinking without getting bogged down in methodology. Start with the design challenge in user terms. Walk through your approach as a logical progression. Show how user feedback influenced iterations. End with confidence in your final solution.
When to use it: When presenting to other designers or design-aware stakeholders who want to understand your problem-solving approach and design judgment.
Pro tip: Mention specific deliverables at each stage—“low-fi wireframes,” “interactive Figma prototype,” “usability testing with 8 participants”—to show tangible progress.
You are presenting design decisions for a complex enterprise software interface.
User task complexity: {simple / moderate / highly_complex} Information density: {amount_of_data_users_need_to_process} Key design decision 1: {major_interface_choice_you_made} Rationale 1: {why_this_decision_serves_users} Key design decision 2: {second_major_choice} Rationale 2: {user_or_business_reason_for_this} Controversial choice: {decision_stakeholders_questioned} Your defense: {why_you_stuck_with_this_approach}
Write a 200 to 270 word design rationale that shows strategic thinking behind interface decisions. Present each major decision as a deliberate choice with clear reasoning. Address the controversial choice directly and explain your user-centered logic. Keep the tone confident and evidence-based.
When to use it: When presenting B2B or enterprise projects where stakeholders need to understand why you made complex interface decisions that affect productivity.
Pro tip: Frame controversial decisions around user goals rather than personal preference—“Users need to scan 200+ records quickly” justifies dense information design better than “I prefer compact layouts.”
You are explaining how you solved an accessibility challenge in your UX design.
Accessibility barrier: {specific_barrier_you_addressed} Affected user group: {who_was_excluded_by_original_design} WCAG level targeted: {AA / AAA} Design solution: {how_you_made_it_accessible} Inclusive benefit: {how_this_helped_all_users_not_just_disabled_users} Implementation challenge: {technical_or_design_constraint_faced} Team education: {how_you_got_buy_in_for_accessibility} Testing approach: {how_you_validated_accessibility_improvements}
Write a 220 to 290 word accessibility case that shows inclusive design thinking. Start with the barrier in human terms, not technical jargon. Explain your solution and why it benefits everyone. Address any implementation challenges honestly. End with how you verified the solution worked for real users.
When to use it: When you want to demonstrate inclusive design skills and show that you consider accessibility as core UX practice, not an afterthought.
Pro tip: Emphasize universal benefits—“High contrast design helped users with low vision and also improved readability in bright office environments.”
You are presenting a design system component you created for a case study.
Component name: {button / form / card / navigation_element} Design problem: {inconsistency_or_inefficiency_it_solves} Usage contexts: {where_this_component_appears} Design variations: {different_states