Transform Customer Interview Transcripts into Ranked Pain-Point Matrix
Turn raw interview notes into a structured matrix that ranks customer pain points by frequency and business impact to guide your product roadmap.
Prompt
Act as a Senior Product Manager. I will provide raw notes from customer interviews. Your job is to extract specific pain points and organize them into a ranked matrix. Follow these rules: 1. Identify distinct user problems, not feature requests. 2. For each problem, extract one verbatim quote from the transcript as evidence. 3. Estimate the business impact as either Low, Medium, or High based on mentioned operational or financial consequences. 4. Tally the frequency of each problem across the provided notes. Output format: Provide a markdown table with columns: Problem Statement, Verbatim Quote, Business Impact, and Frequency Count. Follow the table with a 3-bullet summary of the top priorities based on highest frequency and impact. This is for internal product discovery and does not replace formal user research methodologies.Example output
Tips and common edits
Why this works
- Forces a distinction between user problems and feature requests.
- Mandates verbatim evidence to ground the analysis in real user data.
- Uses a structured table to make prioritization decisions visually clear.
Use this to synthesize discovery sessions when you have messy notes from 3-10 user interviews. Paste your combined notes directly after the prompt in ChatGPT, Claude, or Gemini. Ensure your notes contain clear speaker labels.
Common edits
- Add a column for 'User Persona' if you are interviewing different types of stakeholders.
- Adjust the impact criteria to focus specifically on churn risk if that is your current primary goal.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Define Feature Non-Goals and Scope Boundaries
Sort requested features into three clear out-of-scope buckets with explicit business reasons to prevent scope creep.
Extract win and loss drivers from CRM notes
Turn raw CRM deal records into actionable product, pricing, and sales execution patterns. Use it to prepare roadmap reviews and board updates.
Cluster Support Tickets by Operational Cost and Severity
Transforms raw support ticket exports into prioritized root-cause engineering clusters ranked by operational support hours wasted.
Draft a Zero-to-One Product Discovery Experiment Card
Generates a structured, one-page test card with a falsifiable hypothesis, cheap validation test, and numeric kill threshold for new features.
Synthesize User Interview Notes into Counted Themes and Insights
Turns raw interview notes into a ranked theme table showing how many participants raised each theme, with observations kept separate from interpretation.
Write a Customer Interview Script That Validates a Problem with Past-Behavior Questions
Get a 30-minute problem-discovery interview script with past-behavior questions, two follow-up probes each, banned-question rewrites and evidence signals.
- Draft a working-backwards press release and FAQ
- Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
- Build a Competitor Feature Comparison and Positioning Summary
- Prioritize Your Feature Backlog with RICE Scoring and Flagged Weak Assumptions
- Score beta readiness for general availability release
- Reframe a feature request into a core user problem