Loading...
Generate comprehensive questions for customer interviews, surveys, and feedback collection sessions to gather actionable insights.
# Create Questionnaire for User Research Act as a Product Manager creating a questionnaire for user research. ## Research Context - **Research Objective**: [What you want to learn] - **Target Audience**: [User segments] - **Research Method**: [Interview/Survey/Focus Group] - **Duration**: [Expected time] ## Questionnaire Structure ### 1. Warm-up Questions (5 minutes) **Purpose**: Build rapport and get context - Tell me about yourself and your role. - How long have you been using [product category]? - What does a typical day look like for you? - What tools do you currently use for [relevant task]? ### 2. Background and Context (10 minutes) **Purpose**: Understand current state - What are your biggest challenges with [current solution]? - How do you currently solve [problem]? - What would make your workflow easier? - What features do you wish existed? ### 3. Specific Feature Questions (15-20 minutes) **Purpose**: Gather detailed feedback **For New Features**: - How would you use [feature]? - What problems would this solve for you? - What concerns do you have about [feature]? - How does this compare to alternative solutions? **For Existing Features**: - How often do you use [feature]? - What do you like most about [feature]? - What frustrates you about [feature]? - What improvements would you suggest? ### 4. Ideal Solution Questions (10 minutes) **Purpose**: Understand desires - If you could design your ideal solution, what would it look like? - What would make you switch from your current solution? - What's missing from current options? - What would make this feature indispensable? ### 5. Prioritization Questions (5 minutes) **Purpose**: Understand importance - Rank these features by importance: [List features] - If you could only have one improvement, what would it be? - What would you pay for this feature? - What's nice-to-have vs. must-have? ### 6. Closing Questions (5 minutes) **Purpose**: Capture final thoughts - Any other thoughts or feedback? - Would you recommend [product] to others? Why/why not? - What would make you a power user? - Anything else you'd like to share? ## Survey-Specific Questions **For Email/Online Surveys** (use shorter, multiple-choice when possible): **Multiple Choice**: - How often do you use [feature]? - Daily - Weekly - Monthly - Rarely - Never **Rating Scales**: - Rate your satisfaction with [feature] (1-10) - How likely are you to recommend [feature]? (0-10 NPS scale) **Open-Ended**: - What would improve your experience with [feature]? - What features would you like to see added? ## Best Practices **Question Formulation**: - Use clear, jargon-free language - Ask one question at a time - Avoid leading questions - Use open-ended questions for insights - Use closed-ended questions for quantification **Question Order**: - Start with easy, non-threatening questions - Build complexity gradually - Group related questions together - End with optional demographic questions **Interview Tips**: - Listen more than you speak - Ask "Why?" to dig deeper - Use "Tell me more about..." prompts - Capture exact quotes when possible **Survey Tips**: - Keep surveys under 10 minutes - Use progress indicators - Make questions optional where appropriate - Offer incentives for completion
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns
Helps you articulate a compelling, long-term product vision by guiding you through the creation of a 'Working Backwards' Press Release or a strategic memo.
Develops pricing models and strategies
This template is crafted to facilitate the creation of epics for a product backlog, inspired partly by Tim Herbig's hypothesis framework. It provides a structured approach to articulate assumptions about new features, products, or services. By clearly outlining the action or solution for target beneficiaries, the expected outcomes, and the methodology for testing and validation, teams can better navigate the uncertainty inherent in product development.