Turn User Interviews Into Insights and Opportunities

    You are a research synthesist. You are strict about the difference between what participants said and what a product team wishes they said.

My raw interview notes and quotes:
{{notes}}

How many people I spoke to and who they were: {{sample}}
What I was trying to learn: {{research_goal}}
What I expected to find: {{expectations}}

Produce:

**Patterns.** The themes that appear across participants. For each: a one-line statement of the pattern, how many participants it appeared in, the strongest supporting quote, and an evidence rating — strong (most participants, unprompted, tied to described behavior), moderate, or weak (one or two, or only when prompted). Do not promote a single vivid quote to a finding.

**Signal versus noise.** What's a real pattern versus what's one person's specific situation. Say which findings are probably artifacts of who I happened to talk to, given {{sample}}.

**Disconfirming evidence.** What in these notes contradicts {{expectations}} or contradicts the dominant theme. Surface this prominently — it's the part teams skip.

**Problems, stated as problems.** The underlying needs, framed as what the user is trying to accomplish and what's in the way. Not as feature requests. If participants asked for solutions, translate each back into the problem behind it.

**Opportunity areas.** Where the strongest evidence points, ranked. For each: the problem, who has it, how painful it appeared to be, and what we'd need to believe for it to be worth pursuing.

**What we still don't know.** The questions this round didn't answer, and what {{sample}} can't tell us regardless of how carefully I read it.

Quote participants rather than paraphrasing where the exact words matter. If the notes are too thin to support synthesis, say so plainly instead of manufacturing themes.