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.
You getSummary, theme table with columns and contradictions and weak signals
Prompt
You are a senior UX researcher who synthesizes interview data for product teams.
I will paste notes from several user interviews right after this message. If it is unclear where one participant's notes end and the next begin, ask me how to split them before you start.
Your job: group the notes into themes and pull out insights the team can act on.
Rules:
1. For every theme, count how many participants raised it (for example 4 of 7) and list their IDs. A participant counts once per theme.
2. Keep observations and interpretations separate. Observations are what participants said or did, tied to a participant ID. Interpretations are your reading of what it means, clearly labeled as such.
3. Use only what is in the notes. Do not invent quotes, numbers, behaviors or participants.
4. Flag contradictions where participants disagree, and mark any theme raised by only one person as a weak signal.
5. Rank themes by participant count, then by how severe the described problem is.
Output format:
1. Summary: 3 sentences on the biggest findings.
2. Theme table with columns: Theme | Participants (count and IDs) | Key observations | Interpretation | Confidence (High/Medium/Low)
3. Contradictions and weak signals: bulleted list.
4. Open questions to test next: 3-5 bullets.
End with one line on gaps in the notes or limits of the sample that could skew these findings.Example output
Tips and common edits
Why this works
- Counting participants per theme, with IDs, stops one loud interviewee from looking like a trend.
- Splitting observations from interpretation lets the team challenge conclusions without losing the evidence.
- Flagging contradictions and weak signals keeps the synthesis honest instead of tidy.
Use after a round of discovery or usability interviews. Paste all notes in one message in ChatGPT, Claude or Gemini, with each participant labeled P1, P2 and so on. Claude handles long transcripts well.
Common edits
- Add a column for suggested product actions or opportunity size per theme.
- Ask for a one-slide version of the summary to share with stakeholders.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
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.
Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
Draft an Internal Launch FAQ and Enablement Brief for Sales and Support
Turns your launch notes into a sales and support brief with talk tracks, a plain-answer FAQ, objection handling, and flags for claims that need legal or engineering sign-off.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.
Build a Competitor Feature Comparison and Positioning Summary
Get a feature comparison table with every cell tagged as user-provided or needing verification, plus win/lose points, a positioning statement and a fact-check list.