PromptSharp › Prompt Library › Product Management › Interview debrief: from transcripts to opportunities, not feature requests
Interview debrief: from transcripts to opportunities, not feature requests
Five user interviews this week. Extract opportunities — not feature requests — while keeping quote-level receipts.
The prompt — copy and run it
You are a product-discovery coach processing user-interview transcripts. I will paste anonymized notes or transcripts. Produce: A) OPPORTUNITY TABLE — columns: opportunity (the need or pain, phrased in the user's own words), verbatim quote + interview number, frequency across interviews, severity signal (workaround built / paying for alternative / complaining only), existing workaround. B) FEATURE-REQUEST TRANSLATION — every explicit feature ask in the material, mapped back to the underlying need it expresses, with the quote. C) NEXT TESTS — the 3 assumptions now most worth testing, each with the cheapest honest test design (fake door, prototype walkthrough, concierge). Inputs: [PASTE ANONYMIZED TRANSCRIPTS OR NOTES, LABELED BY INTERVIEW NUMBER + SEGMENT] · [PRODUCT + SEGMENT CONTEXT] Rules: Do not invent user quotes, merge users into composites, or infer needs no quote supports — write "not observed" instead. Verify frequency counts before this enters a roadmap argument. Keep users anonymous: no names, emails, or company identifiers in the output.
Why this prompt works
Translating feature asks back to needs is what separates discovery from order-taking. Frequency and severity columns stop the loudest interview from writing the roadmap, and the quote-level receipts survive the stakeholder who asks 'says who?'
Want the daily version?
The PromptSharp Product Brief delivers prompts like this every day. Honest status: sample stage — 50 waitlist signups start the free daily, and waitlist members see every issue first.
Frequently asked
When should I use this prompt?
Five user interviews this week. Extract opportunities — not feature requests — while keeping quote-level receipts.
Why does this prompt work?
Translating feature asks back to needs is what separates discovery from order-taking. Frequency and severity columns stop the loudest interview from writing the roadmap, and the quote-level receipts survive the stakeholder who asks 'says who?'
What mistake does this prompt help you avoid?
{'code': 'PF05', 'note': "The loudest interview writing the roadmap — frequency and severity columns plus quote-level receipts that survive 'says who?'."}
Related Product Management prompts
Interview synthesis: turn user calls into jobs-to-be-done, not feature requests
You ran a batch of user interviews and got a wishlist. Translate it into the underlying jobs and unmet needs worth building for.…
PRD skeleton with the edge cases the eng team will actually find
You have a validated problem and a solution sketch. Draft the PRD skeleton — with the edge cases and non-goals that prevent the we…
All Product Management free prompts
The PromptSharp Product Brief page — five full free prompts plus the ladder status.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt each day, rotating across the roster. See what each vertical is like before you commit to one.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Home · Prompt Library · Pricing · Archive · Privacy · Terms · Refunds
Finance · CPG · Marketing · Sales · Consulting & Strategy · Product Management · Dev & Engineering · C-suite · Law · Personal Finance · Career & Job Search · Focus & Productivity · Learning · Health & Fitness · Parenting