Customer Interview Analyzer
Extract customer insights, pain points, needs and opportunities from interview notes.
Act as a Senior Product Researcher and Product Manager.
Analyze the following customer-interview notes:
{{interview_notes}}
Research objective:
{{research_objective}}
Product or problem context:
{{context}}
Analyze the notes and identify:
1. Customer Goals
2. Jobs To Be Done
3. Current Behaviors
4. Pain Points
5. Frustrations
6. Motivations
7. Existing Alternatives
8. Decision Criteria
9. Workarounds
10. Barriers to Adoption
11. Positive Feedback
12. Feature Requests
13. Underlying Customer Needs
14. Contradictions
15. Emotional or Social Factors
16. Product Opportunities
17. Risks and Concerns
18. Questions Requiring Further Research
For every finding, provide:
- Finding
- Supporting Evidence
- Evidence Type
- Frequency, if multiple interviews are provided
- Confidence Level
- Product Implication
- Recommended Follow-Up
Separate:
- Direct customer statements
- Researcher interpretation
- Product hypothesis
Do not treat every feature request as a validated need.
Do not invent quotations, motivations or frequencies.
Group related findings into themes.
Return:
1. A thematic analysis
2. A structured insight table
3. The five most important customer problems
4. Product opportunities
5. Assumptions requiring validation
6. Recommended next research questionsExample in action
See how this prompt transforms a real input into a structured result.
Research objective: Understand why customers struggle to use historical reports. Interview notes: Participant 1: “I know the report exists, but I never remember which section contains it. I usually ask a colleague for the link.” Participant 2: “The report names are very similar. I open several reports before finding the right one.” Participant 3: “I would like to save the reports I use every month. Searching for them repeatedly wastes time.” Participant 4: “The date filter resets every time I return to the report.” Product context: An internal analytics application used by operations teams.
Theme 1: Report Discoverability Finding: Users cannot reliably locate previously used reports. Supporting Evidence: Participants 1, 2 and 3 described repeated difficulty finding the correct report. Confidence: High Underlying Need: Quick access to frequently used reporting information. Product Implications: - Improve report search - Clarify report naming - Add recently viewed reports - Support saved reports --- Theme 2: Repeated Configuration Finding: Users repeatedly configure the same date filters. Supporting Evidence: Participant 4 reported that filters reset when returning to a report. Confidence: Medium Opportunity: Allow users to save filter preferences with a report. --- Top Customer Problems: 1. Reports are difficult to discover. 2. Similar report names create confusion. 3. Frequently used reports cannot be saved. 4. Filter configurations are not retained. Recommended Next Research: - Measure report-navigation time - Review search terms - Test saved-report functionality - Validate whether report naming matches user terminology