0
Customer research synthesis from raw interview notes
⁂auto-checked, 3 hours oldAauraNovice
The prompt
I have raw notes from number customer interviews about topic. Synthesize them into actual insight, not a summary of what everyone said.
Raw notes:
raw_interview_notes
Do this:
1. Identify patterns that appeared across MULTIPLE interviews (state how many, out of how many total) versus single outlier comments, don't treat one loud opinion as a trend.
2. Find the contradictions: where did customers disagree with each other, and what might explain the difference (segment, use case, prior experience)?
3. Surface the insight that would be easy to miss on a skim: something implied but not directly stated by any single customer, that becomes visible only when you look across all of them together.
4. Distinguish what customers said they want from what their actual described behavior suggests they need (people are unreliable narrators of their own motivations).
5. Give me 3 specific, testable hypotheses this research suggests, each stated as something we could validate or kill with a specific next action, not vague takeaways like 'users want more flexibility.'
Quote directly from the notes to support each claim, don't paraphrase away the evidence.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 3 hours ago |
Example output
Pattern found in 7 of 9 interviews: users described 'exporting to a spreadsheet' as their real workflow, not using the dashboard as the source of truth, despite the dashboard being the paid feature. Contradiction: enterprise-segment customers wanted more customization ('I want to change literally everything'), while smaller-team customers wanted fewer choices ('just tell me what to look at'), likely explained by team size affecting who actually configures the tool. Implied insight: no single customer said 'your onboarding is too generic,' but across 6 interviews, each described a different workaround for the same onboarding gap, indicating a real unaddressed problem invisible in any one transcript. Said-vs-behavior gap: customers said they wanted 'more integrations' but described using only 2 of the 14 existing integrations, suggesting the actual need is better surfacing of what's already there, not more breadth. 3 testable hypotheses given, each with a specific validation action (e.g. a smoke-test landing page, a targeted follow-up survey).
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.