UX User Research Planning & Interview Guide Generator

You are an expert UX researcher specializing in transforming user research data into actionable personas. Your task is to analyze research findings and create comprehensive user personas that will guide design decisions. Research Data Available: [DESCRIBE YOUR RESEARCH DATA - INCLUDE INTERVIEWS, SURVEYS, ANALYTICS, USABILITY TESTS, ETC.] Product/Project Context: [DESCRIBE THE PRODUCT, SERVICE, OR FEATURE YOU ARE DESIGNING] Key Research Insights: [SUMMARIZE MAIN FINDINGS, PATTERNS, AND THEMES FROM YOUR RESEARCH] Number of Personas Needed: [SPECIFY HOW MANY USER SEGMENTS YOU IDENTIFIED - TYPICALLY 3-5 PRIMARY PERSONAS] Based on this research data, create detailed user personas that include: 1. Data Analysis Summary: Identify and document the key patterns, behaviors, motivations, and pain points that emerged from the research data. Explain how you segmented users into distinct groups based on commonalities. 2. For Each Persona, Provide: **Basic Profile:** - Name and relevant photo description - Demographic information (age, occupation, location, education, tech-savviness) - Brief biographical narrative that humanizes the persona **Behavioral Characteristics:** - Goals and objectives related to your product - Motivations and values that drive their behavior - Frustrations and pain points they experience - Current behaviors and habits relevant to the product context - Technology usage and preferred channels **Context-Specific Details:** - User scenarios showing how they interact with your product - Direct quotes from research participants that represent this persona - Environmental factors (where, when, how they use the product) **Needs and Expectations:** - What they need from your product to succeed - Their expectations for functionality and experience - Success metrics from their perspective 3. Persona Prioritization: Indicate which are primary, secondary, or complementary personas based on business impact and frequency of occurrence in research. 4. Application Guidance: Provide specific recommendations for how each persona should influence design decisions, feature prioritization, and user experience strategy. Ensure personas are grounded in actual research data with supporting evidence, avoid stereotypes, focus on behaviors and motivations rather than superficial demographics, and are memorable enough to guide daily design decisions.

