Working UX designers need interview questions fast. These 25 ChatGPT prompts generate complete interview scripts, follow-up questions, and research briefs you can use immediately.
These prompts pair well with Jasper AI for UX Designers-specific tone control, or Copy.ai for fast iteration.
Discovery Interview Scripts
You are a UX researcher preparing for user discovery interviews about a digital product redesign.
Product: {product_name} User type: {target_user_segment} Current pain points we know: {known_issues} Business goal: {primary_business_objective} Interview length: {30_45_60_minutes} User’s experience level: {beginner_intermediate_expert} Tone: {conversational_formal_friendly}
Write a complete interview script with 12-15 open-ended questions. Start with warm-up questions about their background. Move to current behavior and pain points. End with future state and wish list questions. Include 2-3 follow-up probes for each main question. Format as a script the researcher can read directly from, 800-1000 words total.
When to use it: You have a user interview scheduled tomorrow and need a structured script that covers discovery without leading the participant.
Pro tip: Always include the user’s experience level - beginners need more context-setting questions while experts can dive straight into nuanced workflow details.
You are a UX researcher conducting interviews to understand why users abandon a specific workflow.
Workflow: {specific_user_workflow} Drop-off point: {where_users_typically_abandon} Product context: {mobile_app_web_platform_desktop} Users interviewed: {how_many_users_recruited} Interview format: {in_person_remote_moderated_unmoderated} Hypothesis: {your_best_guess_why_users_drop_off} Tone: {empathetic_neutral_investigative}
Create a 45-minute interview guide focused on uncovering abandonment triggers. Include task-based questions that walk through their last attempt. Add emotional state probes. Include questions about workarounds they’ve tried. Structure as: context questions (5 mins), workflow walkthrough (25 mins), alternatives exploration (10 mins), wrap-up (5 mins). 600-800 words.
When to use it: Your analytics show a specific drop-off point but you need to understand the human story behind the data.
Pro tip: Ask about their “last time” they tried the workflow rather than general behavior - specific instances reveal more honest details than hypothetical responses.
You are a UX researcher interviewing users about their relationship with a competitor product before building a alternative.
Competitor product: {competitor_name} Our planned solution: {brief_description_new_product} User segment: {target_demographic} Competitor’s strength: {what_they_do_well} Gap we’re targeting: {opportunity_area} Research timeline: {tight_standard_extensive} User recruitment: {existing_customers_prospects_mixed}
Design a 50-minute interview that uncovers switching triggers without revealing our product plans. Focus on moments of frustration, workaround behavior, and unmet needs. Include questions about their decision process for choosing tools. Structure around job-to-be-done framework. End with hypothetical improvement scenarios. 700-900 words with specific question phrasing.
When to use it: You’re building something to compete with an established player and need to find the gaps that would make users switch.
Pro tip: Never mention your planned solution during the interview - users will tell you what they think you want to hear instead of revealing real pain points.
You are a UX researcher interviewing long-term users about feature usage patterns and hidden workflows.
Product: {your_product_name} User tenure: {how_long_theyve_used_it} Feature in question: {specific_feature_being_studied} Usage frequency: {daily_weekly_monthly_rarely} User role: {job_title_or_user_type} Team context: {solo_user_team_lead_admin} Business priority: {increase_usage_improve_experience_remove_feature}
Create interview questions that reveal how power users actually work vs how we think they work. Include questions about feature combinations, undocumented workflows, and efficiency tricks. Ask about teaching others and onboarding. Structure as: current workflow deep dive (20 mins), feature-specific exploration (20 mins), ideal state visioning (10 mins). 500-700 words.
When to use it: You need to understand how experienced users really work with your product before making changes that might break their established patterns.
Pro tip: Ask power users to show you their shortcuts and “tricks” - they often develop workflows that reveal better product directions than your roadmap.
You are a UX researcher preparing questions for users who’ve recently churned or downgraded their subscription.
Product: {saas_product_name} Churn timeframe: {when_they_left} Previous subscription: {plan_level_they_had} Churn reason (suspected): {billing_features_complexity_competition} Relationship status: {can_we_win_them_back} Interview tone: {understanding_investigative_win_back} Follow-up goal: {pure_research_potential_reactivation}
Write questions that uncover the real story behind their departure without sounding defensive. Include timeline reconstruction of their declining usage. Ask about the final straw moment. Explore what would need to change for them to return. Keep questions neutral and research-focused. Structure as 30-minute conversation. Include follow-up probes for emotional responses. 400-600 words.
When to use it: Your churn rate is climbing and you need to understand the real reasons beyond exit survey responses.
Pro tip: Focus on the timeline leading up to their decision rather than the decision itself - the warning signs matter more than the final moment.
Usability Testing Scripts
You are a UX researcher facilitating a moderated usability test for a new feature release.
Feature: {feature_name_and_description} Test environment: {prototype_staging_live_product} User type: {new_existing_mixed_users} Task complexity: {simple_moderate_complex_workflow} Success metrics: {completion_time_error_rate_satisfaction} Testing method: {think_aloud_observation_task_based} Session length: {30_45_60_minutes}
Create a complete testing script with pre-task briefing, 4-6 realistic scenarios, and post-task questions. Include specific instructions for what to observe. Add prompts for when users get stuck. Structure the scenarios from simple to complex. Include emotional state check-ins. Format as a script the facilitator can follow exactly. 800-1000 words.
When to use it: You have usability sessions booked and need a structured script that captures both task completion and user sentiment.
Pro tip: Write scenarios as realistic goals the user would actually have, not feature tours - users behave differently when they have genuine motivation.
You are a UX researcher testing the onboarding flow for new users who signed up but haven’t completed setup.
Product: {product_name} Onboarding stage: {signup_to_first_value} Drop-off data: {where_most_users_abandon} New user type: {technical_non_technical_mixed} Onboarding length: {steps_or_time_estimate} Previous version results: {what_didnt_work_before} Test format: {live_prototype_click_through}
Design a 45-minute test session that identifies onboarding friction points. Include pre-task questions about their expectations. Create realistic scenarios for why they signed up. Add think-aloud instructions. Include recovery testing when they get confused. Structure as: expectation setting (5 mins), onboarding walkthrough (30 mins), reflection questions (10 mins). 600-800 words with specific observation prompts.
When to use it: Your trial-to-paid conversion is low and you suspect the onboarding experience is losing users before they see value.
Pro tip: Test with people who match your actual signup demographics, not internal team members - domain knowledge blindness is real in onboarding flows.
You are a UX researcher conducting comparative usability testing between your product and a key competitor.
Your product: {your_product_name} Competitor: {competitor_product} Task focus: {specific_workflow_being_compared} User familiarity: {new_to_both_familiar_with_competitor_familiar_with_yours} Test structure: {a_b_sequential_parallel} Success measure: {speed_accuracy_preference_satisfaction} Session recording: {screen_recording_notes_both}
Create a testing protocol that fairly compares both products without bias. Include identical tasks for each platform. Add post-task preference questions. Include prompts for facilitator neutrality. Structure as counterbalanced testing with qualitative follow-up. Add instructions for handling user frustration with either product. 700-900 words with bias-prevention guidelines.
When to use it: You need objective evidence of your product’s strengths and weaknesses compared to the competition for roadmap prioritization.
Pro tip: Randomize which product users try first and use identical task language for both - small wording differences can skew results significantly.
You are a UX researcher testing accessibility and usability with users who have specific accessibility needs.
User needs: {visual_motor_cognitive_hearing_impairments} Assistive technology: {screen_reader_keyboard_navigation_voice_control} Product area: {specific_feature_or_flow} Accessibility goal: {compliance_usability_both} User experience level: {new_experienced_power_user} Testing environment: {user_lab_remote_in_context} Session support: {accessibility_expert_available}
Design an inclusive usability testing session that respects user expertise and reveals real barriers. Include technology setup time. Create meaningful tasks that match their actual use cases. Add questions about their typical strategies and workarounds. Include breaks and flexibility for different interaction speeds. Structure as collaborative problem-solving rather than formal testing. 600-800 words with accommodation guidelines.
When to use it: You’re testing with users who have accessibility needs and want to ensure your approach is respectful and productive.
Pro tip: Users with accessibility needs are often expert problem-solvers - ask about their strategies and workarounds as much as testing your interface.
You are a UX researcher conducting guerrilla usability testing at a conference or public location.
Location: {conference_coffee_shop_library_public_space} Product: {mobile_app_website_prototype} Task focus: {quick_specific_workflow} Time constraint: {5_10_15_minutes_per_person} Incentive: {coffee_gift_card_swag_none} Recording method: {phone_screen_recording_notes_only} Target users: {demographic_or_job_role}
Create a streamlined testing script for quick public feedback sessions. Include a 30-second product intro. Design 2-3 focused tasks that reveal key insights quickly. Add rapid-fire follow-up questions. Include polite ways to end sessions that aren’t working. Structure for maximum insight in minimum time. Add tips for approaching strangers professionally. 400-500 words with logistics guidance.
When to use it: You need quick user feedback and don’t have time for formal lab recruiting - you’re at an event or need insights this week.
Pro tip: Focus on one specific flow rather than general impressions - you’ll get more actionable insights from 10 people testing the same thing than broad feedback.
Stakeholder Interview Questions
You are a UX researcher interviewing a product stakeholder to understand business requirements before starting user research.
Stakeholder role: {product_manager_ceo_sales_director} Project: {specific_project_or_initiative} Timeline pressure: {tight_standard_flexible_deadline} Success metrics: {known_unknown_contested} User research budget: {limited_standard_extensive} Stakeholder research experience: {research_savvy_new_to_ux_resistant} Political context: {smooth_project_contested_direction}
Write questions that align business goals with research approach. Include questions about assumptions, constraints, and success definitions. Ask about user access and internal data availability. Probe for unstated concerns or political considerations. Structure as collaborative planning session: current state (10 mins), desired outcomes (15 mins), research parameters (10 mins). 500-700 words with diplomatic phrasing.
When to use it: You’re starting a new project and need to understand what the business actually needs from your research before designing the study.
Pro tip: Ask what would surprise them most in user feedback - stakeholder assumptions often reveal the most important things to test.
You are a UX researcher presenting research findings to stakeholders who expected different results.
Research findings: {brief_summary_of_key_insights} Stakeholder expectations: {what_they_expected_to_hear} Business implications: {how_findings_affect_roadmap} Audience: {product_team_executives_mixed_group} Presentation format: {meeting_deck_report_workshop} Follow-up needed: {decisions_more_research_action_planning} Resistance level: {open_minded_skeptical_defensive}
Create a presentation script that introduces unexpected findings diplomatically. Include data storytelling that connects user insights to business impact. Add preemptive responses to likely objections. Structure as narrative: what we learned, why it matters, what it means for decisions. Include specific quotes and examples. End with recommended actions. 700-900 words with transition phrases and stakeholder management guidance.
When to use it: Your research findings contradict what stakeholders wanted to hear and you need to present results that will actually influence decisions.
Pro tip: Lead with a finding they agree with before introducing contradictory evidence - it establishes your credibility before challenging their assumptions.
You are a UX researcher facilitating a workshop with cross-functional stakeholders to prioritize research insights for roadmap planning.
Research insights: {number_of_key_findings} Stakeholder mix: {engineering_product_design_business} Roadmap timeline: {next_quarter_6_months_annual} Resource constraints: {development_capacity_budget_time} Conflicting priorities: {feature_requests_vs_user_needs} Workshop length: {90_minutes_half_day_full_day} Decision authority: {clear_unclear_contested}
Design a workshop agenda that turns research insights into actionable roadmap decisions. Include individual reflection, group discussion, and prioritization exercises. Add facilitation prompts for managing disagreement. Create templates for capturing decisions and next steps. Structure as: insights review (20 mins), impact assessment (30 mins), prioritization voting (25 mins), action planning (15 mins). 600-800 words with facilitation tips.
When to use it: You have solid research insights but need stakeholder buy-in and decision-making to turn findings into product changes.
Pro tip: Use dot voting or other structured prioritization methods - open discussion often gets dominated by the loudest voice rather than the best arguments.
You are a UX researcher interviewing customer support and sales teams about user problems before designing formal research studies.
Team: {customer_support_sales_success_mixed} Product area: {specific_feature_or_workflow} Support volume: {high_moderate_low_complaint_frequency} Team research relationship: {collaborative_new_skeptical} Support tools: {ticketing_system_chat_logs_call_recordings} Research goal: {validate_problems_discover_