From User Interview to Opportunity Statement in One Session
The gap between a user interview and a sprint-ready opportunity statement is where most discovery work gets lost. This resource gives you the exact prompt sequence to run in a single Claude session — from raw transcript to structured opportunity statement — including how to handle contradictory signals and what the output should look like before sprint planning.
Discovery Interview Synthesis
One Session. One Opportunity Statement.
A structured prompt sequence that turns raw interview transcripts into sprint-ready opportunity statements.
Load Transcripts
Paste all interview notes and ask Claude to extract raw quotes grouped by theme. No formatting needed.
Cluster Themes
Ask Claude to reduce quotes into three to five major signal clusters, each with at least two supporting quotes.
Surface Contradictions
Run a dedicated prompt to find where users disagreed. Contradictions are signal, not noise.
Draft the Statement
Ask Claude to write the opportunity statement using your team's template. Give it the format you expect.
Validate Output
Review the draft against original transcripts. If a key quote is missing, the synthesis likely lost something.
Expect Them
Most interviews produce contradictions. Flagging them is part of the process, not a sign that the data is bad.
Segment by Context
Contradictions often resolve when you separate by user role, experience level, or frequency of use.
Name the Tension
A strong opportunity statement can include an open question when the data does not fully resolve.
Opportunity Header
One sentence: the unmet need, who has it, and why addressing it matters to the business right now.
Evidence Block
Three to five quotes that support the opportunity. Selected to represent range, not just the clearest signal.
Open Questions
The things you still need to validate. Listing them makes sprint planning conversations more honest.
Synthesizing Too Early
Starting the opportunity statement before all interviews are loaded means the first themes anchor everything that follows.
Ignoring Outliers
The interview that breaks your pattern usually matters more than three that confirm it. Do not skip it.
Over-Polishing
A synthesis that sounds too clean has usually lost the raw complexity of what users actually said.
Key Takeaways
- 1Run a five-prompt sequence to convert raw interview transcripts into a structured opportunity statement in one session.
- 2Use a signal-clustering prompt to group themes automatically and surface the most consistent user pain points.
- 3Flag contradictory signals early with a dedicated prompt step so you address them before they reach sprint planning.
- 4Format your opportunity statement output to match the structure your team expects in planning documents.
- 5Save the session as a reusable template so every discovery sprint starts from the same proven foundation.
The Interview-to-Opportunity Prompt Pack
Sign in to access this prompt-pack
Create a free Fluent account to unlock templates, prompt packs, and checklists.
Create free account