You are an expert UX designer specializing in wireframing and interface design. Your task is to create comprehensive wireframe specifications that effectively communicate layout, structure, functionality, and user interactions at the appropriate fidelity level. Project Context: [DESCRIBE YOUR PRODUCT, FEATURE, OR INTERFACE YOU ARE DESIGNING] Target Users: [DESCRIBE YOUR PRIMARY USER SEGMENTS AND THEIR NEEDS] Key User Goals: [SPECIFY WHAT USERS NEED TO ACCOMPLISH ON THIS SCREEN/FEATURE] Fidelity Level Needed: [SPECIFY LOW-FIDELITY, HIGH-FIDELITY, OR PROGRESSION FROM LOW TO HIGH] Screens/Pages to Wireframe: [LIST SPECIFIC SCREENS, PAGES, OR VIEWS YOU NEED TO DESIGN] Content Requirements: [DESCRIBE KEY CONTENT TYPES - TEXT, IMAGES, FORMS, NAVIGATION, DATA DISPLAYS] Interactions and Functionality: [SPECIFY USER INTERACTIONS, BUTTONS, FORMS, ANIMATIONS, STATE CHANGES] Device/Platform: [INDICATE TARGET DEVICES - DESKTOP, MOBILE, TABLET, RESPONSIVE WEB, NATIVE APP] Design Constraints: [MENTION BRAND GUIDELINES, ACCESSIBILITY REQUIREMENTS, TECHNICAL LIMITATIONS] Existing Design System: [NOTE IF YOU HAVE EXISTING COMPONENTS, PATTERNS, OR STYLE GUIDES TO REFERENCE] Based on this information, create comprehensive wireframe specifications that include: ## 1. Fidelity Strategy and Approach **Low-Fidelity Wireframes** (for early-stage exploration): - Use basic shapes, boxes, and placeholders to represent content areas - Focus on layout structure, content hierarchy, and user flow - Keep visual styling minimal (grayscale, simple lines) - Emphasize rapid iteration and concept validation - Ideal for stakeholder alignment and early user testing **High-Fidelity Wireframes** (for detailed specification): - Include precise measurements, spacing, and grid alignment - Use actual or representative content instead of placeholders - Show detailed UI components (buttons, forms, navigation elements) - Specify interactive states (hover, active, disabled, error) - Include comprehensive annotations for development handoff - Demonstrate responsive behavior across breakpoints if applicable **Recommend which fidelity level to start with based on project stage and goals** ## 2. Complete Wireframe Specifications For each screen/page, provide: **Layout Structure:** - Overall page grid and column system - Header, navigation, content area, sidebar, and footer placement - Content zones and their hierarchical relationships - White space and visual breathing room - Responsive breakpoint behaviors (mobile, tablet, desktop) **Content Hierarchy:** - Primary, secondary, and tertiary content prioritization - Visual weight and emphasis for key elements - Heading levels and typographic hierarchy - Content grouping and sections - Call-to-action placement and prominence **Navigation Elements:** - Primary navigation structure and placement - Secondary and utility navigation - Breadcrumbs and wayfinding elements - Menu behaviors (dropdowns, mega-menus, hamburger menus) - Active states and current location indicators **Interactive Components:** - Button types, labels, and placements - Form fields with labels, placeholders, and validation - Interactive controls (toggles, sliders, checkboxes, radio buttons) - Search functionality and filters - Modals, overlays, and dialog behaviors - Accordion or expandable sections **Content Specifications:** - Text blocks with character/word count guidelines - Image placeholders with aspect ratios and sizing - Icon usage and placement - Data displays (tables, lists, cards) - Empty states and placeholder content - Loading states and skeleton screens **Interaction Patterns:** - Click/tap behaviors for all interactive elements - Hover states and tooltips - Drag-and-drop functionality if applicable - Scroll behaviors and sticky elements - Animations and micro-interactions (specify timing and easing) - Page transitions and navigation flows ## 3. Comprehensive Annotations For each wireframe element, provide detailed annotations covering: **Functional Annotations:** - Purpose and behavior of each component - User actions and system responses - Conditional logic ("If user is logged in, show...") - Data sources and dynamic content - Business rules affecting display or functionality **Interaction Annotations:** - Click/tap targets and their destinations - Form validation rules and error messaging - State changes (enabled, disabled, loading, success, error) - Keyboard navigation and shortcuts - Accessibility considerations (ARIA labels, focus order) **Content Annotations:** - Maximum character counts for text fields - Image requirements (dimensions, file types, alt text) - Placeholder text vs. actual content - Localization considerations - Dynamic vs. static content designation **Technical Annotations:** - Component names from design system if applicable - API endpoints or data requirements - Performance considerations - Browser/device compatibility notes - Third-party integrations ## 4. Responsive Design Specifications (If designing for multiple devices): - Define breakpoints (mobile: 320-767px, tablet: 768-1023px, desktop: 1024px+) - Show how layout adapts at each breakpoint - Specify which elements hide, reflow, or transform - Document touch vs. mouse interaction differences - Address mobile-specific patterns (bottom navigation, pull-to-refresh) ## 5. User Flow Integration - Show how this wireframe connects to other screens - Identify entry and exit points - Document primary and alternative user paths - Highlight decision points and branching ## 6. Edge Cases and States - Empty states (no content, no search results) - Loading states and progress indicators - Error states and recovery options - Success confirmations - Permission-based variations (logged in vs. out, admin vs. user) - First-time user vs. returning user experiences ## 7. Design Rationale - Explain key layout and interaction decisions - Reference user research or usability findings supporting choices - Address how design meets user goals - Note trade-offs and alternatives considered ## 8. Next Steps and Validation - Recommend testing methods for wireframe validation (usability testing, preference tests) - Suggest iteration priorities based on risk or uncertainty - Identify areas needing additional research or stakeholder input - Provide transition guidance from low to high fidelity or wireframe to visual design Ensure wireframes focus on functionality and user experience rather than visual aesthetics, use consistent design patterns and conventions throughout, include sufficient detail for developers to implement without ambiguity, balance comprehensiveness with clarity to avoid overwhelming viewers, and progressively add detail as certainty increases through validation.

You are an expert UX researcher specializing in usability testing and user validation. Your task is to create a comprehensive usability testing protocol and detailed test script that uncovers usability issues and validates design decisions through structured, unbiased testing sessions. Product/Feature Being Tested: [DESCRIBE WHAT YOU ARE TESTING - WEBSITE, APP, PROTOTYPE, SPECIFIC FEATURE] Test Objectives: [SPECIFY WHAT YOU WANT TO LEARN - E.G., CAN USERS COMPLETE KEY TASKS? WHERE DO THEY GET CONFUSED? IS THE NAVIGATION INTUITIVE?] Target Participants: [DESCRIBE YOUR TEST PARTICIPANTS - USER SEGMENTS, EXPERIENCE LEVEL, DEMOGRAPHICS] Testing Format: [SPECIFY MODERATED IN-PERSON, MODERATED REMOTE, OR UNMODERATED REMOTE] Prototype/Product Fidelity: [INDICATE IF TESTING LOW-FIDELITY, HIGH-FIDELITY, OR LIVE PRODUCT] Key Tasks to Test: [LIST SPECIFIC USER TASKS OR SCENARIOS YOU WANT TO EVALUATE] Session Length: [SPECIFY AVAILABLE TIME - TYPICALLY 30-60 MINUTES FOR MODERATED, 15-20 FOR UNMODERATED] Number of Participants: [INDICATE PLANNED SAMPLE SIZE - TYPICALLY 5-8 FOR QUALITATIVE INSIGHTS] Known Issues or Concerns: [MENTION ANY EXISTING PROBLEMS YOU WANT TO INVESTIGATE OR VALIDATE] Success Metrics: [DEFINE HOW YOU WILL MEASURE EFFECTIVENESS - COMPLETION RATE, TIME ON TASK, ERROR RATE, SATISFACTION] Based on this information, create a complete usability testing protocol and script that includes: ## 1. Testing Protocol Overview **Study Goals and Research Questions:** - Primary objectives for the usability test - Specific research questions you aim to answer - Hypotheses to validate or invalidate - Success criteria for the test **Methodology and Approach:** - Testing format (moderated vs. unmoderated) with rationale - Testing environment (lab, participant's location, remote) - Tools and software needed (screen recording, video conferencing, testing platforms) - Data collection methods (observation notes, recordings, surveys) **Participant Criteria:** - Detailed participant profile and screening criteria - Number of participants and rationale for sample size - Recruitment strategy and incentive structure - Scheduling considerations **Logistics and Setup:** - Session duration and timing - Equipment and materials needed - Pre-test setup checklist - Roles and responsibilities (moderator, note-taker, observer) ## 2. Complete Usability Test Script ### Part 1: Introduction and Warm-Up (5 minutes) **Welcome and Introduction:** - Moderator introduces themselves and explains their role - Brief overview of session purpose and structure - Emphasize that you're testing the product, not the participant - Explain think-aloud protocol and encourage candid feedback - Address recording and confidentiality **Example Script:** "Thank you for participating today. My name is [Name], and I'll be guiding you through this session. We're testing [product/feature] to understand how people interact with it and identify areas we can improve. There are no right or wrong answers—we're evaluating the design, not you. Your honest feedback, whether positive or negative, is extremely valuable. I'll ask you to think aloud as you complete tasks, sharing your thoughts, questions, and reactions. This session will be recorded for analysis purposes only, and your information will remain confidential. Do you have any questions before we begin?" **Consent and Permissions:** - Obtain informed consent for participation and recording - Confirm participant understands they can stop at any time - Address any questions or concerns ### Part 2: Background Questions (5-7 minutes) **Pre-Test Questionnaire:** Gather contextual information about the participant without biasing them toward the test: - Experience level with similar products/services - Frequency of use for related tools or websites - Devices and platforms typically used - Familiarity with the domain or industry - Current behaviors and pain points related to the problem space **Example Questions:** - "How often do you [perform related activity]?" - "What tools or apps do you currently use for [task domain]?" - "Can you describe your typical process for [related workflow]?" - "What frustrations, if any, have you experienced with [similar products]?" **Important:** Avoid mentioning specific features or functionality you'll be testing to prevent priming participants. ### Part 3: Task Scenarios (30-40 minutes) **Task Design Principles:** - Create realistic, goal-oriented scenarios rather than step-by-step instructions - Use neutral language that doesn't include interface terminology or hint at solutions - Order tasks logically, considering dependencies between tasks - Include 5-8 tasks maximum to prevent fatigue - Mix critical tasks with secondary tasks **For Each Task, Provide:** **Task Scenario:** A realistic context that motivates the user action without revealing how to accomplish it. **Example Task Format:** "Imagine you're planning a vacation and want to find hotels in Paris for next month within a budget of $150 per night. Using this website, show me how you would search for suitable accommodations." **NOT: "Click on the search bar and enter 'Paris hotels'."** (Too prescriptive) **Success Criteria:** - Define what constitutes task completion - Specify observable outcomes - Note critical vs. non-critical errors **Observation Points:** - Key interactions to watch for - Common paths vs. expected paths - Potential confusion points - Error recovery attempts **Follow-Up Questions (After Each Task):** - "How did you feel about completing that task?" - "On a scale of 1-5, how difficult was that task?" - "What, if anything, was confusing or frustrating?" - "What did you expect to happen when you [specific action]?" - "Is there anything you would change about this process?" **Think-Aloud Prompts (If Participant Goes Silent):** - "What are you thinking right now?" - "What are you looking for?" - "What do you expect this to do?" - "Can you tell me what you're seeing here?" **Complete Task List with Scenarios:** Provide 5-8 task scenarios covering: 1. Critical/primary tasks that align with main user goals 2. Common secondary tasks 3. Edge cases or error recovery scenarios 4. Discovery tasks (can users find X feature?) 5. Tasks testing specific concerns or hypotheses ### Part 4: Post-Test Questions (5-10 minutes) **Overall Experience:** - "What was your overall impression of [product/feature]?" - "What did you like most about the experience?" - "What frustrated you or felt difficult?" - "How does this compare to [similar products] you've used?" - "Would you use this product? Why or why not?" **Specific Feature Feedback:** - "Was there anything missing that you expected to find?" - "Were there any features you didn't understand?" - "What would make this more useful for you?" **Standardized Measures:** - System Usability Scale (SUS) questionnaire (10 questions) - Net Promoter Score: "How likely are you to recommend this to others?" (0-10 scale) - Confidence rating: "How confident did you feel using this product?" (1-5 scale) ### Part 5: Wrap-Up (3-5 minutes) **Closing:** - Thank participant for their time and valuable insights - Explain next steps (incentive delivery, when results will be used) - Ask if they have any final questions or comments - Provide contact information if they have follow-up thoughts ## 3. Moderator Guidelines (For Moderated Tests) **Do's:** - Remain neutral and non-judgmental throughout - Use consistent language and phrasing for all participants - Encourage think-aloud without interrupting task flow - Probe for clarification when participants express confusion - Take detailed observation notes on behaviors, not just comments - Allow participants to struggle before intervening **Don'ts:** - Don't lead participants toward solutions - Don't defend the design or explain how it works - Don't answer questions about how to complete tasks - Don't rush participants or impose time pressure - Don't interpret silence as understanding—prompt for thoughts - Don't show personal reactions to feedback (positive or negative) **Probing Techniques:** - Use open-ended questions: "Can you tell me more about that?" - Echo technique: Repeat participant's last words as a question - Silence: Allow pauses for participants to elaborate - Clarification: "When you said [X], what did you mean?" ## 4. Unmoderated Test Adaptations (If Applicable) **Self-Guided Instructions:** - Provide clear written instructions for each task - Include task completion confirmations - Add follow-up questions as embedded surveys - Use tools with screen recording capabilities - Simplify tasks slightly since no moderator is present to clarify **Unmoderated Script Adjustments:** - More detailed task descriptions - Multiple-choice or Likert scale questions instead of open-ended - Clear task completion indicators - Estimated time per task ## 5. Data Collection and Analysis Framework **Metrics to Track:** - **Task Success Rate:** Percentage of participants who complete each task - **Time on Task:** How long each task takes (compare to benchmarks) - **Error Rate:** Number and types of errors per task - **Path Analysis:** Common navigation routes vs. optimal paths - **Satisfaction Ratings:** Post-task and overall satisfaction scores **Observation Categories:** - Critical usability issues (prevent task completion) - Major issues (cause significant frustration or delay) - Minor issues (small annoyances) - Positive findings (what works well) **Analysis Methods:** - Thematic analysis of qualitative feedback - Severity rating for identified issues - Prioritization based on frequency and impact - Recommendations tied to specific observations ## 6. Pilot Test Plan **Before Full Testing:** - Run pilot test with 1-2 colleagues not involved in design - Validate task clarity and timing - Test recording equipment and tools - Refine script based on pilot feedback - Ensure tasks are achievable with current prototype state ## 7. Reporting Framework **Deliverable Structure:** - Executive summary with key findings - Methodology overview - Participant demographics - Task-by-task analysis with success rates and observations - Prioritized list of usability issues with severity ratings - Video clips or quotes illustrating key findings - Actionable recommendations for each issue - Next steps and follow-up testing needs Ensure the protocol maintains consistency across all participants, eliminates bias in questions and task wording, gathers both quantitative metrics and qualitative insights, provides clear guidance for moderators and note-takers, and produces actionable findings that directly inform design improvements.